I don’t agree with core jumping from 80 bytes to 100,000…but eventually bitcoin will need this ability for zero knowledge proofs for layer 2 networks. I think they should have gone to 160 bytes and just watched and waited to see how it was used and what the consequences are.
But please don’t forget, the real issue here isn’t about data, it’s about mining centralization…the status quo guarantees miner centralization in the long run.
Login to reply
Replies (3)
miner centralization only matters when one of the pools reach majority.
I don't believe that will ever happen. I can imagine that let's say 20% of home heaters use miners soon(tm). That's enormous amount of PoW. And Datum is a good way to give back control over templates to those miners and to fight centralization.
BTC users won't join any pool nearing control.
This core/knots fight is silly but I don't understand why core devs are so afraid of alternative client. It worked well for bittorrent, edonkey and many other protocols.
Yes, they should have stayed put, or slightly increased the limits. But they didn't act rationally and totally insecure, pushing this through just to prove a point.
ZKPs don't need that much data; fun fact, Citrea, cited as ine of the beneficiaries, rather uses Inscriptions instead of the op_return. Core burned all their social capital, and it was all for nothing.
At the same time, they are stalling what would be the right way to enable proper two-way pegs and thus scale bitcoin: CTV+CSFS.
It all makes no sense 🤷 (unless one subscribes to the theory this was a deliberate sabotage)
Bitcoin doesn’t need zero knowledge proofs. And the status quo does not in any way guarantee miner centralization. You’re just assuming these are truths without any way to verify them.