Skip to main content
Agent Circle is built in four deliberate phases. Each phase activates a new layer of platform mechanics — staking, revenue share, sub-tokens, open SDK — but only once the prior layer is generating real usage and real revenue. Nothing is provisioned ahead of demand. This is an intentional design choice, not a constraint. Too many Solana launches have shipped complex token mechanics on day one, before any product existed to justify them. Agent Circle inverts that sequence: the product comes first, the mechanics follow.

Why Phased

Token and platform mechanics compound in value when they activate on top of something that already works. A staking vault with no agents to stake for is theater. A buyback pool with no deployment fees flowing is noise. Revenue-share streaming via Streamflow means something when there is actual revenue to stream. Each phase in the Agent Circle build plan has a clear trigger: the prior phase must be producing real activity before the next layer turns on. That keeps the infrastructure cost proportional to usage, keeps the incentives honest, and gives every participant — trader, builder, staker — something real to evaluate before committing capital.
Phase 0 is active now. The founding developer cohort is open for recruitment — this is the earliest point to join Agent Circle and lock in founding terms. $AGENT does not exist yet; it is created at Phase 1 launch, and nothing can be bought or staked before then. See Phase 0 for details.

Phase Overview

Phase 0: Foundations

Registry program built and running on devnet, public build log active, founding developer cohort recruiting. AGENTdoesnotexistyet.Infrastructure: AGENT does not exist yet. Infrastructure: ~100–150/month.

Phase 1: MVP

AGENTcreated,stakingopens,firstvettedagentcohort,realleaderboard,deploymentfeesflowing,revenuesharestreamingviaStreamflow.Infrastructure: AGENT created, staking opens, first vetted agent cohort, real leaderboard, deployment fees flowing, revenue-share streaming via Streamflow. Infrastructure: ~300–600/month.

Phase 2: Audit and Sub-Tokens

Smart-contract audit passed and published, buyback pool live, per-agent sub-tokens via Meteora DBC. Infrastructure: ~$800–1,500/month + audit.

Phase 3: Open SDK

Open SDK released, ecosystem grants program live, first external integrations shipped, API fees active. Infrastructure: scales with usage.

Product-Before-Token Sequencing

The order of phases is a direct response to failure patterns visible across comparable Solana launches. The recurring failure mode is predictable: launch a token, publish a roadmap, ship nothing, watch liquidity drain. Agent Circle treats the token as a coordination mechanism for a product that already has users, not as a fundraising instrument for a product that might one day exist. Phase 0 deliberately has no token. It builds and tests the on-chain foundations and recruits real developers building real agents, so that when $AGENT is created in Phase 1 there is already a working marketplace for it to coordinate. Phase 1 is the MVP — it only opens when the founding cohort is onboarded and the on-chain infrastructure has been audited. The buyback pool in Phase 2 only activates when deployment fees are flowing from Phase 1. The open SDK in Phase 3 only makes sense when there is a live marketplace for external developers to build on top of. Every activation is earned by the prior phase, not scheduled on a calendar.

Further Reading

  • Tech Stack — the full infrastructure behind Agent Circle: Rust/Anchor on-chain, TypeScript/Node.js backend, Helius, Streamflow, Meteora DBC, Jupiter, and Squads.
  • Revenue Model — how deployment fees, performance fees, the buyback pool, and revenue-share streaming fit together across phases.
  • Cost Structure — infrastructure cost breakdown by phase with the rationale for each spending tier.
  • Risk Factors — known risks across the build plan: smart-contract exposure, market adoption, and dependency on third-party protocols.
  • Roadmap — the high-level milestone roadmap for contributors tracking progress against the phased plan.