Roadmap

A security-gated roadmap for durable crypto infrastructure.

The roadmap is written like an engineering program, not a hype calendar: each phase exposes scope, dependencies, risk, and why it matters to the economy.

PHASE 01 · Shipped foundation

Foundation: simulation-first world

roadmap model

Scope

Persistent forest loop, guest sessions, wallet binding, DNA4 genetics, world snapshots, chronicle memory, market surfaces, and SEEDOS ledger primitives.

Engineering rationale

The priority was proving that the world can run as a deterministic economy before pushing ownership surfaces. This phase locks the principle that gameplay mutation belongs to USK/Postgres, not hot-chain execution.

Dependencies

Prisma schema stability, forest API payloads, resource state, GameEvent history, session identity resolution.

Risk gate

Schema drift and identity merge bugs are more dangerous than missing cosmetic features.

PHASE 02 · Active

Production security and contract hardening

roadmap model

Scope

UUPS production contracts, authorized anchors, timelock, multisig routing, emergency controller, funded staking, LP safety, marketplace signatures, and settlement caps.

Engineering rationale

This phase converts economic prototypes into reviewable protocol surfaces. Every privileged function needs a role, delay, emergency posture, or testable invariant.

Dependencies

Hardhat tests, role rotation scripts, security docs, and deployment rehearsal on Base mainnet.

Risk gate

Upgrade authority and treasury routing are the primary blast-radius controls.

PHASE 03 · Launch-gated

Seed drop and Base launch

roadmap model

Scope

Merkle allowlist, reveal/freeze metadata, live pressure, gasless eligibility where safe, treasury disclosure, mint risk copy, and secondary marketplace readiness.

Engineering rationale

The drop should validate collection demand without pretending minting is the game. Ownership is on-chain; progression remains in the realm.

Dependencies

SeedNFT deployment, marketplace approval flow, treasury router, pressure worker, explorer links, status widgets.

Risk gate

Bot pressure, whale concentration, metadata ambiguity, and fake urgency are launch risks.

PHASE 04 · Research

Governance maturation

roadmap model

Scope

Snapshot-weighted proposals, staked SEEDOS voting power, capped Seed bonus, governance reputation, timelock queue, and forbidden control policy.

Engineering rationale

Governance should tune economic bands, not own the world. The project should keep arbitrary minting, treasury drain, and anchor rewrite outside governance authority.

Dependencies

Voting-power snapshots, anti-double-vote tests, proposal lifecycle UI, timelock monitoring.

Risk gate

Premature DAO claims would reduce credibility with engineers and investors.

PHASE 05 · Research

World expansion and ecosystem automation

roadmap model

Scope

Deeper lineage, territory strategy, advanced sinks, economic simulations, ecosystem dashboards, and public archive growth.

Engineering rationale

Expansion should add consequence without increasing trust ambiguity. Every new system needs a truth owner, proof surface, and failure mode.

Dependencies

Stable economy telemetry, security monitor, settlement history, player retention evidence.

Risk gate

Feature expansion before security maturity creates brittle complexity.