Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ryvo.network/llms.txt

Use this file to discover all available pages before exploring further.

Managed micropayment rails, Circle Nanopayments is the most visible example, validate the core market thesis: machine commerce wants cheap, deferred settlement. Ryvo 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:
  • Access to the rail depends on the operator’s continued availability, pricing, and policy.
  • The operator decides whether your payment or payout is processed right now.
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 Ryvo commits to instead

Ryvo is deliberately a public clearing substrate rather than a managed rail. Concretely:
  • 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 Ryvo meet

Ryvo does not reject operator-centric business models. It moves them up the stack. You can build a Circle-style nanopayment product on top of Ryvo:
  • 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.
  • A policy layer that chooses how and when to serve requests.
The difference is that the substrate under that operator stays open:
  1. Many hubs can coexist.
  2. Users and providers are not bound to one global operator just to access settlement.
  3. Managed products can sit on top, but they are no longer the base settlement layer.
For Circle specifically, the main contention is service-denial risk at the operator layer, not “funds are trapped forever.” Permissionless withdrawal can still exist at the contract layer while service access remains policy-controlled.

​
Summary

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

​
See also