Solana is set to activate Transaction V1 on mainnet on September 9, introducing a larger transaction format that lifts the maximum size of a single transaction from 1,232 bytes to 4,096 bytes.
The change is linked to the SIMD-0296 proposal and is intended to let more complex workloads complete in one atomic transaction rather than being split across multiple calls.
A larger transaction format for mainnet
Under Transaction V1, Solana will allow far more data to be carried in a single transaction than the current format permits. The new 4,096-byte cap is designed to fit within a single 4 KiB memory page on validator hardware, according to the SIMD-0296 proposal on GitHub.
That technical limit matters because the previous 1,232-byte ceiling forced some applications to break work into separate transactions. With the new format, tasks that previously exceeded the cap can be packaged into one transaction instead.
What the upgrade enables
The added space is expected to support workloads that have been difficult to fit into Solana’s existing transaction envelope. The source article cites zero-knowledge proofs, large multisig setups, and other advanced payloads as examples of operations that can benefit from the larger size limit.
It also changes how some bundled activity can be handled. Jito bundles, which had been used to combine multiple transactions into an ordered sequence, may now be replaced in some cases by a single atomic transaction executed directly at the base layer.
Upgrade risks for infrastructure providers
The transition also carries operational requirements for Solana service providers. RPC providers, indexers, and wallets that do not upgrade to Agave v4.2 risk compatibility problems once v1 transactions begin appearing on mainnet.
According to the source article, unprepared RPC calls can return error -32015. Anza also said that systems skipping the upgrade may produce silently incorrect fee data, creating a less visible but potentially important issue for services interacting with the network.
What happens next
The confirmed next step is the September 9 mainnet activation of Transaction V1. Once live, the change will expand the practical range of applications that can be submitted as a single Solana transaction while putting pressure on ecosystem infrastructure to support the new format promptly.
Whether developers immediately shift complex flows from multiple transactions or bundles into one atomic call will depend on how quickly wallets, RPC operators, and other tooling providers complete their Agave v4.2 upgrades.
Source: Cryptopolitan