caelum0x c93c35f07c docs(roadmap): reframe as the credit protocol for the x402 economy + phase plan
Cred402 is the credit & reputation layer for ALL x402 services — RWA verification
is the first wedge, not the whole product. Add docs/roadmap/ with the forward
phase plan (p1–p6): universal x402 receipts, the x402 Gateway wedge,
credit-as-a-service, mainnet-beta credit market, omnichain credit, and
decentralization + the data moat. Broaden README positioning + link the roadmap.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-17 03:00:14 +03:00

2.2 KiB

p1 — Universal x402 receipts (beyond RWA)

Make Cred402 the credit layer for all x402 services, not just RWA. Today the credit path leans on RWA evidence; this phase generalizes it so any x402-payable machine service — data, compute, inference, storage, API calls, RWA verification — is a first-class credit input.

Why

RWA verification was the wedge that proved the loop. But the protocol's value is general: any agent that earns through x402 has a verifiable cash flow, and any verifiable cash flow can underwrite credit. Constraining credit to RWA evidence caps the addressable market to one vertical. The x402 economy is every paid agent-to-agent interaction.

Scope

  • Service taxonomy, generalized. Replace the RWA-centric service types with an open service_category taxonomy: data.*, compute.*, inference.*, storage.*, api.*, rwa.*, defi.*, compliance.*. Each category carries a risk weight and (optional) evidence schema.
  • ServiceCategoryRegistry (on-chain). Governance-managed registry of approved categories + per-category caps and risk weights. New categories are added by governance, not hardcoded.
  • Decouple receipt from evidence. The X402ReceiptRegistry becomes the universal cash-flow primitive; RWA evidence becomes an optional enrichment that boosts a receipt's weight for RWA categories. Non-RWA services build credit from finalized receipts alone.
  • Credit formula update. eligible_revenue sums finalized x402 receipts across all categories, weighted by category risk + counterparty diversity — no RWA requirement.

Deliverables

  • ServiceCategoryRegistry Odra contract + ledger mirror + tests.
  • Generalized receipt/credit path in lib/core + lib/ledger (category-weighted).
  • A non-RWA demo: an inference/data API agent earns x402 revenue → builds credit.
  • Docs: updated risk_model.md (category weighting) + service taxonomy reference.

Success metric

An agent selling a non-RWA x402 service (e.g. an inference endpoint) qualifies for and draws a credit line from purely its x402 receipt history.

Out of scope

New chains (p5), mainnet liquidity (p4), third-party embedding (p3).