ROADMAP · 65 ITEMS · uncommitted

What's built, what's funded, what's next.

Every item below lives in roadmap.yaml. This page renders from that file, so it cannot claim something the repo doesn't.

  • SHIPPED 6
  • IN BUILD 3
  • FUNDED 23
  • PLANNED 23
  • RESEARCH 10
Layer
Status

0

Rails ◇ SCF #45

The facilitator, the schemes, the Bazaar, the MCP server. This layer is the kernel everything above calls.

  • SHIPPED Facilitator live on stellar:testnet — /verify, /settle, /supported

    The three spec endpoints, running against Stellar testnet, callable right now.

    Live endpoint facilitator deployment down

  • SHIPPED /supported returns the Stellar extra, byte-identical to the x402.org baseline

    Includes areFeesSponsored: true. Byte-identical means a stock client needs no walras-specific branch.

    FACTS F-041 ↗

  • SHIPPED Unmodified stock @x402/fetch client completes real settled payments in CI on every push

    Accounts via Friendbot, testnet USDC acquired on the DEX at run time, zero stored secrets. The client is stock — no fork, no patch, no shim.

    CI run ↗settled tx ↗

  • SHIPPED 5 settlements, 5 settled, median settle 5.18 s

    Measured across CI runs, not projected. Replace with live aggregates once the observatory exists.

    EVIDENCE §S7-2 ↗

  • SHIPPED Public repo, Apache-2.0, license gate (zero copyleft)

    The gate fails the build if a copyleft dependency enters the tree.

    GitHub ↗

  • SHIPPED docs/FACTS.md and docs/EVIDENCE.md

    FACTS: every protocol claim dated and source-pinned. EVIDENCE: a transcript or a hash for every capability claim.

    Repo ↗

  • FUNDED T1 Facilitator hardening

    Channel-account pool for bursty agent traffic; idempotency and settle-retry with hash recovery; boot-time fail-closed invariants; full negative-path matrix (malformed XDR, wrong network / asset / amount / recipient, expired, replayed, sponsorship-safety violations) each returning a machine-readable, non-null reason.

  • FUNDED T1 Automatic cataloging on settle

    HTTP and MCP resources keyed on the spec tuple; schema soft-drop; routeTemplate percent-decoded before traversal checks; listings bound to the settled payment's recipient; EXTENSION-RESPONSES outcomes.

  • FUNDED T1 GET /discovery/resources

    The spec's six filters, stable cursor pagination.

  • FUNDED T1 Seller helpers

    One-line, framework-agnostic wrapper for discovery metadata (per-parameter descriptions), plus an LLM onboarding prompt that interviews a seller and generates their complete discovery manifest.

  • FUNDED T1 First paid MCP tool on Stellar

    A real Policywright tool priced in testnet USDC through walras, auto-cataloged by its first payment, keyed on (resource.url, input.toolName).

  • FUNDED T2 GET /discovery/search

    Hybrid lexical + semantic retrieval behind a stable Retriever interface; cursor pagination and partialResults per spec.

  • FUNDED T2 Published evaluation methodology

    Golden query set built from the real catalog with graded judgments; nDCG@10, MRR, recall@k published and enforced as a CI regression gate that demonstrably fails on a deliberately regressing commit.

  • FUNDED T2 upto scheme — spec, contract, upstream PR

    scheme_upto_stellar.md authored; minimal Soroban settlement contract (no admin, no upgrade path, no custody, no persistent balance) enforcing recipient binding, single settlement, ceiling and ledger time-bound via require_auth_for_args; facilitator-side validation; composition with smart-account spending policies documented; upstream PR opened and coordinated through the x402 TSC.

  • FUNDED T2 Threat model

    Every attack surface — payment forgery, catalog poisoning, listing spoofing, fee drain, replay — mapped to its control and its test.

  • FUNDED T2 Monitoring plan

    Alerts demonstrated firing against the live testnet deployment.

  • FUNDED T2 MCP discovery server v1

    search_resources and paid_call, deterministic schemas, one error vocabulary. Signing stays client-side; the server holds no keys.

  • FUNDED T3 Security review remediation

    Audit Bank findings resolved; fail-closed pubnet configuration.

  • FUNDED T3 Mainnet launch, both schemes

    exact and upto live on stellar:pubnet; conformance re-run on both networks; settled hash published per network per scheme.

    Depends on: Security review remediation

  • FUNDED T3 Developer guide, contributed to Stellar Developer Docs

    Role-based — seller / buyer & agent / operator — with live testnet examples.

  • FUNDED T3 Two end-to-end examples

    A paid API discovered and paid by an agent; an MCP agent paying with no pre-baked integration. Both runnable from a clean clone.

  • FUNDED T3 Migration path

    Helpers plus a guide, with one worked port of an existing Base/Solana x402 seller adding stellar:pubnet at config level.

  • FUNDED T3 Production operations

    Runbook; live monitoring and public status page (aggregate metrics only, no PII); degraded-mode behavior documented; spec-change tracking with a named maintainer and a stated conformance-update cadence through and beyond the grant.

  • FUNDED T3 Professional user testing

    Per SCF requirement: a first-time developer measured from docs to a paid, discoverable endpoint in under an hour.

1

Merchant OS ◆ Product

The gap between “x402 middleware exists” and “a business runs on this.” Where Cloudflare and Stripe are pointing on Base, and where Stellar's rails are quietly unfair.

  • PLANNED Gateway mode

    Reverse proxy in front of any existing API; payment-gate a route with zero code changes. A self-serve version of what Cloudflare has behind an early-access waitlist.

  • PLANNED Merchant console

    Revenue, per-resource analytics, request/settle funnel, error taxonomy. Reads the same public endpoints agents read.

  • PLANNED Signed receipts + webhooks

    Every settlement emits a verifiable receipt; webhook on settle and on dispute-window close. Receipts become the substrate for Layer 3 reputation.

  • PLANNED Accounting exports

    CSV / ledger-shaped exports, per-period statements.

  • PLANNED Pricing tools

    Tiered pricing, free-tier quota, per-caller rate limits, promotional zero-price windows.

  • PLANNED Treasury: path-payment settlement

    Accept any SEP-41 asset, receive USDC atomically. Stellar-native; no equivalent on Base or Solana.

  • PLANNED Anchor off-ramp (SEP-24 / SEP-6)

    Agent pays USDC, merchant receives local fiat in a bank account. The demo no other x402 stack can run — highest-leverage item on this page.

  • RESEARCH Protocol plurality

    MPP session support alongside x402 exact / upto, one install. MPP is live on Stellar with Stripe/Tempo distribution; merchants shouldn't have to bet on a protocol.

    Depends on: MPP session semantics stabilising

2

Agent OS ◆ Product

The buyer side. Not rebuilding smart accounts — building the x402 policy layer and the UX on top of the audited ones.

  • PLANNED x402 policy pack on OpenZeppelin smart accounts

    Per-call cap, per-day cap, per-merchant allowlist, per-scheme rules. SDF already points x402 builders at these contracts; the gap is the x402-shaped policy set.

  • RESEARCH Kernel-key delegation via CAP-71

    Protocol 27 “Zipper” makes authentication delegation for smart contract accounts first-class; revisit once mainnet.

    Depends on: Protocol 27 on mainnet

  • PLANNED Spend console

    Per-agent attribution, budget burn-down, kill switch.

  • PLANNED Receipts vault

    Every payment an agent made, exportable, verifiable.

  • PLANNED SDK adapters

    Python, LangChain, Vercel AI SDK, OpenAI Agents SDK, plus the MCP path. @x402/fetch alone is not where agents actually live.

  • PLANNED CCTP funding path

    Fund a Stellar agent wallet from Base/other USDC in seconds. Circle CCTP launched on Stellar in May; kills the cold-start objection.

  • PLANNED Pesalo integration

    Consumer wallet as the human face of the agent budget. First-party; native walras integration.

3

Market & trust ◆ Product

The Bazaar, made browsable by humans and trustworthy for machines.

  • IN BUILD Human Bazaar at /browse

    The catalog as an order book of services. Consumes the same public /discovery endpoints agents use — permanent visible dogfooding.

    /discovery/resources facilitator deployment down

  • PLANNED One-click playground

    Pay a catalogued service in-browser with Freighter for a cent. The fastest possible “I get it” moment.

  • PLANNED Uptime probes + SLA badges

    Derived from real settlement data, not self-reported.

  • PLANNED Seller reputation from signed receipts

    Settlement count, success rate, median latency. Ethereum got ERC-8004 for agent identity in January; Stellar has nothing yet.

  • PLANNED Curation & collections

    Categories, editorially grouped sets, no paid placement.

  • FUNDED T2 Neutrality guarantee

    House listings receive zero ranking preference, verifiable in code; ranking config published. Locked decision — it survives every layer above.

4

Observatory ◆ Product

Coinbase publishes Base's x402 numbers constantly. Stellar's are invisible. Fixing that is nearly free — the indexing already exists for Tranche 3 telemetry. Working name: walrascan.

  • FUNDED T3 Public metrics

    Settled transactions, distinct payers, catalog size, median latency, all networks. Funded as the T3 status page, then extended.

  • PLANNED Per-seller public pages

    A shareable page per catalogued service.

  • PLANNED Cross-facilitator conformance board

    The same suite run against every Stellar facilitator, results public.

  • PLANNED Periodic ecosystem reports

    What got paid for on Stellar this month.

5

Confidential x402 ⬡ Upstream

Every agent's usage graph is currently public on every x402 chain — who your agents pay, how often, at what volume. Nobody has an answer. Stellar just shipped the primitives for one.

Dependency, stated plainly: Confidential Tokens is a Developer Preview — live on testnet, contract and verifier audits underway, not approved for mainnet. Nothing in this layer ships to mainnet before that does. Spec work proceeds now; implementation is testnet-only until then.

  • RESEARCH exact-confidential scheme spec

    Settlement executes inside the Confidential Token wrapper; the client proof shows the hidden transfer pays the quoted price to the advertised recipient; the facilitator verifies a proof instead of a plaintext amount.

    Depends on: Confidential Tokens leaving Developer Preview

  • RESEARCH Reference implementation on testnet

    Against the OpenZeppelin suite + Nethermind UltraHonk verifier.

    Depends on: exact-confidential scheme spec

  • RESEARCH upto-confidential

    Metered billing where the settled amount is hidden — usage volume stays private. Composes with the Layer 0 upto contract.

    Depends on: Layer 0 upto contract

  • RESEARCH Selective-disclosure receipts

    The wrapper's disclosure primitive is the receipt: prove a specific payment to a specific party without exposing the rest.

  • RESEARCH Auditor view-key mode for merchants

    Auditable privacy, not opaque privacy — the framing SDF is already committed to.

  • RESEARCH ZK seller stats

    Prove “>N settlements, <X% failure rate” for Bazaar ranking without revealing revenue.

  • RESEARCH Upstream: confidential scheme through the x402 TSC

    SDF holds a Premier seat on the x402 Foundation Governing Board and will want a flagship reason for it.

Ecosystem & standards ⬡ Upstream

Work that belongs to everyone: specs, docs, and suites contributed upstream rather than kept.

  • FUNDED T2 upto scheme spec + contract, upstream to x402

    Authored, implemented, and coordinated through the x402 TSC rather than kept private.

  • FUNDED T3 Stellar Developer Docs contribution

    Role-based x402 guide, contributed upstream.

  • FUNDED T3 Migration guide for existing Base/Solana x402 sellers

    One worked port, config-level.

  • RESEARCH Confidential scheme proposal

    Through the x402 TSC, once the primitives are mainnet-eligible.

    Depends on: Confidential Tokens leaving Developer Preview

  • PLANNED Conformance suite published for any facilitator to run

    Including the ones competing with walras. That's the point.

  • PLANNED llms.txt, /.well-known/x402, and a public MCP endpoint for walras itself

    The project's own machine-readable surface.

First-party sellers ◆ Product

Adoption is designed in, not hoped for. walras's own services, listed on the same terms as anyone else's — zero ranking preference.

  • IN BUILD Policywright (SCF #44) — first paid MCP tool on Stellar, via walras

    T1 code-complete, submitted ahead of target.

  • IN BUILD Nectar Network (SCF #42) — planned walras-discoverable seller

    Live on testnet with real TVL; T3 + audit submitted; mainnet targeted Sept/Oct 2026.

  • PLANNED Pesalo — buyer-side wallet with native walras integration

    In development.