> For the complete documentation index, see [llms.txt](https://cubepaper.gitbook.io/cubepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cubepaper.gitbook.io/cubepaper/whitepaper.md).

# Whitepaper

### RELEASE NOTES

### D**ISCLAIMER**

This white lite paper is a living document and it will receive updates when deemed necessary by the Realm of Cuboids team (hereinafter also referred to as “Cuboids”). Cuboids reserves the right to alter any information listed here; values could be updated as the project grows but overall the core structure will stay the same and any major changes will be announced.

This White paper is an integral part of the Realm of Cuboids website and both are regulated by the TERMS AND CONDITIONS (“T\&Cs”) therein downloadable or otherwise accessible. By reading or accessing this White paper in any way you automatically acknowledge having read, understood and accepted the Website T\&Cs as well. For the avoidance of any doubt, Realm of Cuboids including but not limited to the overall project, the website, all its under development software including any future smart contracts and mobile apps as presented in this conceptual paper is a pure online video game and entertainment platform, and it is not (nor is it required to be) an active licensed, regulated or exempted financial, gambling/e-gaming/betting, or payment or digital asset service or VASP of any kind and in any jurisdiction. Any terminology used in this document, or on the Website is intended only as a basic reference, without any effective or legal meaning of the same terms in a financial environment, and/or any other regulated framework including e-gaming and/or gambling and betting. The CUBIX token (<mark style="color:blue;">**$CUBIX**</mark>), the SHAPE token (<mark style="color:blue;">**$SHAPE**</mark>) are strictly for governance, utility or in-game tokens in any jurisdiction and are not and can not be considered as securities or otherwise regulated tokens of any kind, are not in any way e-money and/or fiat or asset backed stable coins, whether global or limited in scope.&#x20;

This document taken by itself is not, nor can it be construed as a contract, an investment contract or a contractual agreement of any kind. It is not an invitation or offer to invest in Realm of Cuboids or the CubeVerse, or acquire or use its tokens in any way with any expectation of future financial benefits and/or profit.&#x20;

Any user of the Cuboids Website and reader of this White paper declares to have:&#x20;

* Received appropriate technical, administrative and legal advice before and after reading this document and the Website’s content.
* Accepts that there is an inherent high risk in acquiring or using any kind of blockchain and/or crypto token, platform, software, or interface.
* Acknowledges with full disclaimer for any of the persons or entities mentioned within this White paper or in any way directly or indirectly connected to the Cuboids project, that there can be any kind of damage suffered, including total loss.


---

# 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://cubepaper.gitbook.io/cubepaper/whitepaper.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.