- Status: Live on mainnet since September 15, 2026, at the start of epoch 1035, per the official Solana upgrades page
- Size limit: 4,096 bytes for v1 transactions, up from 1,232 bytes
- Works with: Jito-Solana validators and Agave RPC nodes on v4.2.2 or later (the v1 format shipped with the Agave 4.2 release line)
- Not changed: Legacy and v0 transactions keep the 1,232 byte limit
What changed
Two proposals are involved. SIMD-0296 defines the larger size, and SIMD-0385 defines the v1 format that delivers it. Solana Compass reported in July that the old limit forced zero-knowledge proof submissions, complex multisig approvals, and large batched instructions to be split across several transactions. A single larger transaction lets that work run atomically, meaning it either succeeds or fails as one unit. The official page doesn’t explain in detail why the old limit was so small. It says only that 1,232 bytes applied to legacy and v0 formats, and that v1 is the first format to exceed it.
V1 also changes how transactions are built:
- The first byte is 0x81, so infrastructure can identify v1 without full deserialization.
- Signatures move to the end of the transaction.
- Compute unit limit, loaded account data size, heap size, and priority fee sit in a fixed config section instead of ComputeBudget instructions.
- Priority fees are a total in lamports, not micro-lamports per compute unit.
- Duplicate account addresses are rejected.
The address lookup table tradeoff
V1 does not support address lookup tables. Accounts must be listed inline, up to a runtime limit of 64. Version 0 transactions can still use lookup tables, with the same 64 account ceiling. A draft proposal, SIMD-0596, would raise the v1 limit to 96 accounts, but it is not active. Teams that relied on lookup tables to fit many accounts into a small transaction should test whether v1 suits them. Because v0 remains available, nothing forces a switch.
Practical gotchas for tooling
The 4,096 byte limit applies only to v1. Base58 encoding stays capped at 1,232 bytes, so larger transactions must be sent as base64. Clients reading blocks or transactions must pass maxSupportedTransactionVersion: 1 to getTransaction and getBlock, or v1 transactions can cause errors. Indexers must read resource limits from the new config section, and fee caps that scan ComputeBudget instructions do not apply to v1. Unset resource limits default to zero in v1, so a transaction fails unless it sets them explicitly.
Who Benefits and How
App developers, wallets, indexers and RPC providers are the ones affected. Developers building proof submissions, multisig approvals or big batches can now do each in one transaction. Ordinary wallet users have no action to take, and any benefit reaches them only if the apps they use adopt v1. Adoption is not automatic: apps need the minimum library versions the official page lists, such as @solana/kit 8.0.0 and @solana/web3.js 3.0.2.
Open questions
- A bigger limit does not guarantee larger transactions in practice. How many apps will adopt v1 is unknown.
- No independent data on how much v1 traffic has appeared since activation was found.
- SIMD-0596, the draft that would raise the v1 account limit to 96, is not active.
Quick answers
Do wallet users need to do anything?
No action is described for ordinary users. The change matters to app developers, wallets, indexers, and RPC providers.
Do old transactions still work?
Yes. Legacy and v0 transactions remain valid and keep the 1,232 byte limit.
Which software versions are involved?
The Solana page says Jito-Solana validators and Agave RPC nodes should run v4.2.2 or later, and the v1 format shipped with the Agave 4.2 release line.
Sources
- Solana: Larger Transaction Sizes (v1 Transactions) upgrade page (accessed Oct 13, 2026)
- Solana Compass: Solana Agave v4.2 to Halve Slot Times, Cut Rent 90%, and Triple Transaction Size (Jul 28, 2026)
