SanctuaryCUBYBOO
The Guardian comes first. The ecosystem grows around it.
Transparent by design. Verified where possible.
2,222 Guardians · 16 Essences · 1 Ecosystem
Planned use of mint ETH
This is the project's economic model for the ETH collected at mint: how it would split across development, marketing, and two buyback mechanisms. No mint has happened yet, so no ETH has been collected or distributed under this model.
Technical development, smart contracts, and operational costs.
Dedicated growth budget, separate from development.
Planned to buy back $CUBYBOO on the market for holder rewards.
Planned to buy back and burn Guardians at the floor price.
| Development breakdown (35% of mint, planned) | Share of total mint |
|---|---|
| Technical development and smart contracts | 20% |
| Art production and content | 10% |
| Operational costs | 5% |
NFT Buyback & Token Buyback
Together, Token Buyback and NFT Buyback form the project's full planned buyback strategy.
25% of mint ETH is planned to buy back Guardians at the floor price. Bought-back Guardians join the Team NFT Reserve, reducing circulating supply. This is separate from the creator-fee mechanism above.
25% of mint ETH is planned to buy back $CUBYBOO on the market, distributed to Guardian holders by rarity tier across three tranches after reveal.
Each tranche, a Guardian would receive (its multiplier ÷ 4,330) of all the $CUBYBOO bought back that round, 4,330 being the sum of the multipliers across all 2,222 planned Guardians. Despite the smallest individual multiplier, Commons would capture the largest share of the pool simply because there would be so many of them.
The model calls for each tranche to be executed gradually over several weeks (TWAP) to limit sniping, and for $CUBYBOO claimed by holders to also unlock gradually rather than all at once.
Total $CUBYBOO supply, confirmed on-chain
Team token allocation, stated by the project
Planned Guardian NFT collection size
The supply figure is independently confirmed on-chain (see On-Chain Verification). The team-allocation and collection-size figures describe the project's stated design, not yet independently verifiable.
$CUBYBOO
$CUBYBOO is a deployed ERC-20 contract on Robinhood. Its supply, decimals, and network below are independently confirmed on-chain. Team allocation and swap fee are the project's stated design; the wallets that would let anyone verify them independently are not yet published (see On-Chain Verification).
| Item | Detail |
|---|---|
| Total supply | 1,000,000,000 $CUBYBOO |
| Decimals | 18 |
| Network | Robinhood |
| Team allocation (stated) | 0% |
| Swap fee (stated) | 1.1% |
0x213941B9a933b34F411F89FE8aBBb20DA23c2a9EVerified directly against Robinhood: contract bytecode, name, symbol, decimals, and total supply all match the figures on this page.
Planned Ecosystem Mechanics
These mechanics are part of the planned Cubyboo ecosystem and are not represented as live functionality until deployed and verified.
Lock $CUBYBOO for a reward multiplier on future governance-reserve distributions.
Some Guardians may unlock new paths within the ecosystem.
Guardian holders would vote on how the swap-fee reserve is used once it reaches a threshold.
When the time comes, the Guardians may have a voice in what comes next.
Wallet-linked badges for continuous Guardian holding; the NFT itself never changes.
Some Guardians may awaken beyond what they were.
Burning a Guardian to redistribute its buyback share or upgrade another Guardian's badge.
To become something new, something may have to be surrendered.
Burning two Guardians of the same tier to grant a badge upgrade to a third.
Some paths lead beyond what a Guardian was meant to become.
Swap Fee & Creator Fee
A 1.1% fee on $CUBYBOO swaps is planned to route into a project-controlled governance reserve. The receiving wallet will be published in On-Chain Verification once confirmed.
A 5% creator fee is planned for eligible secondary-market sales. The final enforcement mechanism will be published once the NFT contract and marketplace configuration are finalized.
Verified Contracts & Wallets
Only what is independently verifiable is marked as such. Everything else is listed honestly as not yet published.
This section will be updated as each contract and wallet is deployed and confirmed. Addresses are never published here until verified.
What each badge means
LIVE: currently available functionality.
DEPLOYED: infrastructure is deployed on-chain, but the functionality is not necessarily active yet.
IN DEVELOPMENT: actively being built.
PLANNED: intended, but development has not started.
PROPOSED: a concept under consideration, with no deployment commitment.
Tokenomics and ecosystem mechanics may evolve as the Cubyboo ecosystem develops. Only deployed and independently verifiable mechanisms should be considered active. Future mechanics are presented as plans or proposals, not guarantees.
Ready to become a
Guardian?
Accept the Oath and join the Whitelist to secure your spot.