Solana plans to increase its maximum transaction size from 1,232 bytes to 4,096 bytes on Wednesday. The change is set to give developers more flexibility when designing transactions, while legacy formats will remain supported across the network.
Expanded transaction capacity
The larger limit aims to enable certain complex activities—including larger cryptographic proofs, multi-approval payments, and some confidential transfers—to be completed in a single Solana transaction rather than requiring several. Solana previously capped transaction size at 1,232 bytes, mainly due to legacy network constraints that required transactions to fit within a typical 1,280-byte internet packet.
Ethereum, another leading blockchain network, does not enforce a fixed transaction size. Instead, Ethereum users can include larger amounts of data when paying the necessary fees. Solana’s move brings its processing ability closer to that of data-flexible blockchains, potentially attracting more advanced developers and enterprise use cases.
| Blockchain | Previous Transaction Size Limit | New Transaction Size Limit | Transaction Size Flexibility |
|---|---|---|---|
| Solana | 1,232 bytes | 4,096 bytes | Fixed, but increased |
| Ethereum | Variable, by fee | Variable, by fee | Flexible, based on fee |
Technical upgrade and developer impact
The upgrade—known as Transaction v1—has been active on Solana’s development and test networks. Developers will be able to use either the new, larger transaction format or continue with current formats unless a given application requires the larger capacity.
The Solana Foundation, the nonprofit supporting Solana blockchain, stated that this change is backward compatible. Wallets and applications that do not require the larger limit do not need to update immediately, although some backend services and blockchain data providers must add support for Transaction v1 to ensure stability across the ecosystem.
Solana has implemented Transaction v1 in test environments to prepare for the rollout. Existing transaction formats will still work, allowing for a gradual transition for app developers and service providers.
Systems that read Solana blocks and transaction data must recognize the new format; otherwise, requests might fail. Priority fee information is also stored in a different section for Transaction v1, raising the need for updates in some data providers to maintain correct reporting.
Incorrect processing of transaction data can lead to user-facing platforms such as wallets, blockchain explorers, and trading apps displaying inaccurate details, a situation Solana’s engineering team advises service providers to avoid by upgrading promptly.
Mini dictionary: Solana Foundation, a nonprofit organization supporting the growth, development, and adoption of the Solana blockchain ecosystem through grants, education, and community resources.
Network effects and fee structure
Allowing bigger transactions is expected to increase network bandwidth use. With multiple large transactions competing for limited network resources, some users may have to pay higher priority fees to ensure timely processing. However, no additional fee based on transaction size is being introduced at this stage. Priority fees will remain optional and continue to depend on network demand and processing needs.
The decision to lift the size cap follows Solana’s transaction traffic system overhaul in 2022. The updated 4,096-byte threshold aligns with a standard four-kilobyte memory page widely used in validator hardware, offering technical consistency and potential performance improvements.
Governance and proposals
Solana’s community and technical leadership coordinated on this upgrade through formal proposals. The change is defined by two proposals, SIMD-0296 and SIMD-0385, co-authored by Jacob Creech and engineer Andrew Fitzgerald, who both serve in technical roles at Solana.
These proposals are separate from recent governance votes, including those regarding SOL issuance and changes to the network’s fee or supply mechanisms.
