Solana has activated Transaction V1 on its mainnet, increasing the maximum transaction size from 1,232 bytes to 4,096 bytes — a more than threefold expansion. The upgrade, which went live at the start of epoch 1,035 on September 15, 2026, around 01:20 UTC, gives developers significantly more space to include instructions, signatures, and other data within a single transaction.
This change does not increase Solana’s transactions per second; instead, it expands the amount of information each transaction can carry. The Solana Foundation says the larger format can support workloads such as zero-knowledge proofs, large multisignature setups, and on-chain signature schemes that were previously difficult to fit under the old 1,232-byte limit.
Solana Raises Transaction Size Limit to 4,096 Bytes
Solana’s previous byte ceiling originated from early network design choices tied to packet-size limits. This restriction persisted even after the network transitioned to QUIC for transaction traffic. With the new V1 format, transactions now reach up to 4,096 bytes — about 3.3 times the previous maximum.
The larger space reduces the need to split complex actions across multiple transactions. Developers can place more instructions and signatures inside one atomic transaction. For example, the extra room supports company wallets requiring several approvals, privacy tools using large cryptographic proofs, and DeFi operations that need multiple steps to either succeed or fail together.
Transaction V1 Targets Multisig, ZK Proofs, and Complex DeFi
Before the upgrade, developers often worked around the size limit by using several transactions or other methods to fit larger operations on-chain. Solana’s SIMD-0296 proposal noted that the old cap restricted use cases with large proof sizes and multiple signatures. The proposal set the new maximum at 4,096 bytes, while SIMD-0385 introduced the V1 transaction format.
Solana continues to support Legacy and V0 transactions, so applications do not have to switch immediately. However, developers who want the larger transaction capacity must use V1. Infrastructure services — including RPC providers, indexers, wallets, explorers, and analytics tools — need to update their systems to recognize and process V1 transactions correctly.
Solana Narrows One Transaction Gap with Ethereum
The upgrade narrows a technical gap between Solana and Ethereum. Solana previously imposed a fixed 1,232-byte transaction limit, while Ethereum does not use a fixed byte ceiling. Instead, Ethereum controls transaction execution and data through gas rules, and following EIP-7825, it enforces a protocol-level per-transaction gas cap of 16,777,216 gas.
As a result, the two networks still use different approaches. Solana now allows much larger transaction payloads than before but keeps a fixed 4,096-byte cap for V1 transactions. Ethereum can support larger data-heavy operations when they remain within gas rules and the transaction gas cap. Therefore, the Solana change gives developers more room than they had before but does not remove every structural difference between the networks.
Meanwhile, Solana has continued changing other network parameters. In August, the network reduced slot time from 400 milliseconds to 350 milliseconds, with plans for a further reduction to 200 milliseconds. Transaction V1 remains separate from those speed changes because it focuses on how much data developers can place inside a single transaction rather than how quickly the network produces slots.
Also Read: How Does Real-World Asset Tokenization Work on Solana?
Leave a Reply