The Solana Foundation has raised the maximum size of a single transaction from 1,232 to 4,096 bytes — a 3.3x increase. The new limit applies only to the v1 transaction format; the legacy and v0 formats remain unchanged.
The old 1,232-byte limit had long been a holdover from the network's architecture rather than an actual requirement. It was tied to the size of a network packet that could be transmitted without fragmentation.
Since 2022, Solana transactions have been transmitted over the QUIC protocol, which has no such hard ceiling. The old limit simply stayed in place out of inertia.
Developers chose 4,096 bytes specifically because it matches the typical memory page size of a validator, so a transaction no longer crosses that boundary, which simplifies processing.
What the New Format Enables
The old limit made it impossible to fit heavy operations into a single atomic transaction. Developers had to split ZK proofs, large multisig setups, and batch calls into a chain of transactions or bundle them together to guarantee joint execution.
The v1 format accommodates zero-knowledge proofs, including confidential transfers, nested multisig setups, and other complex signature schemes.
Network throughput itself doesn't increase. What changes is the amount of data inside an individual transaction, not the number of transactions per second — compute resource limits and the number of signatures remain the same.
What Market Participants Need to Know
Sending transactions in the v1 format remains optional: wallets and applications that are fine with the old limit don't need to make any changes.
But services that read, index, or pay for other people's transactions — exchanges, analytics platforms, wallets — will need to update their infrastructure to support the new format. Without an update, such services risk mishandling blocks and transactions that use the v1 format.
The logic behind priority fees is also changing: the fee is now set as a fixed amount for the entire transaction, rather than calculated per unit of compute resources as before.
Larger transactions require more network resources, so they will likely come with a higher fee compared to shorter transactions of the same priority.