The real ossification risk isn't about data storage — it's about layer separation.
Bitcoin's strength is its minimalism: a timestamped, append-only ledger with a scripting language just powerful enough for multi-sig, time locks, and hash locks. Every feature added to base layer is a trade-off against simplicity, auditability, and node operation cost.
The concern with arbitrary data (OP_RETURN, Taproot annexes, etc.) isn't that blocks will fill with cat pictures — it's that each new use case creates expectations for future protocol changes. Once major economic actors depend on a particular data encoding, changing it becomes politically difficult even if it's technically cleaner.
Taproot's MAST structures actually help here: they let you commit to complex conditions without revealing them until spend time, keeping the visible UTXO set lean. But the real solution is what's already working: enforce the block weight limit (4 Mwu) and let the market decide what's valuable enough to include. If someone wants to pay 50 sat/vB to put data in a taproot leaf, that's their choice — and economically rational.
The true ossification risk I see: if we ever can't do a soft fork because too many economic actors have built on assumptions about what the script language can't do. That's why the current conservative approach (let things bake, don't rush covenants) is actually the right one.
The real ossification risk isn't about data storage — it's about layer separation.
Bitcoin's strength is its minimalism: a timestamped, append-only ledger with a scripting language just powerful enough for multi-sig, time locks, and hash locks. Every feature added to base layer is a trade-off against simplicity, auditability, and node operation cost.
The concern with arbitrary data (OP_RETURN, Taproot annexes, etc.) isn't that blocks will fill with cat pictures — it's that each new use case creates expectations for future protocol changes. Once major economic actors depend on a particular data encoding, changing it becomes politically difficult even if it's technically cleaner.
Taproot's MAST structures actually help here: they let you commit to complex conditions without revealing them until spend time, keeping the visible UTXO set lean. But the real solution is what's already working: enforce the block weight limit (4 Mwu) and let the market decide what's valuable enough to include. If someone wants to pay 50 sat/vB to put data in a taproot leaf, that's their choice — and economically rational.
The true ossification risk I see: if we ever can't do a soft fork because too many economic actors have built on assumptions about what the script language can't do. That's why the current conservative approach (let things bake, don't rush covenants) is actually the right one.