> For the complete documentation index, see [llms.txt](https://docs.robofi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.robofi.io/user-guide/users-with-robofi-wallet/stake-to-dabots/stake-to-bots-after-ibo-phase.md).

# Stake to Bots "after IBO" phase

Please read [<mark style="color:blue;">here</mark> ](/dabots/bot-life-cycle-and-ibo.md)to understand about "After IBO" phase.&#x20;

When a DABot already ends IBO, it goes to "After IBO" phase. In this phase, bot continues to raise fund by accepting more staking from users. This staking will still be opened when bot has not  reached the MAX CAP (max amount of crypto assets that bot wants to handle).&#x20;

In the following example, the sToken is `sUSDT`, the DABot name is `Capricorn`, this bot only accepts sUSDT for staking, the C-token name is `CapsUSDT.`

**Step 1:** If you are staking to a bot for the 1st time, you need to [<mark style="color:purple;">enable staking</mark>](/user-guide/users-with-robofi-wallet/stake-to-dabots/stake-to-bots-in-ibo-phase.md). If you had enabled staking, then you can skip this step.&#x20;

**Step 2:**  Stake to bots, because CEX DABots only accept sTokens for staking, if you are not having sTokens yet, please go to [<mark style="color:blue;">RoboFi Treasury</mark>](/products/robofi-treasury.md) to [<mark style="color:blue;">convert to sTokens</mark>](/user-guide/users-with-robofi-wallet/swap-to-stoken.md)<mark style="color:blue;">.</mark>

* Click the stake `(+)` button to start staking

![](/files/km42crp1jX9pcFiyBIrM)

* Enter the amount you want to stake.  Click `Confirm` button to stake to bot

![](/files/IaXDnYthca2KCA65HzW1)

* Enter your wallet password and click `Confirm` to finish the transaction

![](/files/n8xNdaHPZwEeDY1wuI2D)

* When staking is done, you can see `My stake` number

![](/files/k4x4F6tMgfTVRpqL4u2t)

* Click `Vault` to see how many bot's C-tokens you are having in the `Warm-Up Vault`. This is the "certificate" of your staking
  * These C-tokens are locked in `Warm-Up Vault` with `Lock time` as a countdown-timer. This is the "staking warm-up period" of each DABot. User can check this at the tab Bot Policy of each bot in the RoboFi Store.&#x20;
  * When Lock time is over, users can:
    * Unlock and Upgrade your C-tokens from Warm-Up Vault to `Regular Vault` with higher reward weight.
    * OR, withdraw C-tokens to your RoboFi Wallet and send/exchange these tokens with any other users. However, tokens not in Vault(s) are not rewarded.&#x20;

The total amount of crypto staking assets (for example, sUSDT) that all users have staked to this bot will be shown in the "Total Value Staked" (with value marked to USD) when viewing bot details.

[<mark style="color:blue;">Understanding more about Vaults for C-tokens</mark>](/user-guide/vaults/vaults-for-c-tokens.md)

Basically, all C-tokens are kept in [<mark style="color:purple;">Vaults</mark>](/user-guide/vaults/vaults-for-c-tokens.md) to be computed for, and distributed staking rewards. Later, users can:

* [<mark style="color:blue;">Harvest rewards from C-tokens</mark>](/user-guide/users-with-robofi-wallet/harvest-rewards/harvest-rewards-from-c-tokens.md)
* Or, [<mark style="color:blue;">unstake from DABots</mark>](/user-guide/users-with-robofi-wallet/unstake-from-dabots.md).


---

# 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.robofi.io/user-guide/users-with-robofi-wallet/stake-to-dabots/stake-to-bots-after-ibo-phase.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.