Solana Triples Transaction Capacity With Optional Transaction v1

Overview

• Solana is raising the maximum serialized transaction size from 1,232 bytes to 4,096 bytes, with a targeted mainnet activation set for Wednesday that remains tentative on the official roadmap.
• Transaction v1 is optional so legacy and v0 formats will continue to work, but developers must opt in to use the larger envelope.
• The v1 format removes Address Lookup Tables and places full 32‑byte account addresses and resource limits inside transaction metadata, which can increase byte use for ALT‑heavy apps while keeping the 64‑account reference limit unchanged.
• RPC providers, indexers, explorers and wallets must update code to recognize version 1 and to read resource limits from the new metadata or they risk request failures and incorrect fee or limit displays.
• The larger envelope aims to let developers fit zero‑knowledge proofs, large multisig and batched atomic operations into one transaction, but teams should test end‑to‑end on testnet and devnet and set compute‑unit and loaded‑data limits explicitly because those defaults are zero and bigger transactions may raise network bandwidth and priority‑fee pressure.