Market desk Bitcoin Ethereum Altcoins DeFi Stablecoins Markets & Trading

Solana Triples Transaction Capacity with V1 Upgrade

Solana activated Transaction V1 on mainnet, increasing the maximum transaction size from 1,232 bytes to 4,096 bytes and enabling more complex operations within single atomic transactions.
1 hour ago 5 views
Solana Triples Transaction Capacity with V1 Upgrade

Solana implemented Transaction V1 on its mainnet on Tuesday, September 15, enabling developers to include more data in each transaction. The upgrade increases the maximum size of serialized transactions to 4,096 bytes from 1,232 bytes, providing approximately 3.3 times more space for transaction data.

The feature gate was activated at the beginning of epoch 1035 at approximately 01:00 UTC and is now live on mainnet, testnet, and devnet. The new transaction format was defined in SIMD-0296, while the V1 Message Format is based on SIMD-0385.

Atomicity and Complex Operations

Previously, developers facing transaction size limitations could split operations into multiple transactions or use Jito bundles. However, bundles do not provide atomicity at the protocol level. With V1, developers can include more instructions and data within a single transaction, ensuring that routing, proof checking, and batching either all execute or all fail together. In some cases, this reduces the number of signatures and confirmations required to complete an operation.

The increased capacity will benefit applications involving zero-knowledge proofs, large multisig operations, and BLS signatures.

Design Trade-offs

Transaction V1 removes Address Lookup Tables in favor of inline account references. While this simplification reduces complexity, it increases transaction size. Analysis of v0 transactions showed that 62 percent used at least one Address Lookup Table; transactions using multiple lookup tables could increase in size by more than 1,500 bytes under the new format. The 64-account limit remains unchanged.

V1 also relocates compute limits and priority fee settings from ComputeBudget instructions to transaction settings, giving infrastructure providers easier access to these parameters.

Implementation Requirements

RPC operators must set maxSupportedTransactionVersion: 1 for getTransaction and getBlock functions. Indexers need to read V1 compute limits and priority fees from transactionConfig. Validators and RPC operators should run Agave v4.2.2 or later. Wallet providers should advertise V1 support only after confirming their software can correctly parse and sign the new transaction format.

Broader Context

The upgrade comes as Solana expands its position in on-chain finance. According to DeFiLlama, total value locked in Solana's DeFi sector is approximately $5.95 billion, with 24-hour decentralized exchange volume around $1.79 billion. Real-world assets on the network have exceeded $4 billion across more than 350,000 addresses.

V1 broadens the range of applications developers can build on Solana, though expanded transaction capacity alone does not guarantee increased adoption or user activity.

Market snapshot

Top cryptocurrency prices

Explore all prices
Market prices will appear after the next scheduled refresh.