Bouncebit
Bouncebit BB staking delegated tokens to validators and represented positions with stBB
Bouncebit BB staking delegated BB to validators on the former proof-of-stake chain and issued stBB receipts. The chain’s announced sunset in August 2026 makes the original rules historical. Before a first commitment, distinguish stBB from BB on BNB Smart Chain; the migrated balance alone doesn’t establish an active delegation.
BB Delegation and Its Recorded Position
Reward participation came from BB committed through the liquid staking contract to a validator, while stBB recorded the delegated position. Validators recorded and verified network transactions, receiving transaction fees as staking rewards. Holding unstaked BB didn’t create that delegation relationship.
BB Committed to a Validator
The consensus mechanism tied committed BB to transaction validation, giving the stake a role in securing the network.
The stBB Receipt
stBB was the liquid staking derivative for BB, representing the stake while the underlying tokens remained committed. It didn’t turn a holder into a validator or certify that a separate yield strategy had accepted the position.
The position’s terms also covered redemption with a share of rewards and penalties. An stBB receipt represented delegated BB, while the eventual settlement determined the tokens returned.
BB, stBB and stBBTC
BB was the asset used in the former validator mechanism, stBB represented staked BB and stBBTC represented staked BBTC. Bitcoin-related staking descriptions didn’t make a BB delegation into a BBTC position. For an older receipt, the applicable staking terms determine the associated rewards and redemption process.
How Did Epochs Shape BB Rewards?
The former chain used 24-hour epochs to organize validator selection and BB reward distribution, with rewards allocated at epoch closure. The epoch schedule didn’t establish a fixed amount of income for every position or an instant withdrawal at each boundary.
Selection of Active Validators
Validator selection used voting weight that took account of the BB staked by the node operator. Governance determined the maximum size of the active validator set.
The reward cycle answered when the network distributed rewards; the redemption process governed when a staking position could return its underlying tokens.
Commission and Validator Performance
Validators could charge a commission on staking rewards to support their operating costs. The charge affected reward distribution, so the amount that a position earned depended on its applicable commission terms. A validator’s reward figure and a holder’s proceeds could differ after that charge. Under the legacy delegation rules, a validator punished for poor performance earned no staking rewards for that epoch, affecting its delegators.
Validator Rewards and CeDeFi Yield
BB-denominated rewards also appeared in the former CeDeFi model, where specific subscriptions combined strategy yield with node staking rewards. Farm participants could stake eligible BB-Tokens to earn stBB funded by a portion of node staking yield. Receiving that reward didn’t mean the recipient had personally delegated BB. A BBUSD strategy subscription and an stBB delegation had different participation conditions.
The former BTC arrangement first staked BBTC to a node, then used stBBTC for a CeDeFi yield subscription. Its funding rate arbitrage yield accompanied node staking rewards. Funding payments and node rewards came from distinct mechanisms. Separately, subscribing to a USDT CeDeFi strategy with BBUSD on the former chain automatically earned BB rewards. An stBB balance alone didn’t establish participation in either arrangement.
How Did stBB Redemption Work?
The legacy Liquid Staking Token documentation described a request followed by a 24-hour wait before the holder could claim the underlying tokens. Settlement included the position’s share of rewards and penalties. Requesting redemption began the exit; it didn’t itself return spendable BB.
BounceBit Earn’s Subscription & Redemption Rules separately described a 7-day unstaking period for claimed stBB rewards. The 24-hour rule specified the interval before claiming under the original arrangement, without establishing a present-day recovery deadline. Following the announced chain sunset, those legacy terms don’t establish an available claim route. An existing stBB position needs an applicable settlement arrangement; a migrated BB token balance doesn’t answer that separate question.
The Chain Sunset and BB Migration
The August 31, 2026 announcement reported the decision to permanently sunset the chain following a hacking incident. Binance had suspended mainnet BB deposits and withdrawals on August 20, 2026 at 02:00 UTC. It scheduled BNB Smart Chain deposits and withdrawals for September 2, 2026 at 07:00 UTC.
The announced BB migration to BNB Smart Chain specified a 1:1 swap ratio. That change concerned the BB token’s network and contract. Validator selection, the liquid staking contract and an existing stBB position were separate parts of the former system. Token support on another network doesn’t by itself restore those parts or their reward mechanism.
Can a BB Balance Establish a New Staking Position?
A BB balance alone doesn’t establish access to a replacement staking route after the announced chain sunset. For a first inspection, identify the holding’s token contract and network without signing a transaction. An old stBB entry represented BB delegated on the former chain; BEP20 BB identifies the migrated token format.
- Identify whether the holding is BB, stBB or stBBTC, keeping each receipt attached to its underlying asset.
- Distinguish a former-chain delegation record from a BB balance on BNB Smart Chain.
- Identify the network and contract that any proposed new staking authorization would use.
- Read how that arrangement would record participation, distribute rewards and return the committed BB.
- Stop before authorization if the available terms only describe the former chain’s staking contract.
Reading an existing position doesn’t create another stake or move its tokens. Until a replacement arrangement establishes its own participation and exit terms, the assessment can stop before any authorization.
Planned Security Uses Beyond Delegation
The original liquid staking design proposed a later restaking use for its derivatives to contribute security beyond the original validator delegation.
stBB represented delegated BB under its original terms; it didn’t establish participation in the proposed restaking arrangement. The future design named its intended security recipients Shared Security Clients (SSC).
Bouncebit BB staking: what people ask
Could a First BB Delegation Be Made Without Running a Node?
The former liquid staking model let BB holders delegate through a smart contract without operating a validator node. Node operators performed the validation work, while stBB represented the holder’s delegated BB. After the announced chain sunset, those legacy rules don’t establish an available first delegation. When holders delegated BB through that contract, the resulting stBB receipt represented their stake without making them active validators.
Was a Minimum BB Holding Required Under the Former Consensus Rules?
The former consensus rules stated no minimum token-holding requirement. That statement doesn’t establish that every staking interface had no deposit minimum, and it doesn’t make historical delegation available after the announced chain sunset.
What Happened to Unselected Node Operators?
Node operators that weren’t selected for the active set entered the candidate set for reevaluation in the next epoch. This was part of the former chain’s validator selection process. Voting weight took account of the operator’s staked BB, while governance controlled the maximum active set size.
Does a 1:1 BB Swap Mean One stBB Must Redeem for One BB?
The announced 1:1 ratio applied to the BB token migration, not the settlement of an stBB staking receipt. The former liquid staking terms allowed redemption for the staked tokens with a share of rewards and penalties. The migration ratio doesn’t set its final redemption amount or establish a currently functioning stBB claim route.
Did the Swap Notice Confirm That stBB Delegation Would Continue?
No. Binance’s notice said Binance Earn, spot, margin and futures services wouldn’t be affected during the contract swap. It didn’t confirm that the former chain’s liquid staking contract would continue operating or that an exchange balance represented an stBB delegation.