# [BTCFi Series 9] Babylon: TVL Up, Yields Thin

> Babylon secures ~$5.6B in native BTC with a token worth ~$78M. The unit economics of Bitcoin security-as-a-service, and why realized yield stays thin.

- Source: https://www.steadyrain.xyz/en/articles/babylon-bsn-reality-check-2026/
- Publisher: Steady Rain
- Author: 0xYatha
- Published: 2026-09-30T04:19:55.470Z
- Categories: BTCFi, DeFi
- Language: en

## Introduction

In mid-May 2026, Babylon's staking vaults held 56,853 BTC, worth roughly $5.64 billion at the prices used in that snapshot. The token that compensates those stakers, BABY, carried a circulating market capitalization of about $78 million on the same date. The asset paying for the security is worth roughly 1.4% of the collateral it is paying for.

That ratio is the central tension, and it does not resolve by pointing at growth. Babylon has the growth. More than 250 finality providers operate on Babylon Genesis. Phase 3 multi-staking has begun rolling out to the first Bitcoin Secured Networks, with Corn, BOB and Pell Network named in Babylon's own ecosystem materials. No slashing incident has been reported, though none of the sources we reviewed independently verifies that absence rather than simply omitting one. BABY traded near $0.020 in May 2026, up about 30% on the week from a March 2026 low of $0.0107, and still roughly 88% below the $0.1661 all-time high set in April 2025.

The reported TVL itself is not settled. Cryptonomist reported Babylon crossing $4 billion in TVL on 15 May 2026, describing it as one year after launch. Phemex, writing in the same month, reported 56,853 BTC at $5.64 billion. Neither source reconciles with the other. The gap is most plausibly a difference in snapshot date, BTC price assumption, or whether Phase 1 locked deposits and Genesis-delegated stake are counted together, but we could not confirm which. Anyone modelling Babylon's economics should treat the $4B to $5.6B band as the honest range rather than picking the larger figure.

Pricing Babylon's core offering reveals the structural constraint. Bitcoin-denominated economic security is abundant and nearly costless to supply. The constraint on this business was never collateral. It is whether any network will pay a real price for it.

## From locked UTXOs to a shared-security marketplace

*[Figure: img1]*

Babylon's three phases are often described as a sequence of releases. They are better understood as three distinct products stacked on the same collateral base.

Phase 1, the Bitcoin locking phase, established the core cryptographic claim. A holder locks BTC into a staking script on the Bitcoin chain itself. There is no wrapping, no bridge, and no custodian holding a redemption liability. The UTXO stays on Bitcoin, encumbered by a covenant-style contract that defines a slashing spend path and an unbonding path. Phase 1 ran in capped deposit rounds and accumulated over 57,000 BTC from 135,290 unique stakers, which Babylon's documentation frames as roughly 0.2% to 0.3% of circulating Bitcoin depending on the snapshot. That phase produced no yield in itself. It produced points, positioning, and the liquid staking tokens built on top of it, of which Lombard's LBTC became the largest.

Phase 2 launched Babylon Genesis, a Cosmos SDK chain with a dual security model. Two separate stakes secure two separate functions. BABY stakers delegate to CometBFT validators, who produce blocks. BTC stakers delegate to finality providers, who sign finality votes on those blocks. A block is not final until finality providers representing sufficient BTC weight have signed it. The Bitcoin-backed layer therefore does not order transactions; it ratifies an ordering produced by a token-weighted validator set. Separately, Babylon Genesis checkpoints its own state into Bitcoin transactions, which gives light clients an objective ordering to fall back on and closes the long-range attack surface that pure proof-of-stake chains carry.

Phase 3 generalizes the finality layer. The same locked BTC can be delegated to finality providers serving other chains, the Bitcoin Secured Networks, with Babylon Genesis acting as the control plane that registers BSNs, tracks delegations and routes rewards. Lombard's March 2025 explainer describes this as a marketplace for shared security, which reflects promotional framing from a party that earns fees on Babylon's success, but the mechanical description is accurate enough. A BSN registers, finality providers opt in, BTC stakers delegate, and the BSN's rewards flow back along the same path.

The architectural achievement is real and narrow. Babylon has made Bitcoin capable of carrying a slashable commitment without leaving Bitcoin. What it has not yet demonstrated is a buyer who pays a meaningful price for that commitment.

## What the first BSNs pay, and where disclosure stops

*[Figure: img2]*

We could not find, in Babylon's documentation, in Lombard's ecosystem materials, or in the secondary coverage we reviewed, any figure for what Corn, BOB or Pell Network remit for Babylon security. Not an amount, not a rate, and not an asset denomination. The topic brief that prompted this analysis also lists Manta as an early BSN; we found no corroboration of that in any primary or secondary source and treat it as unconfirmed.

This is not a minor documentation gap. It is the single number that determines whether Babylon is a services business or a subsidy program, and its absence is itself informative. A security marketplace with real revenue tends to publish its revenue, because revenue is the argument. When a protocol publishes TVL, finality provider counts and integration announcements while leaving the fee schedule unstated, the most parsimonious reading is that the fees are small enough that stating them would undercut the other numbers.

Consider what an early BSN is economically. Corn, BOB and Pell are young networks with their own token supplies, their own treasuries and their own need to bootstrap. They are not cash-rich entities shopping for security the way a bank shops for custody. The plausible structures available to them are payment in their own native token, payment in ecosystem allocation or points with future conversion, or reciprocal arrangements where the BSN receives a Babylon integration and Babylon receives distribution. Each of those makes the BSN a net consumer of subsidy rather than a source of it. If BSNs paid in stablecoins or BTC, that would be a strong signal and it would almost certainly be advertised.

So the reward reaching BTC stakers today is overwhelmingly BABY. Babylon's own documentation states that Phase 2 introduces base staking rewards, language that describes issuance rather than fee distribution. BABY's initial supply is 10 billion tokens with, per the same documentation, no hard cap. Phemex reported 3.87 billion of 10.76 billion tokens circulating in May 2026, roughly 36%, with approximately 6.9 billion still to enter circulation through team unlocks, ecosystem grants and staking rewards.

The distinction between revenue and dilution matters because the two behave differently under stress. Fee revenue paid in an external asset is a transfer from BSN users to BTC stakers and is roughly price-independent from the security token. Emissions paid in the security token are a transfer from existing token holders to stakers, and their value collapses exactly when the token does. A yield funded by emissions is a yield whose denominator moves against the staker in every bad state of the world.

## The arithmetic of a BABY-denominated yield

*[Figure: img3]*

No source we reviewed publishes an audited, BTC-denominated realized APY for Babylon stakers, so we will not assert one. The emission schedule allocated specifically to BTC stakers is also not broken out in the materials available to us. What can be established is the size of the budget from which any yield must come, and that bound is severe.

Take the staked base at the more generous figure, $5.64 billion. A 0.5% BTC-denominated annual yield on that base requires distributing about $28 million of value to BTC stakers over a year. Against BABY's roughly $78 million circulating market capitalization in May 2026, that is close to 36% of the entire circulating float, distributed annually, to one claimant group. At 1%, it approaches 72%. Measured against the fully diluted valuation of roughly $217 million, a 0.5% yield still consumes around 13% of the token's total worth every year.

Now look at the stock rather than the flow. The approximately 6.9 billion BABY tokens not yet circulating are worth about $138 million at $0.020. That is every remaining token, including the portions earmarked for team vesting and ecosystem grants that will never reach BTC stakers. Even under the fiction that the entire unissued supply were paid to BTC stakers and nothing else, the total is under 2.5% of the value of the Bitcoin currently staked. That is a one-time amount, not an annual rate.

There is a reflexive loop inside this. Emissions denominated in BABY are sold by rational stakers into a market whose capitalization is a small fraction of the collateral base. Selling pressure depresses the price, which depresses realized yield, which is answered by higher nominal emissions if the protocol targets a headline APY, which increases selling pressure. The loop is not unique to Babylon. It is more acute here than in most cases because the ratio of secured value to token value is unusually extreme. Ethereum's validators are paid in the asset they are securing. Babylon's BTC stakers are paid in an asset with no claim on the collateral and, so far, no demonstrated claim on external fees.

### Why anyone stakes anyway

The thin yield does not make staking irrational, and this is where the bear case must concede a key mechanism.

A BTC staker on Babylon does not sell, wrap, or transfer the BTC. The coin stays in a UTXO the staker controls, encumbered but not surrendered. The real costs of staking are the slashing risk on the covenant path, the liquidity cost of the unbonding delay, and the operational risk of interacting with the staking script correctly. For a holder with a long horizon and no intention of moving the coin, those costs are close to zero. When the marginal cost of supplying a factor is near zero, the market clears at a near-zero price. Thin yield on Babylon is not a pricing failure. It is the correct price for an abundant input.

The composition of stakers reflects this. Liquid staking token issuers derive their economics from LBTC's circulation and DeFi integration rather than from BABY rewards, so BABY's drawdown barely touches their business case. Holders farming prospective BSN allocations are underwriting an option on future airdrops, not a coupon. Treasuries and long-horizon holders with structurally idle BTC take whatever accrues. None of these participants needs the yield to be good. They need it to be non-negative.

That is a durable supply base and an informative fact about TVL persistence. It is also why TVL cannot be read as evidence of product-market fit. Babylon's supply side is oversubscribed at prices approaching zero. The binding constraint is demand from BSNs willing to pay, and nothing in the current data shows that constraint loosening.

## Slashing that can only punish equivocation

*[Figure: img4]*

Babylon's slashing enforcement is the strongest engineering claim in the stack and the most misunderstood in comparison to Ethereum restaking.

Finality providers sign with Extractable One-Time Signatures. An EOTS key can safely sign one message per height. Sign two conflicting messages at the same height and the two signatures together algebraically reveal the private key. Once revealed, anyone can construct the transaction that spends the slashing path of the delegators' Bitcoin UTXOs. No committee votes, no oracle reports, no governance action. The penalty is a consequence of the cryptography and the enforcement is permissionless, executed on Bitcoin against Bitcoin UTXOs.

This is objectively enforceable in a way that few slashing systems are. It is also extremely narrow. EOTS extraction punishes exactly one fault: equivocation at a height. It cannot punish a finality provider that simply stops signing. It cannot punish censorship, because refusing to sign a valid block is indistinguishable at the signature layer from being offline. It cannot punish a provider that signs a technically valid but semantically harmful state, because validity is what the signature attests to. A BSN buying Babylon security is buying insurance against double-finalization and nothing else.

EigenLayer's design sits at the other end of this tradeoff. Slashing conditions there are defined per service and enforced by Ethereum contracts, which permits a much broader fault set, including conditions that are subjective and require an attestation or dispute process to adjudicate. Broader coverage, weaker objectivity. Babylon's coverage is minimal and its objectivity is close to absolute. Neither is strictly better; they answer different questions about what a service actually needs protection against. For a rollup worried about liveness or censorship, Babylon's mechanism is not the relevant instrument.

The severity parameter is where we hit a documentation wall. The brief prompting this analysis cites a 0.1% penalty for double-signing. We could not corroborate that figure, or any figure, in Babylon's documentation or the secondary coverage we reviewed, and the sources that describe slashing say only that a portion of delegated BTC is burned. The ambiguity is not cosmetic. If a double-sign burns 0.1% of the delegation, then a finality provider controlling meaningful BTC weight faces a penalty that could be trivial relative to the value of a successful attack on a BSN with a large bridge. If it burns a much larger share, the economics invert. A security buyer cannot price protection without knowing the penalty, and the fact that the penalty is not prominently published is a real obstacle to the enterprise-grade positioning Babylon has pursued since raising roughly $96 million from Polychain Capital, Hack VC, Galaxy Digital, OKX Ventures and others, with audits from Coinspect, Zellic and Cantina.

## Multi-staking adds reward streams and fault domains together

*[Figure: img5]*

Phase 3's proposition is that one BTC delegation can secure several BSNs and earn from each. The reward side of that statement is straightforwardly additive. The risk side is where the analysis must be careful, because additivity there depends on a correlation assumption that the architecture works against.

Slashing exposure across BSNs is not diversified in the portfolio sense. The same UTXO backs each commitment, so a fault at any one BSN reaches the same collateral. Adding the second and third BSN adds independent chances to be slashed against a collateral base that does not grow. In expectation that is fine if the per-event penalty is small and the fault probability is genuinely independent across networks. Independence is the assumption that deserves scrutiny.

The fault being punished is equivocation by a finality provider, and equivocation is overwhelmingly an operational failure rather than a strategic choice. Duplicate signing processes after a failover, a restored snapshot that replays old state, a key management error during migration. If the same operator runs finality provider instances across Corn, BOB and Pell Network using shared infrastructure and shared key material, then a single operational incident produces equivocation on several BSNs simultaneously. The economic fault domains are distinct; the operational fault domain is one. We have no public data on the degree of finality provider overlap across BSN sets, and that overlap is the single most important input to whether multi-staking is diversification or leverage.

The counterargument deserves a fair hearing. BSNs have genuinely distinct applications, users and revenue models, so a BTC staker collecting rewards from several of them is less dependent on any one network's survival than a staker exposed to Babylon Genesis alone. That is real diversification of the reward stream. The point is that reward diversification and fault diversification are different properties, and Phase 3 delivers the first much more cleanly than the second.

Concentration in the provider set compounds this. Lombard was, as of March 2025, the largest finality provider on Babylon with over 40% of all staked BTC delegated to it, 22,508 BTC split between 15,038 BTC arriving via LBTC and 7,470 BTC delegated directly. We found no updated figure for 2026, and the count of 250-plus finality providers says nothing about how stake is distributed among them. If anything close to a 40% share persists, then a single operator's signing infrastructure sits astride a plurality of the Bitcoin securing the network, and multi-staking propagates that operator's operational risk into every BSN it serves. The absence of a current concentration disclosure is, again, the part that should concern an analyst more than any particular number.

## What would settle the question

Babylon has built the cryptography. The EOTS construction and Bitcoin-native slashing path solve a problem that BTCFi spent years unable to solve without a bridge or a custodian, and the self-custodial property is why 56,853 BTC were willing to show up at a yield that rounds to nothing. That should not be discounted.

What remains unbuilt is the revenue side, and a handful of specific disclosures would resolve most of the ambiguity in this analysis.

- The BSN fee schedule. What Corn, BOB and Pell Network remit, in what asset, on what cadence. A single stablecoin- or BTC-denominated payment from an operating BSN would change the character of the argument more than another billion dollars of TVL.
- A split of staker rewards between BSN-paid fees and BABY issuance. Until that split is published, every advertised APY figure is unauditable.
- The BABY unlock schedule against the roughly 6.9 billion tokens still to enter circulation, with the portion earmarked for BTC staker rewards identified separately from team and ecosystem allocations.
- The slashing parameter, stated numerically, with its base and its trigger conditions.
- Current finality provider concentration, so that the 250-plus provider count can be read as something other than a headcount.

Babylon's roadmap suggests management sees the revenue problem. The publicized Aave V4 integration, which would let native BTC collateralize stablecoin borrowing through zero-knowledge proofs of Bitcoin state rather than through a bridge, points toward fee income that does not depend on BSN willingness to pay. The supporting claim that on-chain ZK verification costs have fallen from around $15,000 to $10 to $20 per proof comes from the company's own framing and we have not seen it independently verified, but if verification is genuinely that cheap, lending demand is a far deeper market than shared security. The Babylon Foundation's $3 million USDT deposit into Aave in May 2026 is small, though it is at least denominated in something other than its own token.

The condition to watch is not TVL and not BABY's price. It is the first BSN payment made in an asset Babylon does not issue. Until then, the 1.4% ratio between BABY's market capitalization and the Bitcoin it coordinates is the most accurate available statement of what the market thinks Bitcoin-backed security is currently worth.

## References

- [Babylon Genesis Overview, Babylon Labs documentation](https://docs.babylonlabs.io/guides/overview/babylon_genesis/)
- [What Is Babylon (BABY), Phemex Academy, May 2026](https://phemex.com/academy/what-is-babylon-baby-bitcoin-staking-protocol)
- [Babylon Bitcoin staking hits $4 billion TVL milestone, Cryptonomist, 15 May 2026](https://en.cryptonomist.ch/2026/05/15/babylon-bitcoin-staking-4-billion-tvl/)
- [BABY, Babylon Genesis, and BSNs, Lombard Finance, March 2025](https://www.lombard.finance/blog/baby-babylon-genesis-and-bs-ns-babylon-s-3-phases-explained/)