Skip to main content

​
Phase 1: Private Beta Readiness

  • keep public app, docs, x402 gateway, OpenAPI, and llms.txt live
  • run sequential live smoke checks before each public push
  • create a private beta waitlist and Telegram channel
  • collect feedback from Somnia builders running testnet agents
  • publish a status page for frontend, x402, worker, and contracts
  • add short product clips to docs and social posts

​
Phase 2: Developer Adoption and Agent Onboarding

  • publish a reusable starter kit for x402 paid Somnia agents
  • publish a privacy-intent integration example
  • add contract ABIs as downloadable artifacts
  • expand the hosted MCP bridge with richer tool metadata, auth policies, and usage analytics
  • add examples for Claude Desktop, Cursor, and browser-based agents
  • add a guided “bring your own agent” onboarding wizard
  • add copy-paste agent endpoint templates for research, risk, routing, and invoice agents
  • publish Somnia DeFi adapter examples for Somnia Exchange, Somnex, Potion Swap, and custom DEX routers

​
Phase 3: Deeper Somnia-Native Agent Infrastructure

  • expand agent discovery with capability filtering and service reputation
  • add agent-to-agent hiring examples
  • add policy mutation proposals based on agent performance
  • add richer x402 settlement dashboards
  • add a public AgentReputationBook contract for completed work, disputes, and score history
  • add Somnia Reactivity subscriptions for order, invoice, card, policy, and privacy events
  • add Somnia Data Streams schemas for agent reputation, service telemetry, and beta usage
  • convert route/yield intents into deeper Somnia venue adapters as stable testnet router and vault infrastructure matures

​
Phase 4: Public Beta and Ecosystem Growth

  • launch an ArcPay Somnia X account
  • publish weekly build logs and verification receipts
  • onboard 10-25 testnet operators or agent builders
  • drive x402 protected endpoint usage from external builders
  • turn feedback into product issues and public changelogs
  • prepare grant/foundation package with usage, contracts, docs, and roadmap

​
Phase 5: ArcPay Labs Expansion

  • port the same product standard to future chain-specific ArcPay editions
  • keep chain-specific native primitives instead of shallow copies
  • share one common design system, CLI pattern, docs structure, and audit model
  • keep each edition’s docs chain-specific and avoid cross-chain claims in product copy