Solana readies Transaction v1 to triple data capacity

The increase provides roughly 3.3 times more space, enabling the integration of zero-knowledge proofs, large multisignature schemes, and batched operations that previously required fragmentation. By combining these steps into a single transaction, developers can ensure that either every instruction succeeds or the entire process rolls back, reducing the risk of partial failures. While the capacity grows, the network’s limit of 64 referenced accounts per transaction remains unchanged.

Infrastructure providers, including indexers and block explorers, face the most immediate technical hurdle. Unlike legacy or v0 formats, v1 stores compute limits and priority-fee settings directly within the transaction configuration rather than in ComputeBudget instructions. Services that fail to update their software to recognize this new structure risk misreporting fees or failing to process blocks entirely. Furthermore, applications adopting v1 must explicitly set compute-unit and loaded-data limits, as these default to zero under the new schema.

According to Solana Foundation Vice President of Technology Jacob Creech, the v1 format is optional. Users are not required to migrate tokens or adjust their wallets, as legacy and v0 formats will continue to function alongside the new standard. While testnet and devnet environments have already integrated the feature, the mainnet launch remains subject to final confirmation, as the official roadmap currently classifies the activation as pending.