Solana plans to activate Transaction v1 on Wednesday, September 9, 2026, raising the network’s maximum transaction size from 1,232 bytes to 4,096 bytes and giving applications roughly 3.3 tim
Solana plans to activate Transaction v1 on Wednesday, September 9, 2026, raising the network’s maximum transaction size from 1,232 bytes to 4,096 bytes and giving applications roughly 3.3 times as much room to package complex operations into a single transaction, according to CoinDesk. The expanded format is designed to accommodate data-intensive workloads including zero-knowledge proofs, large multisignatures and confidential transfers. Transaction v1 will retain limits on the accounts and instructions a transaction can carry.
The 4,096-byte limit is set out in SIMD-0385, the Solana Improvement Document covering the Transaction v1 format. It compares with the existing 1,232-byte maximum, a difference of 2,864 bytes.
SIMD-0385 also caps v1 transactions at 64 accounts and 64 instructions. Those constraints define the practical scope of the larger payload: developers will be able to include more data in a transaction, but will still operate within fixed account and instruction limits.
The Solana Foundation says the size increase is defined by SIMD-0296 and implemented through v1 under SIMD-0385. Older transaction types are not being displaced; legacy and v0 transactions will remain supported alongside the new version.
Solana’s 1,232-byte transaction ceiling was a networking constraint, not an application-level design choice: a 1,280-byte IPv6 maximum transmission unit left 1,232 bytes for a transaction packet after network overhead, according to SIMD-0296. When Solana adopted QUIC in 2022, the fixed stream-size constraint was removed, allowing larger transactions without the old packet-derived limit. Transaction v1 formalises that capacity change, while the Solana Foundation says legacy and v0 transactions remain supported.
Graphic illustrating how three Solana transactions can be consolidated into one under Transaction v1. — Source: CoinDesk
The Solana Foundation identifies zero-knowledge proofs, large multisignatures and confidential transfers among the workloads expected to benefit from Transaction v1’s larger format. Before the change, workloads whose data exceeded the 1,232-byte limit could require multiple transactions or transaction bundles.
V1 allows more of an operation to fit into a single transaction, including signatures, proof data or instructions when those elements make up a substantial share of its serialized size.
The larger byte capacity does not remove the format’s other constraints: v1 transactions remain limited to 64 accounts and 64 instructions. Meeting the byte-size limit alone is therefore insufficient.
Activation alone will not make every transaction-reading service v1-aware. The Solana Foundation says infrastructure that reads transactions must support the new version and pass maxSupportedTransactionVersion: 1.
That requirement applies to the infrastructure layer handling v1 transactions, while legacy and v0 formats continue to work. The coexistence of formats gives applications a compatibility route, but services parsing transactions will need the specified version support to handle the larger format.
With the September 9 activation planned, SIMD-0296 supplies the increase in transaction-size capacity and SIMD-0385 defines the v1 transaction format, including its 4,096-byte, 64-account and 64-instruction boundaries.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
