> For the complete documentation index, see [llms.txt](https://cubo-1.gitbook.io/cubo-protocol-v0.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cubo-1.gitbook.io/cubo-protocol-v0.1/other/faq.md). # FAQ ### Is this a fork of Strong, Ring, etc? No, Cubo is heavily influenced by Strong as the whole team is a fan of Strong. But Cubo is a unique project. Although the concept is similar to Strong, all the code was written from the ground up by our team. This approach allows us to build a unique product that has unique properties. ### Why provide X CUBO and X DAI? Our contract will create LP tokens in QuickSwap. For this it needs a pair of tokens. Providing liquidity requires 50% of each token. With the system implemented by Cubo a user that creates a node with CUBO over $1 USD is saving on the DAI side. This means the user can provide liquidity cheaper than at a regular DEX. This system also incentivises Cubo believers to keep the price over $1, creating a floor for CUBO's price. ### What if CUBO price goes a lot over $1? If the price goes a lot over $1 there's a theoretical risk that the contract's DAI pool gets depleted. In this case the contract will automatically start adjusting the LP tokens to use the 100 DAI, but less than 100 CUBO (nano node case). The remaining CUBO tokens are kept in the rewards pool. So if CUBO is at $100, this means the liquidity pair created would be: 100 DAI - 1 CUBO. The remaining 99 CUBO provided are added to the rewards pool. ### --- # 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://cubo-1.gitbook.io/cubo-protocol-v0.1/other/faq.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.