NEEDS PROOFv2.0
Optional Token Design
A launch checklist for Worlds that need a local utility asset.
A World does not need a token merely because it uses Spawn. For v1, tokenized public launches are the primary product focus; private or tokenless use is a later option.
Design test
Before creating World Token, the Launcher should answer:
- What specific product action requires a transferable asset?
- Why would credits, access control, or direct payment be insufficient?
- What is the fixed supply and allocation?
- Which actions create demand, circulation, treasury flow, or burn?
- Which parties receive fees, and under what formula?
- What administrator, pause, upgrade, or treasury powers exist?
- How does the design avoid undisclosed pay-to-win behavior?
- What legal, market, and jurisdictional review is required?
Launch disclosure
The final name and ticker replace the placeholder World Token. The launch manifest must publish supply, allocation, liquidity plan, utility, fee routes, sinks, vesting or locks, administrative powers, and material risks before participation.
Token creation does not make a Model valuable, guarantee liquidity, or create a claim on Spawn revenue. Utility claims must match deployed contracts and actual product behavior.