Skip to content

Roadmap

LedgerFlow is evolving from a focused authorization protocol into the standard payment authorization layer for AI agents.

Current: v1 (In Development)

The core protocol and reference implementation.

Protocol

  • Warrant format specification
  • Proof-of-authorization model
  • x402 extension schema
  • Constraint type system
  • Delegation policy
  • Replay protection mechanism

Implementation

  • ledgerflow-core — warrant, proof, digest, constraints
  • ledgerflow-x402 — extension parsing, verification, replay storage
  • ledgerflow-facilitator — rail adapter routing
  • ledgerflow-cli — development tools and fixtures

Acceptance

  • BDD scenarios pass end-to-end
  • Two rail adapters operational (EVM + Exchange)
  • CLI tooling for warrant issuance and verification

v2: Ecosystem Expansion

New Rails

  • Solana rail adapter
  • Additional exchange integrations (Bybit, Coinbase)
  • Stripe / PayPal fiat backstop

Revocation

  • Signed Revocation Lists (SRL)
  • Consistency tokens (ZedToken-inspired)
  • Distributed revocation service

SDK

  • Python SDK
  • TypeScript SDK
  • WASM module for browser/edge

Integrations

  • MCP server integration
  • A2A delegation protocol
  • LangChain / LangGraph middleware

v3: Enterprise & Advanced Features

Policy

  • Constraint templates for common patterns
  • Multi-tenant warrant management
  • Conditional constraints with typed context

Performance

  • Batch verification
  • Hardware acceleration for signature verification
  • Warrant caching with distributed invalidation

Governance

  • Warrant issuer registry
  • Constraint type registry (IANA-style)
  • Protocol versioning and deprecation policy

Long-Term Vision

LedgerFlow aims to become the standard authorization layer for autonomous economic agents. As AI agents become first-class participants in the economy, the need for bounded, auditable, cryptographically verifiable payment authorization becomes critical infrastructure.

Today:    Human pays → x402 → Settlement
v1:       Agent pays → x402 + LedgerFlow → Settlement
Future:   Agent ecosystem → LedgerFlow authorization → Multi-rail settlement

The protocol is intentionally narrow in v1 to prove the product thesis before expanding. The extension model ensures backward compatibility as new features are added.

Contributing

LedgerFlow is open source under Apache-2.0. Contributions are welcome:

  • Protocol design — contribute to the specification
  • Implementation — help with Rust crates and rail adapters
  • Documentation — improve and expand documentation
  • Testing — add acceptance scenarios and edge cases

See Also