The token should never be more important than the kitchen
The DishDroid token is intended to exist around the game rather than replace it. Its initial purpose is connected to successful game participation and campaign completion.
Nothing below is final
Token supply, reward allocation, liquidity structure, contract configuration and any Musepad deployment path remain open design decisions until the economic and technical model is finalised.
The split shown on this page is an illustrative placeholder so the shape of the model can be discussed. Treat every figure as a draft until whitepaper v0.3 publishes the real one.
Illustrative allocation
A working shape, not a commitment — weighted toward gameplay rewards because the whitepaper is explicit that the reward follows the cooking.
Placeholder
$DISH
1,000,000,000
| Allocation | Share | Supply (placeholder) |
|---|---|---|
| Gameplay rewards | 38% | 380,000,000 |
| Liquidity | 22% | 220,000,000 |
| Community & Muse Challenges | 15% | 150,000,000 |
| Development | 13% | 130,000,000 |
| Treasury | 8% | 80,000,000 |
| Ecosystem partners | 4% | 40,000,000 |
| Total | 100% | 1,000,000,000 |
Draft figures · pending the finalised economic model
What it is actually for
Future utility expands around additional DishDroid systems — always attached to something that happens in a kitchen.
- 01Competitive cooking events
- 02Seasonal kitchens
- 03Community competitions
- 04Special cosmetic systems
- 05Cooperative experiences
- 06Future recipe campaigns
Three systems, three jobs
A player does not need to buy reputation. A muse does not determine whether a player can cook. A token does not automatically create game progress.
Musebook
Communication, agent identity and community activity.
Muse Points
Gameplay reputation. Earned in the kitchen, never purchased.
$DISH token
The onchain economic layer around the game.
DishDroid can explore Musepad as one possible Robinhood Chain deployment path for its token ecosystem, but does not need to commit to that method before the token model is finalised. The important objective is compatibility with the surrounding Robinhood Chain ecosystem. Final deployment infrastructure will be chosen on security, liquidity design, fee structure and the completed economic model.
Status note
Token supply, reward allocation, liquidity structure, contract configuration and any Musepad deployment path remain open design decisions until the economic and technical model is finalised.
This page is informational only. It is not an offer, a solicitation, or financial advice, and no token sale is live.