World Configuration
The immutable manifest that defines one configured Blueprint deployment.
World manifest
Before launch, a World should publish a signed or onchain-committed manifest containing:
- World name, Launcher, and parent Blueprint version;
- selected parameter values and configuration hash;
- data manifest and starting-state commitment;
- Season templates and permitted participant actions;
- verification class, checkpoint cadence, and finality policy;
- runtime profile, budget, and depletion behavior;
- settlement bounds and vault configuration;
- optional
$[New Token]design, if used; - fees, recipients, royalties, and administrative powers;
- interface, contract addresses, and risk disclosures.
Freeze points
Configuration can remain editable during drafting and testing. Before economic entry begins, every field that can affect eligibility, scoring, capital, fees, verification, or settlement must be frozen under the published launch process.
Changing a value outside the Blueprint's allowed parameter domain creates a fork or a new Blueprint version. Changing frozen Season rules requires a new Season—not an edit to the active one.
User-facing requirement
The launch interface should show a concise configuration summary and provide the full machine-readable manifest. A hash without accessible underlying data is not sufficient disclosure.