The Solana Foundation reports that the network’s maximum transaction size rose from 1,232 bytes to 4,096 bytes, more than tripling the data capacity of a single transaction. The change took effect on mainnet Tuesday at the beginning of epoch 1,035, around 1:00 am UTC, per the blockchain data provided.
The change gives developers room to fit more complex operations into a single package, including zero-knowledge proofs and transactions carrying multiple signatures. A spokesperson for the Solana Foundation told Cointelegraph the upgrade is aimed at letting developers “do more” with applications like zero-knowledge proofs and new onchain signature schemes, by freeing up workloads that previously could not fit inside a single transaction.
The Numbers Behind the Upgrade
A jump from 1,232 bytes to 4,096 bytes marks a notable rise in storage space. Here is how it breaks down:
- The old limit was 1,232 bytes.
- The new limit is 4,096 bytes.
- That is more than three times the previous space.
The update included the v1 transaction format, a design that preserves full backward compatibility with older transactions. That means existing formats continue to work for applications and wallet providers, though protocols hoping to benefit from the increased size must move to v1 transactions themselves.
What the Upgrade Actually Changes
A larger size gives developers room to put more complicated operations inside a single Solana transaction. The main benefits include:
- Zero-knowledge proofs
- Transactions requiring multiple signatures
- New onchain signature schemes
These were operations that used to run up against the 1,232-byte ceiling. Now that the limit has risen, developers can put them all into one package instead of spreading them across separate transactions.
How the Upgrade Went Live
Tuesday marked the launch of the upgrade on mainnet at the beginning of epoch 1,035, roughly 1:00 am UTC, per blockchain data provided by the Solana Foundation. The upgrade brought the v1 transaction format, which preserves full backward compatibility with older transactions. While existing transaction formats keep functioning for applications and wallet providers, protocols wishing to gain the size increase must switch to v1 transactions.
Related Moves From Solana
Solana has been making other moves alongside the transaction size upgrade. In August, the network reduced its slot time from 400 milliseconds to 350 milliseconds. In June, the Solana Foundation shared plans to reduce slot times from 400 milliseconds to 200 milliseconds, arguing that it would improve latency and accelerate confirmations on the blockchain network.
The reasoning given for reducing slot times is to cut down latency and speed up confirmations. Whether these changes actually take hold is still unclear.
Validator Approval on Aug. 28
On Aug. 28, Solana validators approved a proposal to double the network’s annual disinflation rate, reducing future issuance of Solana (SOL), the network’s native token.
The approval arrives alongside the transaction size increase and the continuing slot-time cuts. Combined, these developments mark a period of significant activity for the network’s underlying framework.
What Developers Need to Know
The upgrade alters how transactions work on Solana, and it does so in a way that matters for people actually writing code against the platform. Because the v1 transaction format maintains backward compatibility, existing applications will keep running without interruption when the upgrade takes effect.
To make use of the expanded size limits, developers must switch their code to v1 transactions. That change also clears room for new transaction types that were once too large to include.
The Case for the Upgrade
Solana’s upgrade sends a clear message about its ambitions. It gives transactions more room, which lets developers build more elaborate applications without splitting their code into separate packages.
Designing the upgrade so it preserves support for older versions was a deliberate decision, and it pays off by letting the transition take place without disturbing any systems already in use. That matters greatly when a live network depends on those systems to keep running.
The increase gives Solana the capacity to handle more complex cryptographic functions within a single transaction. Zero-knowledge proofs stand out as a strong method for protecting privacy during computation, and the expanded size allowance now removes the restriction that had constrained their deployment before.
Looking Ahead
Solana’s transition from 400 milliseconds to 350 milliseconds and then to 200 milliseconds is ongoing. The outcome of those plans is not yet known, but the path is obvious: the network is heading for quicker transactions.
The Aug. 28 proposal approved by validators to combat inflation will gradually change how the token economy works. It reduces the number of new SOL tokens entering circulation.
The combined moves on transaction capacity, reduced slot times, and the price-stability plan show a system that keeps changing how it works at its foundation. The cap on what a single message can hold has grown to more than three times its earlier level, and the v1 design offers a plain route ahead for builders.
The update became active Tuesday at the beginning of epoch 1,035, roughly 1:00 am UTC. The key message for developers is straightforward: review how your transactions are constructed, move to v1 if you need more room, and benefit from the expanded capacity now on offer for your code.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.