Solana Doubles Down On Transaction Capacity

Solana is tripling its transaction size limit to 4,096 bytes on September 9. This change, proposed in SIMD-0296 and implemented by Anza engineers Jacob Creech and Andrew Fitzgerald, will allow for more complex transactions without fragmenting data. The original 1,232-byte limit was a relic of the network's IPv6 MTU constraints but became pointless after Solana switched to QUIC in 2022.

The new limit is based on validator hardware page constraints, with each transaction restricted to a single standard 4 KiB page of memory. This change will accommodate workloads that exceed the old limit, including zero-knowledge proofs and large multisig configurations. Jito bundles, which allowed developers to merge up to five transactions into an all-or-nothing sequence, are now obsolete.

Transaction v1, introduced with this update, is opt-in for senders and will not affect legacy or v0 transactions. However, data tools and block explorers must be updated to handle the new format, as they will completely freeze or spit out errors if not. Anza requires RPC providers to upgrade to Agave v4.2, and Helius has issued a migration checklist detailing the work.