Practical overview
When it fits
Use Eternum when looking for a strategy game centered on onchain territory and resource management, or when examining an open-source game stack combining a web client with Cairo contracts.
Who it is for
- Players interested in onchain strategy, territorial competition and seasonal tournaments.
- Developers exploring a TypeScript game client, Cairo contracts or Starknet and Madara appchain architecture.
Documented uses
- Claim Realms and manage resources across a hex-based world.
- Build armies, trade with other players and form alliances.
- Compete in Blitz, a shorter tournament format with ranked matchmaking and objective-based scoring.
- Study or adapt the game's client, contracts and shared packages.
Requirements & limits
- The README describes the game as fully onchain and identifies Starknet and a self-hosted Madara appchain in its architecture.
- The repository separates the player-facing client from Cairo game domains, chain infrastructure and supporting services.
- Blitz has its own tournament rules and pace; it is presented as a format distinct from the broader Eternum sandbox.
- The local development setup requires both JavaScript tooling and native contract tools.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the Eternum development workspace
Set up the repository dependencies and build shared packages before starting the game development server.
Before you start
- Node.js v20.19 or later
- pnpm v10.25
- Bun
- Scarb and Foundry versions pinned in contracts/l3/world-native/.tool-versions
Steps
Clone the repository and change into its directory.
Install workspace dependencies with pnpm install --frozen-lockfile.
Run the native-tools installer and source the environment file it creates.
Build shared packages with pnpm run build:packages.
Expected outcome
Workspace dependencies are installed and shared packages are built; the README lists pnpm dev as the next command to start the game development server.
Guide limitations
- The README says to select the isolated native manifest and admission endpoint before starting the client.
- This setup sequence does not describe deploying the game or configuring a production environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- BibliothecaDAO/eternum · Official homepage title · retained in its source language

