Skip to main content
The table below is generated from the latest committed live demo snapshot for program Ba2puU8D2CLD1dYfRQ4YBXxirdyz3zVLLChvMf9AqJ1Y on devnet.
ScenarioParticipantsChannelsUnderlying PaymentsSettlement TxsSerialized Tx BytesSigned Message BytesSignature CountCompression
Scenario 1/5 — Latest Commitment Settlement2110164525110.00x / 9 tx saved
Scenario 2/5 — Commitment Bundle Settlement439214937534.50x / 7 tx saved
Scenario 3/5 — Clearing Round (Single Payer)32100,000,0002139237350,000,000.00x / 99,999,998 tx saved
Scenario 4/5 — Clearing Round (Bilateral)22100,000,0001798352100,000,000.00x / 99,999,999 tx saved
Scenario 5/5 — Clearing Round (Largest Executable v0 + ALT)551,666,666,66519856151,666,666,665.00x / 1,666,666,664 tx saved
ScenarioExplorer
Scenario 1/5 — Latest Commitment Settlementtx 1
Scenario 2/5 — Commitment Bundle Settlementtx 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 Agon 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 Agon’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