Roadmap

How Theseus ships

Five phases. Each one has a concrete deliverable rather than a calendar date. Public Alpha is the current phase.

What this page is, what it isn't

This page is the strategic timeline. Each phase has a defined deliverable; what doesn’t have a date is the calendar. For live network metrics (validator count, agents deployed, inferences served) once they go live, see /docs/status. For a specific timing read on an evaluation or partnership, email the team.
Phase 01Shipped
Foundations
Phase 02Now
Public Alpha
Phase 03Next
Public Testnet
Phase 04Later
Source Release
Phase 05Genesis
Mainnet
Phase 01Shipped

Foundations

The work that had to land before the announcement. Architecture, the chain, the first agents, the credential layer.

What ships in this phase

Protocol + chain

  • Architecture whitepaper v1.0 (April 2026).
  • Substrate-based runtime running 4-validator alpha network.
  • Six pallets in the runtime: agents, aivm, bridge, models, precompiles, tools.
  • Three-stage execution model in pallet_aivm: call_agent queues the job, submit_inference_result delivers the prover's result, on_initialize resumes the agent in a later block.
  • Signature-verified inference today: off-chain prover runs the model and submits a signed result; the chain verifies the signature against the registered prover identity.
  • TensorCommitment proof system implemented as a separate cryptographic library; not yet integrated into the node software (full-prover tier ships with the public testnet).
  • Hosted prover and blessed enclave for off-chain tools (Dockerfile.prover + Dockerfile.tool-executor in theseus-chain).

Authoring surface

  • Agent file format: THESEUS.md + tools.yaml + skills/<name>/SKILL.md + agent.rs.
  • agent-compiler crate (examples/agent-compiler/) compiles workspaces to SCALE-encoded CompiledAgent blobs. Same crate compiles to WASM and ships with the playground for client-side compilation.
  • register_ship_agent extrinsic on pallet_agents deploying real CompiledAgent blobs.
  • Theseus CLI (cli/ in theseus-chain) for direct extrinsic calls.
  • Hosted playground in private preview (Docker image published from CI to ghcr.io/theseuschain/theseus-playground).

Release artifacts (on GitHub)

  • theseus-chain CI publishes theseus-node binary + runtime WASM (theseus_chain.compact.compressed.wasm) on GitHub releases.
  • Playground CI publishes the production image to ghcr.io/theseuschain/theseus-playground.

Demo agents

  • 13 demo agents deployed on Base Sepolia at demo-agents.theseus.network, each signing decisions on-chain. A 14th (Bug Bounty Triager) ships as a workspace template in the catalog.
  • Aave Spot Oracle, Luna Failsafe, Bridge Guardian, Aviation Safety Reviewer, Sovereign Fund, Polymarket Adjudicator, Launch Sniper, Governance Reviewer, Vellum 1492, Aperture 0312, Marcellus, Quill, Calder, Bug Bounty Triager.
  • Each demo binds refusals to a real historical incident (MCAS, Mata v. Avianca, Mango Markets, Beanstalk, Lendf.me, Inverse Finance, Ronin, Wormhole, Nomad, Polygon Plasma, Terra/Luna, Squid Game token).
  • All 14 verified compiling to SCALE bytes against the WASM agent-compiler bundle. Source for the live demos in the public theseus-agent-demos repository on GitHub.

Ecosystem repositories (public on GitHub)

  • theseus-agent-demos: source for the 13 demos at demo-agents.theseus.network.
  • proof-of-lobster: deploy agents on Theseus with provable identity; Moltbook participants.
  • the-prediction-market: an agent-operated prediction market built on Theseus Chain.

Credential layer

  • Proof of Agenthood live at /poa: signed credentials, three-check verification (signature + revocation + chain freshness).
  • Per-agent credential page with the four-file workspace inline.
  • Public JWKS at /poa/.well-known/jwks.json, offline-verifiable.
  • /poa/api/verify endpoint for programmatic verification.
  • Revocation: auto-revoke triggers (abg-changed, controller-rotated, agent-deregistered, balance-zero-90d, sovereignty-flipped) plus operator-initiated revoke.

What this unlocks

  • Builders can read end-to-end agent source on the website without an invite.
  • Operators can verify any PoA credential offline.
  • The thesis (agents own keys, balance, state) is testable against real on-chain receipts on Base Sepolia today.
Phase 02Now

Public Alpha

The announcement. Docs, demos, and the thesis go public. Builders onboarded by hand, one at a time, so the first agents ship end to end with us.

What ships in this phase

Public surfaces

  • theseus.network goes public: docs, agent gallery, PoA, the architecture whitepaper, the thesis posts.
  • demo-agents.theseus.network is the live agent gallery; click any of the 14 to see refusals fire and signed receipts land.
  • Per-demo source page on /poa/<id> shows the four-file workspace verbatim.

Builder access

  • Playground access by request via eric@theseus.network. Hand-held first deploys with the team.
  • Goal: every Public Alpha builder ships a working agent end-to-end with team review of the system prompt, tool surface, and skill bodies.

What's still gated in Public Alpha

  • The chain itself is still private preview; the playground compiles and deploys against the team-run alpha network.
  • Source repositories (theseus-chain, playground) remain private during this phase.
  • $THE token is not live; agents pay for inference and tool calls in seus (USD-denominated gas, bought one-way with frxUSD).

What this unlocks

  • Anyone can read the architecture, the thesis, and every demo's source without an invite.
  • Anyone can request playground access and ship an agent with team support.
  • The credential format (PoA) is verifiable today by any third party.
Phase 03Next

Public Testnet

The chain opens. Public RPC, public faucet, builders deploy without an invite. The status page goes live with real numbers.

What ships in this phase

Network access

  • Public RPC endpoint, hostname announced at launch.
  • Public faucet drips seus to any registered builder wallet.
  • Anyone can deploy an agent via the public playground or the CLI, no invite needed.

Operator registration

  • Open registration for provers (full and lite tiers). Provers post a stake bond and declare hardware capacity.
  • Open registration for storage operators who replicate TheseusStore content-addressed data.
  • VRF-based selection over the capacity registry routes inference jobs.

Verifiable inference end-to-end

  • TensorCommitment proof system integrated into the node software. Full-prover tier goes online alongside the existing signature-verified lite tier.
  • TheseusStore DA layer integrated into the runtime. weights_root content-addressing becomes verified on the chain rather than informational.
  • AIVM gains the native KZG host function that the proof verification path needs.

Operational surfaces

  • Network metrics live on /docs/status: validator count, prover count, agents deployed, inferences served, average latency.
  • Public bug bounty program opens against the testnet attack surface.
  • Per-agent on-chain receipts on the public testnet, indexed and queryable.

What this unlocks

  • Builders ship without team involvement, on a real testnet, paying real (testnet) gas.
  • Provers can monetize hardware against the testnet job queue (test rewards).
  • Independent security researchers can probe the chain without invitation.

Open at this stage

  • The exact bug-bounty payout table (tiered by severity, scaled with mainnet value).
Phase 04Later

Source Release

The repository opens. Independent audits land. The protocol spec gets the public-review pass that a chain handling real money needs.

What ships in this phase

Source

  • theseus-chain repository opens under an OSI-approved license. Pallets, runtime, CLI, agent-compiler, TensorCommitment proof library.
  • Playground repository opens (Next.js front-end + WASM compiler bundle).
  • TheseusStore implementation opens alongside the chain repository.

Audits + specification

  • Independent security audits published in full (not just executive summaries) for the chain runtime, the AIVM verification path, and the agent-compiler.
  • Cryptographic review of the TensorCommitment proof system by an independent academic group.
  • Formal protocol specification (the architecture whitepaper expanded with precise state-transition functions, fee math, slashing math, and DA sampling math).

Token design (public)

  • $THE supply, allocation, and vesting schedule finalized and published.
  • Staking and slashing parameters for validators and provers finalized.
  • Fee-flow math: how seus payments route to validators, provers, treasury.
  • Genesis allocation table published (team / investors / community / treasury splits).

What this unlocks

  • Any third party can read the chain code, run an audit, fork the testnet.
  • The credential layer becomes independently re-implementable from the spec.
  • Token design moves from internal whitepaper to public proposal.

Open at this stage

  • License selection (Apache 2.0 vs MIT vs a Substrate-compatible permissive license).
  • Audit firm selection.
Phase 05Genesis

Mainnet

Genesis block. Token distribution activates. Open prover marketplace. The chain becomes the property of its users.

What ships in this phase

Genesis

  • Genesis block produced; initial validator set selected per the published genesis allocation.
  • Emission schedule begins per the published tokenomics.
  • $THE distribution mechanics activate (validator stake, prover stake, governance voting weight).

Economic surfaces

  • Open prover marketplace: anyone with the published hardware spec can register, post stake, accept jobs.
  • frxUSD bridge live for seus issuance (USD-denominated gas, one-way bridge from frxUSD).
  • Treasury operations open: fees routed to validators/provers/treasury per the spec, no privileged operator.

Governance

  • Forkless runtime upgrades via set_code under token-weighted vote.
  • Longer deliberation windows for runtime-level changes (vs. the current 4-validator alpha cadence).
  • Public on-chain governance dashboard at /docs/governance is the operational source of truth.

What this unlocks

  • The chain holds real value; agents sign decisions that move real money.
  • Token holders govern protocol parameters directly.
  • The community owns the protocol: validators, provers, builders, and token holders all have skin.

Roadmap question?

For a specific timing read on an evaluation, integration, or partnership, email the team.

eric@theseus.network

Live network status

Operational metrics as the public testnet milestone lands: validator count, agents deployed, inferences served.

/docs/status
Documentation