Asset Architecture
Optional local utility, network capital, and measurable compute funding.
Canonical v2 economic split
a) WORLD TOKEN = OPTIONAL UTILITY
Optional World-specific asset with its own name and ticker, used only when transferable local utility serves a real product function.
b) $SPAWN = PROPOSED NETWORK CAPITAL
Existing token with two near-term proposed protocol roles: a published World-creation requirement and optional collateral in eligible Seasons. Neither role is live without verified production contracts.
c) $ETH = COMPUTE
Native value used for blockchain gas and the external compute/storage/verification budget.
Why an optional World Token may power a World
A World may use an optional World Token when transferable local utility serves a clear product purpose. The final asset receives its own name and ticker; World Token is a category, not a literal ticker.
more World activity → more local-token demand/consumption.
Example:
- Burn/pay
$HURRICANEto create a hurricane. - Lock
$SPAWNonly when the Season includes real competitive capital at risk.
Example action classes
Class A — ordinary World action
Only its named World Token, when the World needs local transferable utility.
Example: spend 500 $HURRICANE to modify or deploy an allowed storm component.
Class B — competitive economic action
Optional World Token + $SPAWN, but only after the applicable vault and settlement controls are verified.
Example: use a disclosed amount of World Token for a defined World action and lock a disclosed amount of $SPAWN as Season capital.
Class C — protocol action
Primarily $SPAWN.
Example: satisfy the $SPAWN creation requirement published by a verified production launch contract. Until that contract exists, no amount is authoritative.
Deferred roles
Cross-World settlement, provider/verifier security bonds, and generalized protocol-fee routing are conceptual. They are not part of the near-term utility claim.