"We need to stop data on bitcoin because there could be viruses and grandma could get infected!" But on-chain data just sits there as inert bytes that no node ever executes, and bitcoin isn't a file network, so there's no path by which verifying the chain runs or installs anything. "We need to stop all spam on bitcoin!" But you can't prevent arbitrary data from being embedded, and the BIP itself admits this because it says all you do is force people to disguise the data as financial data or break it into multiple pushes. "We need to slow down spam on bitcoin!" But 110 doesn't stop spam and the authors concede that, so all it really does is pick which data survives, because it restores the 83 byte OP_RETURN limit that Runes already fit inside while it guts inscriptions. "We need to make it harder for spammers to spam on bitcoin!" But forcing data off OP_RETURN and into disguised outputs can make the footprint worse, because provably unspendable OP_RETURN can be pruned while disguised script data sticks around and bloats what every node has to keep. "We need to signal to spammers that we don't want spam on bitcoin!" But arbitrary data has been on bitcoin since the genesis block when Satoshi embedded the Times headline about the bank bailout. "But spam is bad and bitcoin is money!" But we already knew bitcoin was money because it has a price ticker, and that's been the main use case to date.
Isn't it curious that twitter polls don't translate into miner signaling? Who could have seen this coming?
Agreed.
Nah just seen this movie many times before.
It's crazy how they think they can stranglehold the developers and the miners, like that's not how bitcoin works sorry.
Welcome to theonevortex spacestr profile!
About Me
Former host of The Bitcoin News Show. Creator of https://bitcoindev.org. Bitcoin Is. And that is enough.
Interests
- No interests listed.