> For the complete documentation index, see [llms.txt](https://docs.mvlchain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mvlchain.io/user-guide/token-use-cases/mvl-staking/staking-pools.md).

# Staking Pools

## B**asic Concept**

Staking Pools is a bMVL, MVL single token deposit service that will be conducted on the MVL Fi.

The main purpose of the service is to:

* Encourage ERC20 MVL token holders to switch to BEP20 bMVL token network to activate bMVL liquidity providing (BNB-bMVL LP creation) participation
* In the future, in addition to the MVL Bridge, provide and compensate network conversion liquidity to MultiChain DEX that supports ERC20 MVL ↔ BEP20 bMVL network conversion (to be introduced later)
* Considering the activation stage of bMVL, MVL transactions according to the step-by-step connecting between mobility services and blockchains, pre-checking specifications such as mainnet and side chains to be prepared in the future

## Single Staking (bMVL)

### **Basics**

* MVL Fi's Bridge function converts ERC20 MVL tokens into BEP20 bMVL tokens and deposits them in MVL Fi's Staking Pools, bMVL is paid as rewards according to the amount and period of deposit.

## Single Staking (MVL)

### **Basics**

* If you deposit MVL in MVL Fi's Staking Pools, MVL is paid as rewards according to the amount and period of deposit.

## **Single Staking Spec.**

**bMVL Token Address**

{% embed url="<https://bscscan.com/token/0x5f588efaf8eb57e3837486e834fc5a4e07768d98>" %}

**MVL Token Address**

{% embed url="<https://etherscan.io/token/0xa849eaae994fb86afa73382e9bd88c2b6b18dc71>" %}

**MVL ↔ bMVL Bridge**

* Bridge on MVL Fi

{% embed url="<https://mvlfi.mvlchain.io/>" %}

**bMVL Staking**

* Single Staking on MVL Fi

{% embed url="<https://mvlfi.mvlchain.io/pools>" %}

* 1st Single Staking Contract (22.12.01\~23.12.03)

{% embed url="<https://bscscan.com/address/0x0A3AC95445F3e02cC80267f02B9669ed75b71043>" %}

* 2nd Single Staking Contract (23.12.05\~24.12.07)

{% embed url="<https://bscscan.com/address/0x121E257f4A6fa763012eF0b6b6f68905F6D4b721>" %}

* 3rd Single Staking Contract (24.12.09\~)

{% embed url="<https://bscscan.com/address/0x8CeB404D939c293ad070A5B33fc197df3aF1AbB7>" %}

* Fixed Single Staking Contract (24.03.08\~24.06.06)

{% embed url="<https://bscscan.com/address/0x5a54ec1e6da36f19a806a9168fd4270fef697354>" %}

**MVL Staking**

* Single Staking on MVL Fi

{% embed url="<https://mvlfi.mvlchain.io/pools>" %}

* 1st Single Staking Contract (23.11.24\~24.11.26)

{% embed url="<https://etherscan.io/address/0x92Ec27935cE7b523cc70C2fFaf0728F1Fa6425dF>" %}

* 2nd Single Staking Contract (24.11.28\~)

{% embed url="<https://etherscan.io/address/0x742AB08EEc9f940beF657394720090F163f535Cc>" %}

* 1st Fixed Single Staking Contract (24.03.08\~24.06.06)

{% embed url="<https://etherscan.io/address/0x1BdFAa7aFAa454F491b5de40d24d681F0F3Adb1A>" %}

* 2nd Fixed Single Staking Contract (24.06.04\~)

{% embed url="<https://etherscan.io/address/0xB87A16fD301b3CFed03982D99840970328d185aD>" %}


---

# 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.mvlchain.io/user-guide/token-use-cases/mvl-staking/staking-pools.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.