How PoX-5 pays out
The waterfall, bond payout order and reserve, as the deployed pox-5 contract implements them.
Line numbers refer to the deployed pox-5 source, which is identical to stacks-core tag 4.0.1 (commit 62e03cc). A copy is in the repository at research/pox-5.deployed.clar.
Distributions
Once per distribution interval (1,050 Bitcoin blocks, two per reward cycle), anyone may call calculate-rewards. The sBTC that reached pox-5 since the previous call is the gross pool for that interval. The call is booked to the reward cycle that contains its calculation height, which is the last block of the interval.
The waterfall
Bonds first
Each active bond is owed a target for the interval: shares × target-rate ÷ 10000 ÷ 50 (pox-5 L2266). Each bond receives min(target, what is left) (pox-5 L2269-2272).
Reserve: 15% of the remainder
After bonds, 15% of what remains goes to the reserve (pox-5 L2190, RESERVE_RATIO u1500). If no STX is staked that cycle, the whole remainder goes to the reserve.
STX-only stakers: the rest
The other 85% is shared flat per uSTX among STX-only stakers (pox-5 L2191-2201).
Bond order
Bonds are paid in descending stx-value-ratio, with ties going to the lower bond index. The contract enforces this: a call with bonds in the wrong order fails with ERR_INVALID_BOND_PERIOD_ORDERING (pox-5 L2285-2299). Within a bond, rewards are flat per staked sat (pox-5 L2276-2279, pox-5 L2304-2309): no staker in a bond is paid before another.
So when the pool is short, the bond paid last in this order is the first to be short-paid.
The reserve: a back-stop, not an automatic one
The reserve is designed as a back-stop for bonds: "The reserve exists to buffer protocol bond shortfalls" (Stacks docs, Rewards and tranches).
In this first iteration it can't be drawn automatically. transfer-from-reserve (pox-5 L2696) is private and uncalled, and using the reserve goes through a SIP process (pox-5 L2692-2694). Automatic responses are anticipated for PoX-6 (Stacks docs). In a shortfall the reserve deposit is zero, so the reserve stays flat: it does not drain.
Why this matters for the metrics
Because it cannot be drawn automatically today, Metacenter does not count the reserve as protection already in place. It shows it as hypothetical cover: how many cycles of obligation it would equal at today's sizes, if the SIP process made it payable.