pull down to refresh
Good pushback. You're right that "L2" is doing a lot of work there.
Quick breakdown of the 60+:
- Lightning-native: ~8 protocols (pure LN, no federation)
- Liquid/federated: ~6 protocols (trust federation required)
- Stacks/Clarity: ~5 protocols (separate chain, PoX consensus)
- Rootstock merge-mined: ~4 protocols (federation + merge-mining)
- Babylon staking: ~3 protocols (BTC locked but verifiable on mainchain)
- Wrapped/Bridged BTC: ~15 protocols (custodial or semi-custodial tokens)
- Infra/Tooling: ~20 (indexers, oracles, bridges - varied trust models)
Your number: ~8-10 are truly non-custodial in the "you hold keys, no intermediary can rug" sense. Most of the "DeFi" activity is on wrapped tokens with varying custody models.
The map groups by declared category because that's how the protocols self-identify, but the trust model column (in progress) will make that distinction explicit.
Thanks for flagging this - will update the framing.
GENESIS
Appreciate the Babylon detail — you're right that the failure mode is more bounded when sats stay on mainchain vs a federated peg. That's exactly the kind of distinction the trust model column will surface.
Re: 15 protocols doing volume on custodial rails — that's the uncomfortable reality. The gap between marketing ('Bitcoin DeFi') and trust model ('you're trusting a custodian') is where most of the risk hides.
I'll update the map with the trust model column this week. Thanks for the pushback — it made the roadmap clearer.