Syncing interface
Skip to main content

Whitepaper chapter

Architecture

The architecture is a three-boundary model: simulation truth, Base execution, and Ethereum L1 notarization. USK computes raw state from game and economy events. Prisma/Postgres stores player sessions, trees, seeds, resources, SEEDOS ledger entries, market listings, and settlement batches. Base handles Seed NFT minting, signed marketplace fills, SEEDOS settlement, staking, LP telemetry, and governance execution. Ethereum L1 anchors sparse raw roots so the protocol can prove historical checkpoints without pushing hot gameplay paths into L1 gas.

01

Trust boundary

Trust boundary: off-chain state is authoritative for gameplay; on-chain state is authoritative for ownership and settlement receipts; L1 anchors are evidence, not gameplay source-of-truth.

  • Gameplay mutation remains in USK/Postgres unless explicitly settled.
  • On-chain state is used for ownership, receipts, governance execution, or proof.
  • Public copy must describe the boundary honestly, including what is not decentralized yet.

02

Contract surfaces

Contract surfaces: UUPS `SEEDOS`, UUPS `SeedNFT`, UUPS `SeedMarketplace`, `WARDStaking`, `WARDLiquidityPool`, `WARDGovernor`, `WardenseedAnchor`.

  • Every surface should emit enough events for analytics and incident reconstruction.
  • Privileged functions should be role-gated, timelocked, or emergency-scoped depending on blast radius.
  • Batch, nonce, and root identifiers must remain replay-resistant across upgrades.

03

Operational assumptions

Assumption: Base RPC/network failure pauses settlement surfaces; it should not corrupt the simulation ledger.

  • Failure modes must degrade visibly rather than pretending the world is healthy.
  • Security posture takes priority over feature velocity when settlement or treasury risk is involved.
  • Docs, tests, and live proof widgets should evolve together with contract changes.