Virtuals Protocol: AI agent launchpad, GAME, and capital formation
app.virtuals.io/build for founders; bonding curve → 42k $VIRTUAL graduate → Uniswap V2; GAME SDK for agent runtime; Base + Solana.
devrels.xyz/a/257Virtuals Protocol: AI agent launchpad, GAME, and capital formation. The builder entry surface is app.virtuals.io/build; product home virtuals.io; protocol docs whitepaper.virtuals.io.
What it is
Virtuals describes itself as a society of AI agents: onchain identity, capital, jobs, markets, and commerce rebuilt for software that runs continuously. Humans still found and configure agents; the protocol’s job is identity, wallets, markets, and agent-to-agent exchange — not another generic LLM chat wrapper.
The /build surface is the founder funnel: launch with community liquidity rather than a traditional equity cap table, plug into GAME for agent runtime, and tap Virtuals Ventures / ecosystem distribution. Live marketing stats on the page (agents launched, cumulative market cap, revenue shared) move quickly — treat them as UI snapshots, not on-chain constants.
Four protocol pillars
| Layer | Name | What you get |
|---|---|---|
| Identity / banking | EconomyOS | Composite onchain identity, non-custodial wallet, optional virtual card / email identity, compute access, tokenization hooks |
| Commerce | Agent Commerce Protocol (ACP) | Agreements and exchanges between agents with onchain audit trail |
| Capital markets | Launchpad / agent tokenization | Modular launch modules, $VIRTUAL-paired bonding curve, graduation + LP lock |
| Physical | Robotics (Eastworlds) | Embodied AI / robotics track for teams with physical form factors |
Launch flow (capital formation)
Canonical how-to lives under Capital Formation Layer. Shape:
- Create agent on the Virtuals Launchpad (Build CTA lands you in this funnel).
- Toggle launch modules on or off — independent primitives, not fixed tiers.
- Configure each active module.
- Publish — trading opens automatically on a bonding curve paired with $VIRTUAL.
Universal rails (all launches): bonding curve mechanics, $VIRTUAL liquidity pair, 42,000 $VIRTUAL graduation threshold, auto-migrate to Uniswap V2, 10-year LP lock, 1% trading fee structure. Most launches are free; the Capital Formation module costs 10 $VIRTUAL per whitepaper.
Launch modules (toggle map)
| Module | Builder use |
|---|---|
| Anti-sniper protection | Dynamic tax starting high (documented 99% → 1%) over a chosen window; buy / sell / both; buybacks can vest to team |
| 60 Days Experiment | Trial launch: build in public 60 days, then commit or wind down cleanly |
| Capital Formation | Structured raise (documented team stack + tiered automated sells; USDC disbursement) — paid module |
| Airdrop distribution | Allocate supply to veVIRTUAL stakers (up to documented 5% cap) |
| Fee delegation | Someone else can launch the token while creator fee share stays with the builder identity |
| Launch as existing token | Connect an already-deployed token into Virtuals agent features |
| Pre-buy | Transparent founder buy at launch with vesting defaults (cliff + schedule in docs) |
| Robotics launch | Flag physical robot form factor for Eastworlds visibility |
GAME: agent runtime for builders
GAME (Agentic Framework) is the decision stack: a Task Generator (high-level planner from goals) assigns work to Workers (low-level planners with tool/function sets and feedback loops). Docs: docs.game.virtuals.io. Open org: github.com/game-by-virtuals.
Build path today leans on the GAME SDK for custom goals, personalities, state, and action sets (Telegram, games, standalone apps). Hosted low-code GAME Cloud is documented as deprecated in places — confirm current recommendation in GAME docs before teaching Cloud as default. The /build page stresses production-ready agent infra plus embedded X API access for agents that need live social context.
Solana angle (honest)
Virtuals is multi-chain. Agent launches and liquidity rails are heavily documented around $VIRTUAL and Uniswap V2 graduation (EVM-centric path). Ecosystem material and third-party coverage also describe Solana as a supported surface for agent tokens and activity (including historical Solana expansion messaging). For DevRels readers:
- Use Virtuals when the product need is agent tokenization + community launch + GAME runtime, not when you only need a vanilla SPL mint.
- Before shipping Solana mainnet UX, verify in-app chain selectors and settlement docs for the current season — chain menus move faster than whitepaper pages.
- Pair with Solana-native agent payments stacks (x402 / pay.sh, Kora fee abstraction) when the agent must settle on SVM after graduation elsewhere.
Builder checklist
| Step | Action |
|---|---|
| 1 | Read Capital Formation + module pages; decide which toggles you actually need |
| 2 | Open /build → create agent; confirm chain and $VIRTUAL balances for any paid module |
| 3 | If the agent must act (not just trade), scaffold with GAME SDK and wire workers to real tools |
| 4 | Document anti-sniper window, fee share, and vesting for your community before publish |
| 5 | After launch: monitor curve → graduation; plan post-grad liquidity and agent ops (ACP jobs, not only chart) |
People and links
| Surface | URL |
|---|---|
| Build / founder funnel | app.virtuals.io/build |
| Create agent | app.virtuals.io/create |
| Product | virtuals.io |
| Whitepaper | whitepaper.virtuals.io |
| GAME docs | docs.game.virtuals.io |
| GAME GitHub | game-by-virtuals |
| X | @virtuals_io |
| Ventures | virtuals.vc |
Resources
- Virtuals Build
- Capital Formation Layer
- GAME documentation
- NEAR Intents (cross-chain outcomes) — different stack; useful when agents need non-Virtuals settlement paths
Keep reading
x402, AP2, MPP, ACP, TAP, UCP and PayPal Agent Ready get lumped together as "agent payments", but they sit at different layers. Two move money over HTTP 402, two prove who authorized what, two define a checkout, and one is a PSP adapter. Here is what each one looks like in code, what it settles on, what it costs where that is published, and how to pick.
Creator fees 1-10%. API key bb_liv for custom boards. LinkedIn omitted.
Prepare returns an unsigned payment transaction. Sign it locally. Submit. Poll the payment signature. Never pay twice.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
