Lista Liquid Staking

Lista Liquid Staking issues a liquid staking token for BNB that appreciates against BNB in line with staking rewards. It held about $574M at the 2026-08-14 survey. The verdict is the chain’s, not an individual protocol finding. ListaStakeManager delegates through multiple validators, but bot-operated unbonding and rebalancing, a seven-day native exit, and Lista contract controls remain above BNB Smart Chain consensus. BSC’s own documentation describes Proof of Staked Authority with 21 Cabinet validators, and its October 2022 response to the Token Hub exploit included a coordinated chain halt. Under the standing rejected-chain rule, Lista’s protocol merits cannot make a BNB-native claim eligible.

Review triggers: events that reopen the verdict
• Deploys meaningful liquidity on a chain the registry approves
• The BSC verdict changes

Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.

The research file

The mechanism

A user deposits BNB into ListaStakeManager and receives non-rebasing slisBNB. Rewards from delegated validators increase slisBNB’s exchange rate against BNB. Lista documents delegation across multiple validators and a bot that rebalances stake for reliability and reward rates. slisBNB can be transferred, used as collateral or placed in liquidity pools, each of which adds separate liquidation or impermanent-loss risk.

Control and operating record

The stake manager, bot-driven validator allocation and Lista governance are protocol controls; audits reduce but do not eliminate their contract and key risk. Below them, BSC uses Proof of Staked Authority. BNB Chain currently documents 45 validators divided into 21 highest-stake Cabinets and 24 Candidates. Following the October 2022 BSC Token Hub exploit, BNB Chain reported that validators coordinated a temporary halt and later restart. That is direct operating evidence for the chain-level judgment.

The exit

Lista says a withdrawal request triggers a bot to unbond BNB; after the seven-day unbonding period slisBNB is burned and BNB becomes claimable. Selling slisBNB on a DEX can avoid the queue but exposes the holder to available depth, price discount and AMM risk. Both exits depend on BSC continuing to execute and finalize transactions.

Why the class rule decides

Because the underlying asset is native BNB and the staking manager operates on BSC, the settlement-chain dependency cannot be diversified away inside this product. This class memo does not assert that Lista failed an individual audit. Review reopens if BSC passes the chain framework or Lista creates material liquidity for a genuinely distinct claim settled on an approved chain.

Class rule

The rejected chain class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Lista Docs — slisBNB overview · primary · accessed 2026-08-14
  Supports: slisBNB overview
• Lista Docs — staking, rebalancing and withdrawal mechanics · primary · accessed 2026-08-14
  Supports: staking, rebalancing
• BNB Chain Docs — validator architecture · primary · accessed 2026-08-14
  Supports: validator architecture
• BNB Chain — October 2022 ecosystem update · secondary · accessed 2026-08-14
  Supports: October 2022 ecosystem update

Inherited controls

The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.