Kernel restaking was publicly placed into wind-down on March 7, 2026, as outlined in our update Important Update for the Kernel Community. New deposits have been paused since, and Kernel is in a claims-only state. Moving forward, Kernel unstaking via BscScan will be supported for three years, through June 8, 2029.

This post explains a minor operational change: the Kernel dApp interface is being retired, and from that point holders will claim directly through the Kernel StakeManager contract on BscScan. Nothing about your ability to withdraw changes.

What is changing

• The Kernel dApp UI will be retired on or around June 8, 2026. After that, holders claim directly through the Kernel StakeManager contract on BscScan.

• Between June 3 and June 10, 2026, a scheduled upgrade is being performed on the Kernel StakeManager contract. Claims continue uninterrupted before, during, and after the upgrade. The exchange rate is fixed at the prevailing rate.

These are operational steps. They do not affect the backing of your assets or your ability to claim them.

Operational support window

Kernel unstaking via BscScan will be supported for three years, through June 8, 2029. We encourage holders to claim within this window.

How to claim via BscScan

Once the dApp UI is retired, you can withdraw your assets directly on-chain using BscScan. All Kernel-supported assets are withdrawn through a single contract:

Kernel StakeManager (proxy): 0xb32dF5B33dBCCA60437EC17b27842c12bFE83394

At a high level, the function you call depends on the asset you staked:

1. Native BNB — call unstakeNative(amount, referralId) on the StakeManager.

2. clisBNB — call unstakeClisBNB(amount, referralId) on the StakeManager.

3. All other supported assets (asBNB, slisBNB, BTCB, enzoBTC, pumpBTC, uniBTC) — first approve the StakeManager on the asset's token contract, then call unstake(asset, amount, referralId) on the StakeManager.

Set referralId to NA. Detailed, step-by-step instructions with screenshots are in the User Guide. If you prefer to use the dApp while it is still available, you can continue to claim there until it is retired.

Scope

This update concerns the Kernel restaking product only. Kelp (rsETH) and Gain (vaults such as hgETH and agETH) are separate KernelDAO products and are not affected — they continue to operate as usual.

Support

For any questions, contact us at claims@kelpdao.xyz - the single official support channel. We will never DM you first. Be cautious of anyone in DMs or comments claiming to represent KernelDAO; verify everything through claims@kelpdao.xyz.

----------------------------------------

FAQ

Are my assets safe?

Yes. Your assets remain fully backed and claimable on-contract. Kernel will be operationally supported for three years, through June 8, 2029.

How do I claim after the dApp UI is retired?

You claim directly through the Kernel StakeManager contract on BscScan. For Native BNB call unstakeNative; for clisBNB call unstakeClisBNB; for all other assets approve the StakeManager, then call unstake(asset, amount, referralId). The User Guide has detailed steps.

Is there a deadline to claim?

Kernel will be operationally supported for three years, through June 8, 2029. After that date, operational support for Kernel will end. We encourage you to claim within this window.

Are Kelp (rsETH) and Gain affected?

No. Kelp and Gain are separate KernelDAO products and continue to operate as usual. If you only hold rsETH or use Gain vaults, no action is required.

What about tax?

We cannot provide tax advice. Please consult a qualified tax professional regarding your own situation.

Who do I contact?

claims@kelpdao.xyz is the single official support channel. Do not trust DMs from anyone claiming to represent KernelDAO.