[WIP] Router Evolution & Definitions

Router v1 — Task Broker (Today)

  • Surface: RESTful HTTP

  • Role: Web2-friendly task brokerage and session gateway

  • What it does: Receives user requests → creates/updates Session → enqueues tasks in SessionQueue → routes to Miner set via NodePool/NodeSpec

  • Validation: Basic hooks to Validator v2/v3 signals for routing hints

  • Payments: Standard SessionPayment (direct deposit) compatible

Router v2 — COR Prover (Agentic Validator PoC)

  • Surface: MCP + REST, x402 pay-per-call

  • Trust: ERC-8004-ready identity/validation artifacts

  • Role: Agent-facing validation service (LLM evaluation as a service) — validation only

  • What it does:

    • Accepts validate(input, candidate, policy) → runs k-redundant re-inference + PoI + Validator v3 LLM eval

    • Produces attestations (JWS / optional EIP-712) + evidence bundle (IPFS/Arweave)

    • Optionally writes ValidationResponse to ERC-8004 registry

  • Payments: x402 challenge at edge; receipts top-up session or SessionPaymentStaking pool

  • Status/Timing: Phase 4 (Testnet) as COR Prover MVP (PoC); no core protocol changes (uses delegated sessions)

Router v3 — Router Agent (Agentic Inference + Validation)

  • Surface: MCP + REST, x402, ERC-8004 registration (Identity / Validation; optional Reputation writes)

  • Role: Unified agentic AI infra surface for both inference and validation

  • What it does:

    • Inference: /v1/infer (one-shot or streaming), ephemeral sessions, k-redundancy options

    • Validation: /v1/prover/validate (PoI + PoUW + attestations)

    • SessionQueueValidation: emits TaskRoot (per-task Merkle) and updates SessionRoot (rolling ledger) for proof anchoring

  • Payments: x402 per-call and passes/quotas (post-Testnet); seamless with SessionPayment & SessionPaymentStaking

  • Status/Timing: Post-Testnet feature track (x402/8004 Phases 2–3) alongside Mainnet-Lite → Mainnet-Full

Future (v4+) — Generalized AI Infra Surface

  • Scope: Pluggable AI task types (RAG, eval suites, batch jobs, distillation, dataset labeling), hardware hints, policy-aware routing

  • Trust/Privacy: Deeper ERC-8004 reputation writes, TEE/TCME attestations (where applicable), and privacy-preserving sessions defaulted

  • Ops: Multi-tenant quotas, fine-grained SLAs, marketplace pricing, and partner OEM modes

PreviousTestnet Phases & Focus Areas (Structured Plan)NextTestnet & Mainnet Strategy

Last updated