BABY paired vs efficiency
Each row is a different BABY amount paired against the same BTC, shown as a % of the optimal (20,000 × BTC). Weight caps at your BTC amount — extra BABY past 100% adds nothing further. Your selected value is highlighted.
| BABY staked (% of optimal) | Weight (BTC-equiv) | Efficiency | BTC wasted |
|---|
The min() that decides who gets the bonus
Babylon's base BTC and BABY staking already pay their own yields. Co-staking is a third, separate pot — funded by 2.35% of annual BABY inflation — reserved for stakers who pair both assets from the same address in the right ratio. The mechanism is deliberately simple and deliberately punishing for mismatched pairs: your co-staking weight is w = min(BABY staked ÷ 20,000, BTC staked). Every 20,000 BABY you stake unlocks 1 BTC-equivalent of weight, but the moment your BABY runs out relative to your BTC, the min() clamps your weight at whatever BABY can cover — the rest of your BTC sits there, fully staked, fully exposed to finality-provider slashing risk, earning zero co-staking bonus. There is no partial credit curve and no soft cap; it is a hard ratio gate. This calculator prices that gate directly: your exact efficiency percentage, how much BTC weight you're leaving on the table, and — using your own assumptions for how contested the pool is — roughly what the bonus is worth in dollars. If you haven't already, size the base BABY yield itself with the Babylon BTC staking calculator, or compare the whole native-BTC-staking path against running infrastructure yourself with the validator vs pool calculator.
The math
Let B be BTC staked to an active finality provider and Y be BABY staked from the same address. The protocol's co-staking factor is a fixed constant R = 20,000 — every 20,000 BABY makes 1 BTC eligible. Your co-staking weight is w = min(Y⁄R, B), expressed in BTC-equivalent units. Your efficiency is w⁄B × 100: 100% means every BTC you staked is earning the bonus, 50% means half of it is dead weight. The BABY amount needed for full efficiency is simply B × R; any BABY beyond that is not wasted (it still earns Babylon's normal BABY staking yield) but adds nothing further to w, since the min() is already pinned at B.
Rewards are distributed as your reward = pool × (w ⁄ total weight of all co-stakers). This calculator asks you to estimate the two pieces you can't look up on-chain in advance — the combined weight of every other co-staker, and the pool's annual USD value — so it can turn your share into a projected annual reward and an implied APR on your staked BTC's dollar value. Because network-wide participation isn't fixed by the protocol, treat that reward estimate as a sensitivity check under your stated assumptions, not a guaranteed number; the efficiency percentage above it, by contrast, is exact and follows directly from the published formula, independent of what anyone else stakes.
FAQ
What is Babylon BTC-BABY co-staking, and how is it different from regular BABY staking? Co-staking is a second, separate reward layer on top of Babylon's base BTC and BABY staking. To qualify, you delegate BTC to an active finality provider AND stake BABY from the same address. The protocol then computes a co-staking weight for you — a BTC-equivalent score capped by how much BABY you paired against your BTC — and that weight competes for a share of a dedicated co-staking reward pool (funded by 2.35% of annual BABY inflation). Regular BABY staking pays you for locking BABY alone; co-staking pays extra specifically for pairing the two assets in the right ratio, on the theory that stakers with skin in both BTC security and BABY governance are the ones the protocol most wants to reward.
How exactly is the co-staking weight and ratio calculated? The formula is w = min(BABY staked / 20,000, BTC staked). Every 20,000 BABY you stake makes 1 BTC of your delegation eligible for co-staking rewards — that 20,000 figure is Babylon's fixed co-staking factor. So 1 BTC paired with 20,000 BABY gives a weight of exactly 1 (100% efficient); 1 BTC paired with only 10,000 BABY gives a weight of 0.5 (50% efficient, half your BTC earns nothing extra); and 0.1 BTC paired with 2,000 BABY also hits 100% efficiency, because the ratio, not the absolute size, is what matters. Your share of the total reward pool is then your weight divided by the sum of every co-staker's weight.
What happens if I stake more or less BABY than the optimal ratio? Understaking BABY relative to your BTC directly wastes BTC weight: the min() in the formula caps your co-staking weight at BABY/20,000, so any BTC beyond that ratio earns zero co-staking reward even though it's still locked and still exposed to slashing risk. Overstaking BABY beyond the 1:20,000 ratio is not penalized, but it is also not rewarded on the co-staking side — the formula caps weight at your BTC amount, so extra BABY past the optimum adds no further co-staking weight. That excess BABY still earns Babylon's regular BABY staking yield, just not the co-staking bonus, so it is inefficient capital allocation rather than a loss.
Do my BTC and BABY delegations need to be linked to the same address to get co-staking rewards? Yes, and this is a hard requirement, not a suggestion. Babylon's co-staking module only counts a BABY delegation toward your weight if it was staked from the same BABY address that is credited as the staker on your BTC delegation. If you split the two across different wallets — for example staking BTC through one address and BABY through another for tax, custody, or exchange-related reasons — the protocol computes zero co-staking weight for you, even if the total amounts would otherwise hit 100% efficiency. Always verify both legs are staked from the identical BABY address before assuming you qualify.