Building on Archeum

A primer for developers and AI assistants · the full reference lives at archeum.dev

Archeum apps are mobile-only (Android for v1). Apps connect to the user's node - which runs on their phone - using their wallet credentials. Only the Archeum app itself provisions nodes; normal apps never do.

The model in one breath

Every user owns a node on their phone and a handle like @alice. Your app signs in as that user, then reads and writes data on their node over QUIC. An Archeum app is frontend-only: there is no backend to run and none to write. Logic that would have lived on a server runs in the client, and handle ownership lives in Archeum's own feeless consensus (no outside chain, no gas).

Give your AI the skill

We maintain a skill, a compact briefing a coding agent loads before writing Archeum code: where each piece of data lives, the full client surface with the time cost of every call, the rules the node enforces, and the mistakes agents actually make.

curl -o SKILL.md https://archeum.dev/skill/SKILL.md

Install it wherever your agent keeps its skills, or paste it into the conversation. Setup details and ready-made prompts live at archeum.dev/guide/ai-development.

Where data lives

Your app bundle - constants that ship with a build: sprites, static config.
The user's node - personal data with one writer, encrypted to them by default.
The mesh - shared state anyone in the app may change at runtime: leaderboards, chat, presence.
Consensus - globally unique ownership that must settle the same way for everyone.

Full reference

This page is a pointer. The docs at archeum.dev carry the quick starts (Rust and Flutter), the SDK reference, and the concepts behind them.