Key highlights:

  • Solana will raise its maximum transaction size from 1,2332 to 4,096 bytes on September 9
  • The 3.3x increase could enable larger ZK proofs, multisig transactions, and on-chain cryptographic operations to fit into a single transaction
  • Transaction v1 is part of Solana’s broader effort to make the network capable of handling more sophisticated applications

Solana is preparing to activate an upgrade that will increase the maximum size of a single transaction by more than three times, giving developers more room to execute complex transactions. Transaction v1 is scheduled to go live on Solana’s mainnet on September 9, raising the limit from 1,232 bytes to 4,096 bytes.

Solana transaction limit jumps 3.3x 

The upgrade will increase Solana’s maximum serialized transaction size by 3.3 times, eliminating a hurdle that has limited how much data developers can include in a single transaction.

The change comes through SIMD-0296, which establishes the larger transaction size, and SIMD–385, which introduces the Transaction v1 format needed to support it. Solana’s existing legacy and v0 transactions will continue to work, while applications can adopt v1 when they need the additional capacity.

The original 1,232-byte limit was linked to Solana’s historical use of a 1,280-byte IPv6 maximum transmission unit. The network’s adoption of QUIC makes it possible to support larger transactions without the constraints of the original networking limitation.

Additional space will allow developers to put operations into a single atomic transaction that previously had to be split across multiple transactions. Solana identifies zero-knowledge proofs, large multisignature transactions, and on-chain cryptographic schemes such as BLS signatures among the workloads that can benefit from the larger format.

The upgrade does have a trade-off. Transaction v1 removes the use of address lookup tables, meaning accounts that would have previously been represented through compressed lookup references may consume more space as full public keys. 

Solana’s analysis suggests that the headline 4,096-byte limit does not translate into 4,096 bytes of entirely new application payload for every transaction.

Another step in Solana’s scaling push

Transaction v1 arrives as Solana continues to make changes aimed at increasing the network’s capacity for sophisticated applications. 

The network has also been working on higher block compute capacity and shorter slot times. Solana recently outlined plans to reduce slot times from 400 milliseconds to 200 milliseconds, while its Agave 4.2 release includes the larger transaction-size change.

Transaction v1 has already reached Solana’s testnet, with mainnet activation scheduled for September 9. SOL price fell by 2% over the last day, with the upgrade failing to make an impact on the asset’s price.

 

In other protocol news, Solana validators voted on two governance proposals to reduce the network’s token supply by increasing the amount of SOL burned via transaction fees. 

Meanwhile, Ethereum is also targeting substantially greater execution capacity. The Ethereum Foundation says the network’s gas limit has moved from 30M to 60M, with further increases part of its 2026 scaling priorities.