Solana Transaction v1 Heads to Testnet With 3.3x Larger Capacity
Solana’s planned Transaction v1 upgrade will raise the maximum transaction size from 1,232 bytes to 4,096 bytes, making complex operations easier to execute atomically while requiring infrastructure providers to update their tooling.
Solana is preparing to launch Transaction v1 on testnet in the coming weeks, increasing the network’s maximum transaction size by roughly 3.3x. The upgrade is designed to accommodate larger and more sophisticated operations without forcing developers to split them across multiple transactions.
A Larger Transaction Envelope
Defined through SIMD-0296 and SIMD-0385, Transaction v1 introduces a new version byte, 0x81, and places compute and priority-fee settings into a fixed header mask. Embedding these resource configurations directly into the transaction header is intended to streamline validator processing and create a more standardized transaction structure.
The format expands the maximum payload from 1,232 bytes to 4,096 bytes. That additional capacity could allow several previously difficult operations to execute atomically, including:
- Zero-knowledge proofs, which can exceed the legacy transaction limit.
- Large multisignature transactions involving numerous signers.
- BLS signature schemes and other cryptographic operations with larger payloads.
- Complex DeFi actions that previously required multiple linked transactions or workarounds.
The existing v0 format will continue to function, so developers are not being forced into an immediate migration.
Address Lookup Tables and Developer Readiness
Transaction v1 removes Address Lookup Tables (ALTs) from the new format. ALTs were introduced to compress account references and fit more accounts into Solana’s smaller legacy transactions, but the expanded limit reduces the need for that mechanism in many cases.
Mid-August analysis cited in the research found that approximately 62% of sampled v0 transactions used ALTs. However, most of those transactions reportedly fit within the new 4,096-byte ceiling after conversion to v1, with a median buffer of about 420 bytes remaining.
Local testing is already available through solana-test-validator 4.2 and later, as well as tools such as Surfpool. Preliminary feature-gated improvements for mainnet began on Aug. 17, 2026, as part of the Agave 4.2 client release cycle, although testnet activation remains the next major milestone.
Infrastructure providers will need to support the new serialization format. Indexers, RPC services, block explorers, analytics platforms and other systems that parse raw transactions must update their transaction handling before wider deployment.
What This Means
Transaction v1 removes a growing constraint for Solana applications as proofs, multisig workflows and complex on-chain interactions become more demanding. The larger payload does not solve every scaling challenge, but it could reduce transaction fragmentation and simplify application design while preserving the current v0 pathway.
The key test will be the transition from testnet to mainnet. If validators and infrastructure services handle the new format without major issues, Solana will have demonstrated that it can expand transaction capability while maintaining compatibility and network performance.