Solana’s Transaction V1 Is Live, Raising Transaction Capacity 3.3x
•
September 15, 2026 7:12 am
•
Comments
Solana has switched on Transaction V1, a network upgrade that gives developers more than three times as much room inside a single transaction.
The Solana Foundation says the feature activated on mainnet at the start of epoch 1035 on September 15. The maximum transaction size is now 4,096 bytes, up from 1,232 bytes.
That sounds like a narrow engineering change. In practice, it opens the door to operations that previously had to be split into several steps, including zero-knowledge proofs, large multisignature approvals, batched instructions and some confidential transfers.
Legacy and version-zero transactions remain supported, while senders that need the added space can opt into version 1. The Foundation also warns transaction readers, block indexers and fee sponsors to update their software because the new format changes where some limits and fee data are stored.
You can now make larger transactions on Solana
ZK, more complex routing, and more is now possible
The design space just got bigger for all apps on Solana pic.twitter.com/PScNKzuMDH
— Jacob Creech (@jacobvcreech) September 15, 2026
The practical advantage is atomic execution. A developer can fit more related instructions into one transaction, so the whole operation either succeeds or fails together.
That is cleaner than chaining several transactions and accepting the risk that only part of the sequence lands.
CoinDesk notes that the expanded format gives Solana more room for company-wallet approvals and privacy applications. It also makes an important distinction: this upgrade increases how much data one transaction can carry; it does not directly increase transactions per second.
The change is opt-in for senders. Ordinary users do not need to change how they sign or submit transactions.
Developers who want the extra space must build and send the new format.
— Anza (@anza_xyz) September 15, 2026
Infrastructure operators have more immediate work to do. Applications that read transactions or whole blocks must declare support for version 1.
Indexers also need to read compute limits and priority-fee information from the new transaction configuration instead of relying on the older instruction layout.
The design comes from SIMD-0296 and SIMD-0385. The 4,096-byte ceiling was chosen to match a standard four-kilobyte memory page while giving complex applications meaningfully more room.
For Solana, the real win is not a flashy speed claim. It is a larger design envelope.
Developers can now place more cryptographic work and more coordinated actions inside one network-guaranteed transaction, while existing formats remain available for simpler jobs.
Join the conversation!
We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.