> For the complete documentation index, see [llms.txt](https://meversedex.gitbook.io/meverseconnect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meversedex.gitbook.io/meverseconnect/key-features/new-chain-based-cherry.md). # New Chain-based Cherry We plan to support other chains, not only the BSC. This will help TVL rise and it will make the value of Fleta Connect more unique. New Chain-based Cherry is a Cherry token earned by farming on a new chain-based service. New Chain-based Cherry is not separate from Cherry token, it's the same asset but on a different chain. Here are some key points to understand New Chain-based Cherry: * Cherry converted to or minted on a new chain is nCherry. (n is subjective to be changed based on a chain.) * nCherry is emitted as Cherry on BSC is locked via smart contract on BSC. This means that Cherry tokenomics remains the same including circulating supply inflation. * The overall Cherry token metrics remain the same but the Cherry token gains a new field of play with a new chain. This adds a new avenue of yield and related buyback & burns with higher TVL. * With this same logic to mining distribution, Cherry is essentially adding the value of a new chain to Fleta Connect. We currently have Cherry for BSC, pCherry for Polygon, and kCherry for Klaytn. --- # 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://meversedex.gitbook.io/meverseconnect/key-features/new-chain-based-cherry.md?ask=&goal= ``` `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.