Default avatar
Hide&Seek 1 month ago
"The 257-byte control block limit constrains large Taptrees. Advanced smart contracts like BitVM may need to wait until [BIP110] expiry or use testnet/sidechains." source: bip110.org — though on the same page they also pretend that "All known monetary use cases remain fully functional and unaffected.", which is quite gross. Btw, let me add that blocking consensus upgrades will also delay any covenant update, that are required for Ark to become viable, as well as to upgrade lightning... Since I assume we all know what "temporary emergency measure" means. Pretty interesting consequences of a sloppy design... If prevent harmful content on the nodes was the point, cap-sizing OP_RETURN would have been sufficient, but ofc they had to overdo it to retaliate and show everyone who's the bitcoin boss, and now we have this mess instead... Lame. :(

Replies (1)

Can you link the exact source? All I found on the website is this disclaimer, that claims complications around BitVM, not that it becomes unviable. Also, it’s absolutely normal to disable upgrade hooks for other soft forks while this one gets adopted. Not to mention any soft forks will require months or years of discussion and signalling before it has any chance of going live. It’s common engineering logic - don’t start building extensions around your house while its foundations are shaky. image