Bitcoin's core scripting system has a critical gap blocking complex spending rules. Twelve competing proposals now aim to fix it. The outcome could unlock long-sought transaction features.
What's Missing in Bitcoin Script
Bitcoin Script lacks one essential component for covenants. That's the term for spending conditions like time locks or multi-sig requirements. Without it, users can't set advanced transaction rules natively. The network forces workarounds that aren't ideal.
How Twelve Designs Arose
Developers noticed the limitation and proposed fixes. Now twelve distinct approaches are circulating. Some tweak existing opcodes. Others suggest new ones. All target the same missing piece but disagree on implementation. This isn't the first time Bitcoin needed new transaction logic. The community has grappled with similar challenges before.
Why Covenants Matter to Users
Regular users want features like shared wallets with spending caps or auto-renewing contracts. Current Bitcoin can't do these cleanly. Covenants would let people set rules like "this payment releases only after 30 days." It's about making transactions smarter without third parties.
The Path to Resolution
The community must pick one proposal. Fragmentation would hurt Bitcoin's reliability. Developers will debate the options over coming weeks. The next step is clear: test which design works best without breaking the network. Until then, users keep working around the limitation.
