Bitcoin Covenants Without a Soft Fork: FE Keys Lock Spending at 32 Bytes
FE covenants skip the opcode debate entirely by baking spending rules into the signing key itself. No soft fork, no activation drama, no mailing list. But the trade-off is interactive setup and a key you can't read.
Here's the trick. Instead of teaching Bitcoin script a new opcode, FE covenants push the rule into the key itself. The signing key is generated under a constraint. Only a transaction that satisfies a predefined condition can produce a valid signature. Everything else dies at the cryptography, before a single node sees it.
That's a meaningful sidestep. Covenant proposals have been in the workshop for years. OP_CHECKTEMPLATEVERIFY, OP_CHECKSIGFROMSTACK, OP_CAT. Three good ideas, zero activations. Taproot went live in November 2021 and the opcode list hasn't moved since. Every proposal on that list needs a soft fork, and a soft fork needs social consensus long before it needs code. FE covenants need neither. They run on mainnet today.
The trade-off is real. A restricted key isn't a script. You can't compose it with timelocks the way you'd compose opcodes. Setup is interactive, which means a signing ceremony, multiple parties, and coordination overhead a raw opcode would never ask for. Auditability drops as well. A covenant you can read in script is a covenant a reviewer can verify. A constraint baked into a 32-byte key is a black box with a proof stapled to it.
The data is unambiguous on one point. Builders aren't waiting. Vault designs, custody templates, and hard spending limits are shipping on what Bitcoin already has. Not speculation. Arithmetic.
So who wins? Custody desks first, then vault builders. Anyone who needs a spending rule enforced without asking miners, node operators, or a mailing list for permission. Who loses? The opcode purists, and I say that with genuine respect. Their version is cleaner, cheaper to audit, and composable. None of that matters if it never activates.
My take is blunter than usual. Bitcoin's governance process is the most expensive compiler in this industry. FE covenants are how engineers route around it rather than fight it. That's not a compromise, that's a workaround with better shipping velocity.
Watch key-generation tooling over the next two quarters. If signing ceremonies get boring and cheap, covenants arrive and nobody has to vote on them.