> For the complete documentation index, see [llms.txt](https://docs.nucleusearn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nucleusearn.io/nucleus-architecture/deprecation-guide.md).

# Deprecation Guide

### Deprecation Notice

Nucleus protocol is formally deprecated as of 12/19/2025.

Once the frontend is deprecated, the user interface for withdraws will no longer exist. However, the vault as a permissionless protocol will always allow you to withdraw through smart contract interactions. For those who do not have a technical experience, using a block explorer is sufficient and this guide will provide a step by step walk through.

#### Step 1: Identify available assets in the vault

You can use any blockchain explorers available to check assets that are still remaining within the vault. This is an example using the [tETH vault on etherscan.](https://etherscan.io/address/0x19e099B7aEd41FA52718D780dDA74678113C0b32)&#x20;

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

* Here, you can see that WETH, weETH, pufETH are the available assets that exist inside the tETH vault.
* You may decide to choose any asset that exists inside the vault as a withdraw asset. You will specify this token in Step 3.&#x20;

#### Step 2: Get your vault token balance

> For this section, please refer to the [Deployed Assets](/nucleus-architecture/deployed-assets.md) section for finding the right contract addresses.&#x20;

Go to a block explorer's page for the given vault token address. Then query the total amount of vault tokens you have using the `balanceOf` function. &#x20;

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

* You can see we are looking at the `tETH` address, and using the `balanceOf` function. Pass in your wallet address as the input. This address has `0.120759094314511387 tETH` tokens.&#x20;

#### Step 3: Withdraw from the vault

Lastly, go to a block explorer's page for the given `Teller` address and go to the "Write Contract" tab and find the `bulkWithdraw` function.

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

* Connect your wallet to the block explorer using the "Connect to Web3" button.
* For the `withdrawAsset`, input an address of the asset that you found in step one. Here, it is `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2` which is the `WETH` token address.
* For `shareAmount`, input the amount returned from step 2.
* For `minimumAssets`, input zero.&#x20;
* For `to` address, make sure this is your wallet address. The withdrawn funds will be sent to this address.&#x20;
* Once you press the "Write" button, you will be prompted for a transaction signature. Once the transaction is complete, you will see that your vault token was burned and that you received the underlying asset.&#x20;

That's it! Thank you for having been a user of Nucleus.&#x20;


---

# 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://docs.nucleusearn.io/nucleus-architecture/deprecation-guide.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.
