Most of the talk about CTV activation is all about the technical stuff. There isn't much chatter on the economic side like if having covenants could actually lead to the steady fee demand Bitcoin will need since subsidies are gonna drop.
Right now, fees are sitting at about 1.25% of what miners make. By the early 2030s, the subsidy is expected to go below 1 BTC for each block. Lightning helps by moving payments off-chain but isn't really chipping in any significant L1 fees. Plus, with Wrapped BTC, a lot of the economic action shifts to different chains altogether.
With Taproot, we've got a chance for more intricate on-chain logic to unfold. Introducing covenant opcodes (like CTV, CAT, CSFS) could push this even further think about native vault structures, programmable spending conditions, and financial solutions that settle right on L1.
I put together a deeper dive on this topic here: https://covenant.ac/articles/bitcoin-fee-market-economy/
I’m curious to hear what everyone here thinks. Could this covenant-enabled setup actually shift the way the fee market is heading?
Making the case for covenant opcodes and sustainable fee markets
4 replies 60 views
paul.ninjaFull Member
Posts: 152 · Reputation: 539
#2Jun 22, 2025, 07:47 PM
Covenants are probably more useful than a lot of people give them credit for, especially for stuff like vaults, congestion control, batching tricks, timeout trees, and making some of the ugly wallet/security stuff less ugly. But whether or not they create sustained L1 fee pressure is not guaranteed. Some covenant use cases may actually compress activity and make blockspace usage more efficient. That is good for users, but it is not automatically good for miner revenue per economic action. A well-built settlement system can move a lot of value with fewer bytes, which is exactly the sort of thing Bitcoin people usually applaud until the fee-market discussion walks into the room wearing muddy boots.
The stronger economic case, to me, is not "CTV/CAT/CSFS will save the security budget." It is that Bitcoin should be able to support more native self-custodial financial structures without pushing everyone into wrapped BTC, federated duct tape, or custodial yield goblins with nice landing pages.
If meaningful economic activity wants Bitcoin as collateral or settlement, I would rather that happen with Bitcoin-native tools than on some other chain where the main trust model is "bridge admin pinky promise."
Good point on fee compression, more efficient settlement could mean fewer bytes per economic action, which cuts both ways for the fee market. That tension is real.
But your second point is the one to double down on. The choice right now is: Bitcoin-native vaults and self-custodial structures, or "custodial yield goblins with nice landing pages" as you put it. Most BTC holders are choosing the goblins because the native option doesn't exist yet.
The bridge admin pinky promise model has cost $2.8B since 2022. That's not theoretical risk. If covenant opcodes just move some of that activity back to native Bitcoin tools, even without solving the full security budget question, that seems worth doing on its own terms.
What's your read on what gets builders to actually ship on this though - is it the tooling, the opcode activation, or just someone proving demand first?
paul.ninjaFull Member
Posts: 152 · Reputation: 539
#4Jun 24, 2025, 03:08 PM
My read is that builders do not seriously ship until the target stops moving. You can prototype covenant ideas forever, but nobody sane wants to build production wallet infrastructure, recovery flows, vault UX, monitoring, hardware wallet support, and support docs on top of "maybe this opcode, maybe that opcode, maybe never."
So I'd put activation first, but not because the opcode creates demand by magic. It just gives builders a stable floor. After that, tooling decides whether it becomes useful or remains another elegant primitive understood by 40 people and safely ignored by everyone else.
Demand is already visible indirectly. Wrapped BTC, custodial lending, bridge risk, exchange collateral, centralized vault products, all of that is people trying to use BTC as financial collateral or settlement, just outside Bitcoin's trust model. If covenants pull even some of that back into native self-custodial Bitcoin tools, that is worthwhile even if it does not single-handedly solve the whole security budget question.
The first serious wedge is probably not "DeFi on Bitcoin" in the noisy sense. It is vaults, safer custody, delayed withdrawals, spending policies, and recovery paths. Boring stuff, but boring is where real money usually sleeps.
This is sharp - especially the point about activation giving builders a stable floor. That's exactly the bottleneck. Nobody's shipping production infrastructure on top of "maybe."
And you're right that the first wedge isn't flashy DeFi. It's vaults, custody, spending policies - the boring plumbing that institutions need before they'll touch anything native. The noisy stuff comes later, if at all.
The wrapped BTC and custodial lending point is what I keep coming back to. That demand isn't theoretical - it's $70 billion in activity already happening outside Bitcoin's trust model. The question isn't whether people want to use BTC as collateral. They already do. It's whether they can do it without handing their keys to someone else.
Wrote a follow-up piece responding to Saylor's Four Ideologies - arguing there's a fifth, the Economist, focused on who pays for the base layer. Builds on what we've been discussing here:
https://x.com/covenant_btc/status/2064337328936517670?s=20
Related topics
- how was k chosen in this case 2
- Bitcoin Core displaying coins (UTXOs) in a new tab 13
- Are you in favor of BIP-110? Let's get a Bitcoin poll going. 0
- Erlay seems to have some issues here’s a better proposal for a bitcoin protocol without invites 3
- New Optional Hourglass Implementation is Live 3
- Ways to earn some sats by contributing to bitcoin core development 5