Live Devnet Benchmarks - Ryvo Protocol

The table below is generated from the latest committed live demo snapshot on devnet. See Deployment for the current live program ID.

Scenario	Participants	Channels	Underlying Payments	Settlement Txs	Serialized Tx Bytes	Signed Message Bytes	Signature Count	Compression
Scenario 1/5 - Latest Commitment Settlement	2	1	10	1	645	25	1	10.00x / 9 tx saved
Scenario 2/5 - Commitment Bundle Settlement	4	3	9	2	1493	75	3	4.50x / 7 tx saved
Scenario 3/5 - Clearing Round (Single Payer)	3	2	100,000,000	2	1392	37	3	50,000,000.00x / 99,999,998 tx saved
Scenario 4/5 - Clearing Round (Bilateral)	2	2	100,000,000	1	798	35	2	100,000,000.00x / 99,999,999 tx saved
Scenario 5/5 - Clearing Round (Largest Executable v0 + ALT)	5	5	1,666,666,665	1	985	61	5	1,666,666,665.00x / 1,666,666,664 tx saved

Explorer links

Scenario	Explorer
Scenario 1/5 - Latest Commitment Settlement	tx 1
Scenario 2/5 - Commitment Bundle Settlement	tx 1, tx 2
Scenario 3/5 - Clearing Round (Single Payer)	tx 1, tx 2
Scenario 4/5 - Clearing Round (Bilateral)	tx 1
Scenario 5/5 - Clearing Round (Largest Executable v0 + ALT)	tx 1

How to read this

Underlying Payments is the number of individual payments the scenario represents if every payment were settled on-chain independently.
Settlement Txs is the number of actual on-chain transactions Ryvo used to settle all of them.
Compression is the ratio of the two, and the second number is total transactions saved.
Signed Message Bytes is the Ed25519-signed body size, not the full transaction.

The clearing-round scenarios (3, 4, 5) intentionally set the cumulative targets to large values to illustrate that Ryvo’s compression does not care about the size of the underlying obligations. The settlement cost is a function of the signed round, not of the payments it represents.

See also