Solana raised the maximum size of a single transaction to 4,096 bytes from 1,232, a 3.3x increase that went live on the network’s main chain early Tuesday at the start of epoch 1035, around 01:00 UTC.

The change arrives through a new v1 transaction format, set out in two Solana Improvement Documents: SIMD-0296 raises the size limit, and SIMD-0385 defines the format. It is live on mainnet, testnet and devnet.

The old 1,232-byte ceiling forced developers to break larger operations into several chained transactions. The Solana Foundation says the extra room lets that work fit into a single transaction, including the zero-knowledge proofs used in confidential transfers, large multisigs, batched operations, and newer signature schemes such as Winternitz one-time signatures and BLS.

What Developers Have to Do

Older v0 and legacy transactions keep working, so wallets and apps that do not need the extra space are unaffected. Anything that wants the larger size has to adopt v1, and anything that reads Solana data has to recognize the new format before it can parse those transactions. Validators running Jito-Solana and RPC nodes running Agave are told to move to version 4.2.2 or later, because earlier releases downgrade a v1 transaction back to v0.

The 4,096-byte figure is not arbitrary. It matches the standard 4 KiB memory page used by validator hardware, and it caps how costly a single transaction can be to move, since anything larger than the network’s packet size has to be split across multiple data frames that are more expensive to relay reliably.

One of a Run of Changes

The increase continues a steady cadence of protocol upgrades. Solana has been stepping its slot time down from 400 milliseconds toward a 200-millisecond target, reaching 300 so far, while its tokenomics have been under debate since the spring.

Related Listen: Should Stock Tokens Be Limited to KYC’d Users? Or Be Tradeable by Anyone?