Skip to main content
These tables are generated from the deterministic sizing scripts at commit 173463de92b6b04ed6bd43133a0c45f05deb6d3a. They describe the structural capacity of each settlement path given the current message formats, account layouts, and Solana transaction envelope.

Unilateral commitments

ShapeMessage BytesSerialized Tx BytesHeadroom vs Packet
Legacy unilateral commitment103627605
Current V4 typical unilateral commitment28552680
Current V4 conservative unilateral commitment29553679

Bundle settlement

ShapeLargest Entry CountSerialized Tx BytesSigned Message Bytes
Current V4 typical bundle61113168
Current V4 conservative bundle61119174

Cooperative clearing

ModeParticipantsChannelsSerialized Tx BytesMessage BytesAuth Envelope BytesRemaining Bytes
Current v0 + ALT balanced round77111963835113
Current v0 + ALT overall fit630114315381589
Hypothetical BLS v0 + ALT balanced round3232662213321570
Hypothetical BLS v0 + ALT overall fit1313912306037112

How to read this

  • Serialized Tx Bytes is the full on-wire transaction size, including all accounts and the Ed25519 verify instruction.
  • Message Bytes is the size of the signed body only.
  • Auth Envelope Bytes is the portion of the transaction dedicated to Ed25519 signatures and their pre-instruction data.
  • Remaining Bytes is the headroom left before the Solana packet limit.
  • The BLS rows are projections, not implemented wire formats today. They are included to illustrate roughly how much denser rounds could become under signature aggregation. See Roadmap.
The V4 shapes reflect the live deployment’s actual on-chain formats.

See also