Solana Activates 4,096-Byte Transactions with New v1 Format in Epoch 1,035

Solana flipped a major switch on September 15. The network activated its new v1 transaction format at the start of epoch 1,035, pushing the maximum transaction size from 1,232 bytes all the way to 4,096 bytes — a more than threefold jump that’s been in the works for a while.

For most people sending SOL wallet-to-wallet, it’s probably not going to feel like anything changed. But for developers building on the network, it’s a pretty big deal. The old 1,232-byte ceiling had been baked into Solana since its earliest days, tied to the 1,280-byte limit of standard network packets. That constraint forced complex operations — things like zero-knowledge proofs or multisignature setups — to get split across multiple transactions, which meant more signatures, more coordination, more chances for something to go sideways. Now those same operations can fit inside a single transaction.

What Changed at Epoch 1,035

The shift was made possible partly by Solana’s move to the QUIC protocol, which broke the old packet-size dependency. And the 4,096-byte ceiling wasn’t picked randomly — it matches the standard memory page size used by validator hardware, which keeps things tidy on the infrastructure side.

Legacy transaction formats aren’t going anywhere. Existing wallets stay compatible. But developers who want to actually use the extra space need to adopt the v1 format. It’s not automatic. And the new format comes with its own constraints: capped at 12 signatures, 64 accounts, and 64 instructions per transaction. So it’s more room, but not unlimited room.

The Token-2022 update is probably the clearest example of why this matters. That upgrade compresses a set of complex operations into a single atomic transaction — one that previously blew past the old byte limit entirely. With the 4,096-byte cap now live, that kind of bundling becomes workable. Either the whole thing succeeds or the whole thing fails. No partial states, no messy rollback situations.

Not a small thing for developers who’ve been working around the old limit for years.

Speed Goals and Record Transaction Volumes

The byte limit isn’t the only thing Solana’s been tweaking. Block creation time is currently being cut from 400 milliseconds down to 350 milliseconds, with further reductions planned. The target, eventually, is 200 milliseconds. That’s fast. Whether the network gets there on schedule is unclear, but the direction is consistent.

Related: AI Leaders Urge Pause as $1 Trillion Race Ignites Safety Concerns

And the network is clearly being used. Solana logged a record 4.2 billion transactions in July. That’s not a small number. It kind of puts the infrastructure pressure in context — when you’re moving that kind of volume, even modest changes to transaction structure ripple through the whole system.

Larger transactions do mean more bandwidth and more storage per transaction. The v1 format doesn’t triple the transaction count, it just gives each transaction more capacity. That’s a meaningful distinction. But it still puts pressure on every service that touches Solana’s data layer.

Infrastructure Has to Keep Up

RPCs, indexers, block explorers — all of them need to update their systems to properly decode v1 transactions. If they don’t, they’ll misread the data or choke on it entirely. That’s not a theoretical risk. It’s the kind of thing that’s caused headaches on other chains when protocol changes outpaced tooling updates.

Solana’s core team seems aware of it. The upgrade was rolled out at epoch 1,035 with the expectation that infrastructure providers would be ready or close to it. But “ready” is a spectrum in blockchain development. Some services will adapt fast, some won’t. Users relying on third-party tools might hit rough patches while the ecosystem catches up.

Read also: CLARITY Act Hits Senate Wall as 18 State AGs Demand Rejection

And there’s a broader point here. Blockchain networks don’t upgrade in a vacuum. Every protocol change creates a wave of downstream work — wallet teams, explorer teams, RPC providers, application developers. The bigger the change, the bigger the wave. Going from 1,232 to 4,096 bytes is a significant jump, and the ecosystem needs time to absorb it.

For now, the new format is live. Developers can start building with it. The old format still works. And Solana’s transaction record from July — 4.2 billion — sits as a kind of benchmark the network will be measured against as the v1 format gets adopted and the block time reductions continue to roll out.

The 1,232-byte limit that held since Solana’s launch no longer applies as of September 15.