Solana Triples Transaction Capacity as 4,096-Byte Upgrade Goes Live
• September 16, 2026 3:07 pm • CommentsSolana has switched on a long-awaited upgrade that gives developers far more room inside a single transaction.
The network’s new v1 transaction format is now live on mainnet, raising the maximum transaction size from 1,232 bytes to 4,096 bytes. That is a roughly 3.3-fold increase, and it removes a practical constraint that has shaped how Solana applications package complex operations.
According to the Solana Foundation’s technical overview, the txv1 feature activated at the start of epoch 1035 on September 15. The upgrade is also active on testnet and devnet.
Why 4,096 bytes matters
The extra space is about what can fit inside one transaction, not a direct increase in transaction count. One transaction can carry more instructions, signatures and proof data while remaining atomic—either the whole operation succeeds or none of it does.
Solana says the added capacity can help accommodate zero-knowledge proofs, larger multisignature operations, onchain signature schemes and batched work that previously had to be split across several steps. That can reduce the cost and coordination risk involved in chaining multiple transactions together.
The change is delivered through the v1 transaction format defined in SIMD-0385, while the larger size limit comes from SIMD-0296. Developers have to opt into v1 to use the added room.
250ms slots activation now pending on mainnet-beta.
400 → 350 → 300 → 250ms
Reminder, SIMD-0525 features take effect one epoch after they activate thus will go live at the epoch 1037 boundary ~05:01 UTC, Friday Sept 18.
– epoch 1035: pending activation
– epoch 1036: feature…— Anza (@anza_xyz) September 16, 2026
The upgrade is optional, but readers must be ready
Existing legacy and v0 transactions continue to work. Wallets and applications that do not need larger payloads are not being forced into a new format.
There is still important work for infrastructure providers. Software that reads or indexes transactions needs to recognize version 1, and fee sponsors or co-signers must read the relevant limits from the new transaction configuration instead of relying on older compute-budget instructions.
CryptoSlate’s account of the activation places the larger transaction format within a broader push to increase Solana’s useful capacity. The important distinction is that transaction size, block capacity and slot time are separate levers: changing one does not automatically deliver the benefits of the others.
The v1 format addresses what a single atomic operation can contain, while Anza’s current slot-time work targets how quickly the network advances from one block-production window to the next. That makes the 4,096-byte activation one part of an active engineering sequence rather than a stand-alone promise that every application becomes faster overnight.
Developers also have implementation work to do before users feel the difference. Applications must adopt v1 when they need it, indexers have to recognize the new version, and fee sponsors must read limits from the new transaction configuration so their existing safeguards continue to function as intended.
JUST IN: Solana daily stablecoin active addresses hit 888K in September, up 269% from 333K a year ago. pic.twitter.com/Z30vbVWbfg
— Solana (@solana) September 15, 2026
A capacity upgrade meeting real demand
The timing is notable because Solana is not expanding into an empty network. The project’s official account reported 888,000 daily active stablecoin addresses in September, up from 333,000 a year earlier.
That figure is a network-supplied metric, but it helps explain why application developers are pressing for fewer artificial limits on complex transactions.
The immediate effect will depend on adoption. Users will not wake up to a different wallet experience solely because the feature gate activated, and applications still have to implement the new format correctly.
The network has nevertheless removed a hard ceiling that forced developers to work around packet-size constraints dating back to Solana’s original design.
For builders, the real test begins now: whether the larger format turns into simpler application flows, lower coordination overhead and new products that could not fit cleanly into one transaction before.
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.
