Contracts & Modules
Proposed v2 contract/module map. No address should be presented as deployed until it actually exists.
On-chain core
BlueprintRegistry
Stores immutable Blueprint-version identifiers, hashes, Designer/royalty metadata, license pointer, verification class, and benchmark/profile references.
WorldFactory / WorldRegistry
Creates/registers World identity, parent Blueprint version, Launcher, World Token, World configuration hash, fee policy, runtime policy, and liquidity references.
SeasonRegistry
Freezes Season rule/configuration hashes, entry windows, settlement template, randomness class, and finality policy.
SpawnUnitVault
Custodies competitive $SPAWN, maps deposits to Positions, and pays finalized claims.
RuntimeVault
Custodies $ETH runtime funding and pays authorized runtime/verification obligations.
FeeRouter
Accrues eligible fee shares to Designer, Launcher, protocol, treasury, runtime, etc., without requiring many synchronous transfers.
CheckpointRegistry
Records candidate/finalized state commitments and their status.
Verification/AttestationRegistry
Tracks authorized/qualified verifier attestations, bonds, conflicts, and quorum status for REPLAYED Worlds.
SettlementEngine / SettlementTemplates
Accepts only FINALIZED terminal results and applies predeclared, bounded settlement formulas.
LiquidityLocker
Venue-specific protected-liquidity module with no principal withdrawal path where technically supported.
Off-chain services
- Model/Blueprint build pipeline.
- Benchmark service.
- Data manifest/provenance service.
- Runtime scheduler.
- Spawn-managed compute workers.
- Independent verifier workers.
- Indexer/API.
- Website/UI.
- Later provider marketplace/bidding engine.
All fund-custody contracts are NEEDS PROOF until implemented, tested, and audited.
Deployment rule: This page must remain address-free for v2 modules until each production deployment is confirmed and recorded.
Required control registry
Before any module is marked deployed, this page must publish its address and identify every:
- owner or administrator;
- upgrade authority and implementation address;
- pauser or emergency role;
- fee recipient and fee-changing authority;
- treasury or asset-sweep permission;
- signer, verifier, or oracle authority;
- delay, cap, multisig threshold, and renunciation condition.
Unknown authority is a launch blocker. An audit or verified source does not replace this permissions disclosure.
Evidence required for LIVE status
The deployment record must include the chain ID, contract address, creation/configuration transaction hashes, source or bytecode verification, version, tests, security review status, and known limitations.