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.

Ryvo publishes two benchmark families, one grounded in live devnet execution, one grounded in deterministic wire-format sizing. Both are generated from committed artifacts rather than hand-maintained prose, so every number on these pages traces back to a reproducible source.

​
Live devnet benchmarks

Live benchmarks come from the protocol-only devnet demo. Each scenario captures:
  • scenario shape (participants, channels, underlying payments)
  • explorer links for every submitted transaction
  • serialized transaction bytes where measured
  • settlement compression against an exact-payment baseline
The demo script writes a machine-readable manifest to config/ryvo-protocol-demo-last-run.json, and the docs build turns that manifest into the Live devnet benchmarks table. Re-running the demo and the benchmark generator publishes fresh numbers without editing markdown by hand.

​
Synthetic capacity benchmarks

Synthetic benchmarks come from deterministic sizing scripts inside the protocol repo. They measure the structural capacity of each settlement path:
  • unilateral commitment message density
  • bundle settlement limits
  • cooperative clearing-round headroom
  • projected BLS headroom
These are not live transactions, they are bounded-size reconstructions of what will fit on the wire given the current message formats, account layouts, and Solana transaction envelope (v0 with Address Lookup Tables). They are published in Synthetic capacity benchmarks.

​
Source of truth

The generated pages in this section are built from committed JSON snapshots rather than hand-maintained copy. Each snapshot is pinned to a specific commit of the protocol repo and a specific program deployment. If you are citing Ryvo benchmarks externally, link the specific snapshot page and cite the protocol commit and program ID shown on it. That way the numbers remain verifiable over time, even as the deployment evolves.

​
See also