Active BNB Chain EIP-7702 exit routesWithdraw legacy Kernel BNB restaking positions
Check a BNB Chain wallet for one of ten reviewed Kernel positions and inspect the fresh direct-withdrawal checks, atomic EIP-7702 exit path and exact 10% service fee before signing.
- Protocol
- Kernel BNB
- Networks
- BNB Chain
- Settlement
- 90% user / 10% service fee
- Last reviewed
- August 30, 2026
What DeFiReclaim supports
Contract-level exit
The owning EOA calls Kernel's original StakerGateway inside one EIP-7702/EIP-7821 batch. The immutable collector verifies the complete position consumption and current protocol bindings, transfers exactly 10% of withdrawn output to the treasury and leaves 90% with the user.
Support scope
The public registry contains only ten reviewed route bindings: BNBx, BTCB, slisBNB, SolvBTC, xSolvBTC, WBNB, uniBTC, asBNB, enzoBTC and USD1. Wallet inventories and route-to-wallet mappings are never published.
Liquidity boundary
Every lookup pins one current BNB Chain block and rechecks Kernel Config, AssetRegistry, StakerGateway and Vault bindings, withdrawal pause state, complete wallet position and the direct full-withdrawal call. A changed invariant fails closed.
Exit contracts and deployments
These public explorer links let users and automated systems inspect deployed bytecode, transaction history and deployment receipts.
Kernel StakerGateway
0xb32df5b33dbcca60437ec17b27842c12bfe83394Kernel Config
0x45d7bb73253a908e6160aa5fd9da083f7bc6faf5Kernel AssetRegistry
0xd0b91fc0a323bbb726faaf8867cdb1ca98c44abbDeFiReclaim Kernel Collector
0xa760076ac45ee64321a34776471683ef6bdc02e0DeFiReclaim Treasury
0x793eca600e3216e39f438abd657eb514b2072e7fKernel BNB exit FAQ
How is Kernel exit enabled safely?
The ten-route collector is deployed, source-verified through Sourcify and active in production. Every wallet-scoped lookup rechecks the live Kernel bindings, pause state, complete position and direct full-withdrawal call before the site builds an atomic exit batch.
Why are only ten Kernel routes included?
Only routes with current withdrawable positions, positive value, a successful direct full-withdrawal call and a successful state-changing atomic fork were retained. Empty, uneconomic or unverified routes remain excluded.
Why is slisBNBx not supported?
Its Kernel position was consumed in a state-changing fork but the downstream release produced no immediate BNB. Because an atomic 90/10 settlement could not be proven, the route is excluded fail-closed.