The site is becoming a public proof surface for agent commerce.
The roadmap is deliberately evidence-first: live testnet proof, developer entrypoints, wallet-agent boundaries, and a closed mainnet gate until external review artifacts exist.
Strategic roadmap for the Ergo Agent Economy public proof surface. It is not an audit report and does not open mainnet readiness.
One public surface for claims, proofs, and gates.
Make ergoblockchain.org a live proof surface where developers, wallets, agents, and reviewers can inspect state, proofs, APIs, receipts, and trust gates from one public source of truth.
One source of truth for proof data; pages render or link to it instead of duplicating it.
Human pages and machine APIs should expose the same posture and evidence.
Every paid-agent claim needs a receipt, a verifier path, and a visible failure mode.
Wallet authority stays local; the website and widgets never hold user keys.
Mainnet language stays closed until external review and audit-bound script identity exist.
Live, next, gated, later.
Each lane links to public evidence instead of asking readers to trust a roadmap claim.
Live now
Live Proof Surface
The site already exposes a testnet Sage payment flow, full receipt bundle, signed L1 conformance evidence, public MCP endpoint, Proof Explorer, Live Hub, and developer services.
Developer Launch Path
A builder can start from Agent Hub, read the discovery descriptor, call OpenAPI-described endpoints, try stateless developer tools, and embed the Sage widget in testnet mode.
Build next
Embeddable Paid Sage Widget
Move the published widget from a strong v0.3 payment surface toward a polished host demo: quote, wallet launch, verification, chat, receipt callback, tenant config, and failure-state UX.
Wallet-Agent Reference Layer
Turn policy-check, playground, and runner into a tighter reference path for local wallet agents: intent intake, policy verdict, simulation, host-owned signing, broadcast, and receipt retention.
Trust gated
External Review Gate
Publish an independent review or audit artifact that pins scope, findings, residual risks, and what remains excluded before any mainnet wording changes.
Audit-Bound Mainnet Script Identity
Publish exact source-to-ErgoTree mapping, package versions, script hashes, addresses, limits, and reviewer binding before any controlled mainnet launch.
Later
Agent Marketplace And Provider Registry
Expose provider profiles, payment capabilities, conformance state, uptime, receipt examples, and safety metadata so agents can choose services by evidence instead of copy.
The strategic map is also machine-readable.
These paths are the stable entrypoints for builders, agents, and reviewers.
What moves the site to the next level.
Repo work can keep moving locally. Trust gates require external review artifacts before public posture changes.
Polish a hosted Sage widget demo for third-party embedding
Tighten wallet-agent runner around policy, simulation, signing boundary, and receipts
Publish external review findings and residual risk manifest
Bind mainnet script identity to reviewed source and exact deployment artifacts
Still closed by design.
The current public state is stronger because it refuses to blur testnet proof with production readiness. The remaining blockers are explicit and externally gated.
A testnet observed identity manifest is published; mainnet still needs audited source-to-ErgoTree mapping, package versions, and deployment identifiers for every payment primitive.
A draft audit scope manifest is published; signed external review findings are still required before any mainnet language.