Technical Overview

This page is the engineer path into EverArcade. It summarizes the moving parts and links to the implementation docs instead of duplicating them.

World Contracts​

World Contracts define the rules that change world state. They are the boundary between a game idea and a verifiable persistent world.

• World contract architecture
• Contract development
• ABI boundary

Runtime Packages​

Runtime packages keep rules, metadata, and operating expectations portable. Packaging is what lets a world move from local development to hosted operation without becoming trapped in one launcher.

• World packaging
• Runtime distribution strategy
• Release packaging

Deterministic Replay​

EverArcade treats replay as a trust primitive. If a world claims a history, participants should have a path to check the relevant execution window.

• Replay engine
• Replay attack surfaces
• Historical replay

Verification​

Verification connects runtime execution, receipts, release integrity, and operator practice. It exists so communities do not have to rely on one server's memory forever.

• Receipt boundary
• Receipt system
• Runtime release integrity

Federation​

Federation lets operational responsibility extend beyond a single permanent host. The goal is continuity, recoverability, and independent checking rather than a single magic server.

• Federation architecture
• Federation runtime
• Future federation risks

World Packaging​

Packaging is the handoff between creators, operators, marketplaces, and verification tooling.

• Canonical package format
• Game package format
• Deployment readiness matrix

Continuity​

Continuity is the user-facing promise: worlds remember what happened and can continue after upgrades, incidents, migrations, and operator changes.

• Continuity Engine
• Checkpoint system
• Restoration
• Operational recovery

Next steps​

• Check the Capability Matrix for maturity.
• Read Developers for the creator journey.
• Use the Architecture page as the full docs index.