Solana is targeting Wednesday to triple its maximum transaction size from 1,232 bytes to 4,096 bytes, letting developers fit complex operations that once needed multiple transactions into one. The change, called Transaction v1, requires software that reads Solana data to update or risk showing broken or missing information.
Solana is set to raise its maximum transaction size from 1,232 bytes to 4,096 bytes on Wednesday, giving developers more than three times as much room to pack instructions into a single operation. The new format, called Transaction v1, is already running on Solana's test and development networks.
Bigger transactions, fewer steps
Operations that once had to be split across several transactions can increasingly fit into one under Transaction v1, including large cryptographic proofs, payments requiring many approvals and some confidential transfers. Existing transaction formats remain supported, so wallets and apps do not have to switch to v1 unless they need the extra space.
The upgrade could help Solana sharpen its edge over Ethereum. Solana has always been faster and cheaper than its rival, but it previously trailed in one area: its transactions were hard-capped at 1,232 bytes, while Ethereum has no rigid protocol size limit and lets developers run data-dense applications in a single operation by paying a higher fee. By more than tripling its ceiling to 4,096 bytes, Solana is looking to close that gap.
Software that reads Solana must catch up
The larger change falls on services that fetch blocks and transactions rather than on end users. If those services are not updated to recognize v1, requests can fail when they hit the new format. Some software also needs to change where it looks for priority-fee data, since v1 stores that information elsewhere — outdated software can show a fee of zero even when a user paid one.
Wallets, explorers and trading apps often rely on these services to display what happened onchain, so bad data behind the scenes can turn into bad data on a user's screen. Larger transactions also draw more network bandwidth, and developers expect users may need to offer higher priority fees when big transactions compete for space, though the upgrade adds no new per-byte fee.
Why the limits sit where they do
The old 1,232-byte cap traces back to Solana's original networking design, where each transaction had to fit inside a roughly 1,280-byte internet data packet — a constraint that eased after Solana changed how transaction traffic is transmitted in 2022. The new ceiling stops at 4,096 bytes because four kilobytes is a standard memory-page size on validator hardware; going larger could force a transaction to span multiple pages and raise processing costs for the machines that run Solana.
The change is defined in two proposals, SIMD-0296 and SIMD-0385, co-authored by Jacob Creech and Andrew Fitzgerald, and is separate from Solana's recent governance votes on SOL issuance and supply.
Source: CoinDesk
Trading involves risk.