I think one thing is pretty clear, there is no consensus at the moment on this OP_RETURN issue.
Thread
Login to reply
Replies ()
This is what makes bitcoin different than everything else
Option 1) build a cabal of existing devs to agree to the PR, shut out any dissenting devs, spend your credibility on an irrelevent issue and hoist the change on the public with no explanation
Option 2) engage in a public debate, preserve your team's credibility for something meaningful, accept defeat if you cannot build consensus
Option 3) same as option 1, but intentionally destroy the team's credibility to fragmemt the community so you can shoehorn compromising fork-requiring features into what you claim is "real bitcoin" so it can be coopted by governments and banks as an oppressive tool of surveillance and control.
The consensus is whatever gets mined on the longest chain with most PoW. That's how bitcoin works.
Is there a good steelman of removing the byte constraint?
That the limit is not only ineffective and easily circumvented, but also incentivizes more harmful behavior
The best I've heard is that the alternative option is to pollute the UTXOset with forever unspendable transactions. This is bad. To be clear, by removing the byte constraint, it doesn't remove this alternative option; but at least, it would give someone the option to take one for the team and pay 4 times as much fee in order to not pollute the UTXOset.
To me, the incentives just don't line up with a realistic expectation that removing the byte constraint will have any significant positive effect. And, we can't really know what all the negative effects might be until after the fact.
*I don't know if this counts as a good steelman; but, it's the best I've heard yet.
Adding some kind of exponential cost for every increase in published data size could form part of a solution, IMHO.
It wasn't added by consensus.
That's important.
I would say that's how it is 🤷♂️
Fly ball….
Caught
I just hope everyone has fun
Consensus is not needed for mempool policy.
I think one thing is pretty clear, there is no consensus at the moment on this OP_RETURN issue.
View quoted note →
Miners decide what's in blocks. Node runners decide what's in their mempools. I will run the software that respects this.
🔥🔥🔥 Down with Bitcoin C(wh)ore 🔥🔥🔥
There doesn't need to be, it's not a consensus issue.
Let’s provide clarity
Bitcoin isn’t a software project with monetary implications. It’s a monetary revolution that just happens to be built in code.
nevent1qqswcty6czmnnsqw63d79vwtfydpgfgm8hy9vqtfvf6teu8dlrcvlhsppamhxue69uhkztnwdaejumr0ds9duwvz
the consensus is there's no consensus yet
I was told that consensus if found by “humming” what about the non-hummers? Do they get a voice?
Wen Bitcoin mechanic podcast on this issue, Marty?
𝐌𝐄𝐒𝐒𝐀𝐆𝐄 BlackHat_Nexus 𝐅𝐎𝐑 𝐀𝐍𝐘 𝐊𝐈𝐍𝐃 𝐎𝐅 𝐒𝐄𝐑𝐕𝐈𝐂𝐄 𝐑𝐄𝐂𝐎𝐕𝐄𝐑 𝐘𝐎𝐔𝐑 𝐀𝐂𝐂𝐎𝐔𝐍𝐓Fast, Available and Reliable for any of the following services
🤳 Recovery of lost funds🤳 Facebook Hack🤳 WhatsApp Hack 🤳 Instagram Hack🤳 Spying🤳 Windows Hacking🤳 Recover lost wallet 🤳 Credit score trick 🤳 Recover Password🤳 Gmail Hack🤳 SnapChat Hacking 🤳 Cellphone Monitoring 🤳 Tik Tok Hack🤳 Twitter Hack🤳 Lost Phone Tracking🤳 Lost IaptopTracking🤳 Lost Car Tracking🤳 Cloning WhatsApp🤳 Cryptocurrency Wallet🤳 Hacking🤳 Iphone unlock 🤳 Got banned 🤳 Private Number available🤳 Telegram hacking 🤳 Websites hacking 🤳 Hack University 🤳 IOS and Android hack 🤳 Wifi Hacking 🤳 CCTV hacking🤳 Hack Bot Game 🤳 Free fire hack 🤳 Changing of school grades 🤳 Cards 💳hackingNo 🆓 services 🚫WhatsApp +1 3606068592Send a DM 
Telegram
Telegram – a new era of messaging
Fast. Secure. Powerful.
Link to this issue.