Every chain. One view.

A settlement has three encoding layers. Open each result's byte-layout explanation below to see the concrete sizes and values for that transaction.

1. Ethereum blob packing

   The L1 type-3 transaction commits to one or more blobs by versioned hash. Each 131,072-byte blob contains 4,096 field elements. EEZ requires the most-significant byte of every 32-byte element to be zero and stores 31 logical bytes in the remaining bytes, in reverse order. That gives 126,976 logical bytes per blob.

2. EEZ version-0 message envelope

   00version02ChainOperationchain_idu64 little-endianlengthbase-128 u32 varintoperationspayload bytes01CloseBlobStream00…padding

   The native profile accepts one ChainOperation for synchronization, followed by complete InitiateCrossChainTransaction brackets containing Call, StaticCall, returns, and optional Snapshot/Revert regions. One CloseBlobStream ends meaningful bytes; all remaining blob bytes must be zero.

3. Cross-chain semantics

   These are separate envelope messages after ChainOperation, not fields inside ChainOperation.operations. Each semantic transaction names its origin chain and carries opaque chain-defined tx_data. Calls encode the destination chain, source and target addresses, value for mutable calls, zero gas in this deployment, and exact calldata. ReturnSuccess/ReturnFail carry exact result bytes. The context stack derives every call's source chain.

   Byte / message	Wire fields	Meaning
   0x03 Initiate	origin_chain:u64 LE · len:varint · tx_data	Starts one originating cross-chain transaction.
   0x04 Call	to_chain · from · to · value:u256 LE · gas · len · data	Opens a mutable nested call.
   0x05 StaticCall	to_chain · from · to · gas · len · data	Opens a read-only nested call; no value field.
   0x06/07 Return	len:varint · return_data	Closes the most recent call with success or failure.
   0x08/09 Snapshot/Revert	no payload	Brackets a non-empty contiguous call region whose state effects are forcibly rolled back.
   0x0a Finish	no payload	Closes the semantic transaction after all calls and snapshots close.

   A failed return and a forced rollback are different facts: ReturnFail records one call's result, while Snapshot … Revert marks the whole enclosed call span as rolled back. The result view exposes both independently.

4. Tagged operation payload

   The first operation byte selects an RLP body:

   Tag	Format	RLP body
   0x00	Legacy calldata	[blockTxCounts, transactions, l2Entries]
   0x01	Grouped calldata	[blockTxCounts, transactions, l2Entries, outboundGroupSizes]
   0x02	Self-contained blocks	[blocks, l2Entries, outboundGroupSizes]

   For tag 0x02, every element in blocks is a complete canonical block RLP carrying the header, transactions, ommers, and applicable body fields. The decoder derives transaction counts from those bodies. l2Entries carries ABI-encoded execution entries needed for reconstruction; outboundGroupSizes records how many source roots each outbound user transaction consumes.