Skip to main content
Managed micropayment rails — Circle Nanopayments is the most visible example — validate the core market thesis: machine commerce wants cheap, deferred settlement. Agon agrees with that thesis and differs on where trust and control live.

​
What a managed rail gives up

A managed rail makes micropayments cheap by concentrating authorization and settlement inside a single operator. In exchange for that operational efficiency:
  • Balances typically sit inside the operator’s accounts rather than in protocol state.
  • Participants authorize payments against the operator’s ledger, not against a shared on-chain substrate.
  • Access to the rail depends on the operator’s continued availability, pricing, and policy.
  • The operator chooses who can settle, when, and under what terms.
For many commercial use cases this is an entirely reasonable trade. Users accept counterparty and policy risk in exchange for lower fees and smoother UX.

​
What Agon commits to instead

Agon is deliberately a public clearing substrate rather than a managed rail. Concretely:
  • Funds live in Agon’s on-chain state, not inside an operator’s ledger.
  • Any wallet can register as a participant. There is no central admission.
  • Multiple operators can exist simultaneously and compete.
  • No operator can unilaterally prevent a user from settling or withdrawing.
These are protocol-level guarantees. See Trust model and On-chain properties for what is enforced on-chain.

​
Where managed models and Agon meet

Agon does not reject operator-centric business models. It moves them up the stack. You can build a hub-style operator on top of Agon that looks very similar to a managed micropayment product:
  • A single brand, one UX, one SLA.
  • A coordinated matching layer that aggregates demand and provides “guaranteed capacity” experience for users.
  • A pricing and routing layer between users and providers.
The difference is that the substrate under that operator stays open:
  1. Many hubs can coexist.
  2. Balances remain in protocol state, not in the hub’s ledger.
  3. Users and providers are not bound to one global operator just to access settlement.
See Operator hubs for the hub construction in detail, and Authorized settler for the specific delegation primitive that hubs typically use.

​
Summary

  • A managed rail optimizes for operational simplicity at the cost of operator neutrality.
  • Agon optimizes for operator neutrality and composability, and lets operators be built on top.
  • Both answers can be right — for different product constraints.

​
See also