I think one thing is pretty clear, there is no consensus at the moment on this OP_RETURN issue.
Login to reply
Replies (25)
Someone told me
Move to knots or get shot
yeah it’s abundantly clear, they should close the pr
This is what makes bitcoin different than everything else
Knots is better, why use Core?
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's important.
That the limit is not only ineffective and easily circumvented, but also incentivizes more harmful behavior
I would say that's how it is 🤷♂️
Fly ball….
Caught
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.
I just hope everyone has fun
Consensus is not needed for mempool policy.
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
Adding some kind of exponential cost for every increase in published data size could form part of a solution, IMHO.
there is no consensus that it's not a consensus issue
It wasn't added by consensus.
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?
Link to this issue.