> For the complete documentation index, see [llms.txt](https://kerneldao.gitbook.io/kernel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kerneldao.gitbook.io/kernel/getting-started/kernel-deprecated/important-update-for-the-kernel-community.md).

# Important Update for the Kernel Community

The Kernel Dapp UI is being retired as part of our ongoing product evolution. Importantly, **Kelp's retaking and Gain products continue to operate as usual, with no changes.**

Over the past four seasons, you’ve played a key role in building a shared security protocol on BNB Chain — and we’re deeply grateful for that support. As Kernel enters its next chapter with the launch of KUSD, focused on the $250T supply chain financing opportunity, we are streamlining our product suite to better serve this vision.

Nothing changes at the protocol level. The underlying smart contracts remain fully live and functional.

**Your assets remain safe, secure, and fully withdrawable at all times.**

#### Key dates

* **28 February 2026** - End of points issuance (Season 4 was the final season)
* **27 March 2026** - Kernel dApp is sunset.
* After **27 March 2026** - Withdraw directly from smart contracts via BscScan (this guide remains the permanent path)

#### What’s changing

* The frontend is shutting down - the restaking interface will no longer be accessible
* Deposits are paused - no new assets can be staked
* Points are discontinued - no issuance after 28 February 2026

#### What remains

* Smart contracts stay live
* All assets remain safe
* Withdrawals are always available via smart contracts

### How to Withdraw&#x20;

Withdrawals are now handled directly through the smart contracts. Follow the steps below carefully to access your funds.

Need help? Reach out to the team for support.

Before you start, please ensure you have access to the following:&#x20;

* The wallet you used to deposit into Kernel
* Some BNB in that wallet for gas fees

#### Step 1: Get your asset’s contract address

Find the contract address for the asset you want to withdraw.

The full list is at the end of the doc.

#### Step 2: Check your exact balance

1. Go to the "Read as Proxy" contract page on BscScan:[ Click Here](https://bscscan.com/address/0xb32dF5B33dBCCA60437EC17b27842c12bFE83394#readProxyContract#F2)
2. Find balanceOf  (0xf7888aec)
3. In the asset (address) field, paste the address of the asset you found from the list at the end of the doc.\
   \*Note: You must check the balance for the specific assets you deposited into Kernel. If you deposited multiple different assets, you will need to repeat this entire balance check process for each individual asset.
4. In the owner (address) field, paste your own cryptocurrency wallet address. Important: This must be the exact same wallet address that you originally used to deposit your assets into Kernel.
5. Click the "Query" button.
6. Directly below the button, a uint256 response will appear. This is your full deposited balance for that specific asset, perfectly formatted for the smart contract (your actual amount multiplied by 10^18).

\*Withdrawing multiple assets? Repeat this step for each one.&#x20;

<figure><img src="/files/zYhJuKVKoImaeo9ktRBd" alt=""><figcaption></figcaption></figure>

#### Step 3: Connect your wallet

You must connect your wallet to BscScan to authorize the withdrawal.

1. Switch over to the "Write as Proxy" tab:[ Click Here](https://bscscan.com/address/0xb32dF5B33dBCCA60437EC17b27842c12bFE83394#writeProxyContract)
2. Click the "Connect to Web3" button (located just above the function panels, indicated by a red dot).
3. Your wallet will pop up. Select the wallet address that holds your deposited Kernel assets and click "Connect". The dot will turn green once connected.

<figure><img src="/files/LScq81LPcYjW6pxQGmc9" alt=""><figcaption></figcaption></figure>

#### Step 4: Withdraw

Scroll down the "Write as Proxy" page and choose the correct function based on the asset you are withdrawing.

**For Native BNB:**

1. Find and expand the [unstakeNative](https://bscscan.com/address/0xb32dF5B33dBCCA60437EC17b27842c12bFE83394#writeProxyContract#F8) function.
2. In the amount (uint256) field, paste the exact amount of Native BNB balance you have deposited in Kernel. You must use the complete number you copied from your Native BNB balance query in Step 2.
3. In the referralId field, type NA.
4. Click the "Write" button and confirm the transaction in your wallet.

**For clisBNB:**

1. Find and expand the [unstakeClisBNB](https://bscscan.com/address/0xb32dF5B33dBCCA60437EC17b27842c12bFE83394#writeProxyContract#F7) function.
2. In the amount (uint256) field, paste the exact amount of clisBNB balance you have deposited in Kernel. You must use the complete number you copied from your clisBNB balance query in Step 2.
3. In the referralId field, type NA.
4. Click the "Write" button and confirm the transaction in your wallet.

**For All Other Assets:**

1. Find and expand the [unstake](https://bscscan.com/address/0xb32dF5B33dBCCA60437EC17b27842c12bFE83394#writeProxyContract#F6) function.
2. In the asset (address) field, paste the specific Asset Contract Address you copied from the dApp in Step 1.
3. In the amount (uint256) field, paste the complete, exact number you copied from your balance query for that specific asset in Step 2.
4. In the referralId field, type NA.
5. Click the "Write" button and confirm the transaction in your wallet.

<figure><img src="/files/Zgn5eqlVLY8KupUSTbNu" alt=""><figcaption></figcaption></figure>

| Asset            | Function       |
| ---------------- | -------------- |
| Native BNB       | unstakeNative  |
| clisBNB          | unstakeClisBNB |
| All other assets | unstake        |

For unstake (all other assets), you’ll also need to enter the asset contract address from Step 1.

In all cases:

* amount (uint256)-  paste the exact number from Step 2
* referral id - NA
* Click Write and confirm in your wallet

Once the transaction is confirmed on BNB Smart Chain, your assets are back in your wallet.

\*Withdrawing multiple assets? Repeat Steps 2 and 4 for each.

## Smart Contract Addresses

<table><thead><tr><th width="323.875">Asset</th><th>Address</th></tr></thead><tbody><tr><td>asBNB</td><td>0x77734e70b6E88b4d82fE632a168EDf6e700912b6</td></tr><tr><td>USD1</td><td>0x8d0D000Ee44948FC98c9B98A4FA4921476f08B0d</td></tr><tr><td>slisBNB</td><td>0xB0b84D294e0C75A6abe60171b70edEb2EFd14A1B</td></tr><tr><td>BNB (clisBNB)</td><td>0x4b30fcAA7945fE9fDEFD2895aae539ba102Ed6F6</td></tr><tr><td>BNB</td><td>0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c</td></tr><tr><td>BNBx</td><td>0x1bdd3Cf7F79cfB8EdbB955f20ad99211551BA275</td></tr><tr><td>BTCB</td><td>0x7130d2A12B9BCbFAe4f2634d864A1Ee1Ce3Ead9c</td></tr><tr><td>pumpBTC</td><td>0xf9C4FF105803A77eCB5DAE300871Ad76c2794fa4</td></tr><tr><td>mBTC</td><td>0x9BFA177621119e64CecbEabE184ab9993E2ef727</td></tr><tr><td>SBTC</td><td>0x15469528C11E8Ace863F3F9e5a8329216e33dD7d</td></tr><tr><td>solvBTC</td><td>0x4aae823a6a0b376De6A78e74eCC5b079d38cBCf7</td></tr><tr><td>stBTC</td><td>0xf6718b2701D4a6498eF77D7c152b2137Ab28b8A3</td></tr><tr><td>xsolvBTC</td><td>0x1346b618dC92810EC74163e4c27004c921D446a5</td></tr><tr><td>uniBTC</td><td>0x6B2a01A5f79dEb4c2f3c0eDa7b01DF456FbD726a</td></tr><tr><td>enzoBTC</td><td>0x6A9A65B84843F5fD4aC9a0471C4fc11AFfFBce4a</td></tr></tbody></table>

###

### What comes next

This isn’t the end;  it’s a transition.

The $KERNEL token, Kelp’s liquid restaking infrastructure, and KUSD are part of what comes next. We are excited to share more with you on our socials.

* X / Twitter: <https://x.com/kernel_dao>
* Telegram: <https://t.me/KelpDAOxyz/>
* Discord: <https://discord.gg/khSpqCFvGq>

### Need help?

Reach out via Telegram or tag us on X the team will assist you.

\ <br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kerneldao.gitbook.io/kernel/getting-started/kernel-deprecated/important-update-for-the-kernel-community.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
