Transaction v1 and the ALT Trade-off

Solana’s Transaction v1 format aims to reduce validator ingestion complexity by streamlining how transactions are parsed and scheduled. The new format introduces a larger 4,096-byte envelope, allowing applications that exceed the current 1,232-byte limit to operate. Changes include separating instruction headers from payloads and moving resource requests into transaction metadata, enabling earlier determination of fee and resource information with less state-dependent processing.

The v1 format’s impact on serialized size varies. While most structural changes have a bounded effect, removing ALT compression can significantly increase transaction size. For example, an account represented by a one-byte lookup index in v0 must be included as a full 32-byte public key in v1. This trade-off means transactions heavily reliant on ALT may see a notable increase in serialized size, partially offset by the removal of lookup-table addresses and prefixes.

A study of current ALT usage reveals that transactions referencing multiple tables or loading numerous addresses are most affected by the v1 format. The analysis reconstructs how existing ALT-reliant transactions would appear under v1, breaking down serialized size by components such as static account keys, compiled instructions, and lookup entries. The empirical data, drawn from a 30-day sample of 1/16 of transactions, shows a multimodal distribution of transaction sizes, reflecting recurring templates with stable account and instruction combinations.

The shift to v1 highlights a fundamental trade-off: expanded capacity versus increased serialized size for ALT-dependent transactions. Validators benefit from reduced parsing complexity, but applications leveraging ALT may face higher byte costs. The proposed format’s effectiveness depends on how much of the new envelope remains available for genuine application capacity versus accommodating the explicit account sets currently compressed by ALT.