Solana activated its Transaction v1 format on mainnet Tuesday, raising the maximum transaction size from 1,232 bytes to 4,096 bytes and removing a bottleneck that has forced developers to split complex operations across multiple transactions for years. The change went live at the start of epoch 1035, according to the Solana Foundation, after weeks of testing on the network’s testnet and devnet environments.
The upgrade, defined in two protocol proposals known as SIMD-0296 and SIMD-0385, gives developers roughly 3.3 times more room in a single operation. Workloads that previously could not fit inside one transaction now can, including zero-knowledge proofs, large multisignature approvals used by institutions, nested multisigs, Winternitz one-time signatures and BLS signature schemes.
Why the old limit existed
Solana’s 1,232-byte ceiling dates back to the network’s original design. While the chain has always been faster and cheaper than Ethereum, it lagged in one structural area: Ethereum has no rigid protocol-level size limit, so developers can pack massive, data-dense operations into a single transaction simply by paying higher fees. Solana developers had to build custom compression schemes or break work into chunks, adding complexity and failure points to every multi-step workflow.
The network changed how it transmits transaction traffic back in 2022, which made the old ceiling less necessary from a bandwidth standpoint. But the limit stayed on the books because raising it required a coordinated protocol change rather than a client update. That change arrived through SIMD-0296, which handles the size increase itself, and SIMD-0385, which defines the new v1 message format.
The new ceiling stops at 4,096 bytes for a practical reason. Four kilobytes is a standard memory-page size on the validator hardware that runs the network. Letting transactions grow much larger could force a single operation to span several pages, raising processing costs for the machines that keep the chain running. The Foundation said no new per-byte fee has been introduced, though larger transactions may require higher priority fees during congestion, since they occupy more of each block’s limited space.
What changes for developers
The v1 format uses a new message structure with a 0x81 version byte and a configuration mask. Existing transaction formats continue to work, so wallets and applications do not need to switch unless they want the extra space. Older clients can keep submitting legacy transactions indefinitely, which softens the migration.
The heavy lifting falls on infrastructure instead. RPC providers, block explorers, indexers and analytics platforms must learn to parse v1 transactions, or requests can fail when they encounter the new format. The Foundation also changed where some software should look for priority-fee information, directing indexers to decode v1 configuration rather than ComputeBudget instructions. Developers have had local testing tools since August 24, when support landed in Solana CLI v4.2 and Surfpool v1.5, and the testnet activation that followed gave roughly two weeks of runway before the mainnet switch.
What it unlocks
Single-transaction zero-knowledge proofs are the headline use case. Privacy protocols on Solana previously had to truncate or batch their proofs, which limited what they could verify on-chain. With 4,096 bytes, a full proof fits without workarounds. Confidential transfers, which hide amounts while still allowing validators to check that no value was created out of thin air, become practical in the base format rather than requiring external systems.
Institutional workflows benefit too. A corporate treasury wallet that requires five approvals can now bundle the whole approval chain into one operation instead of sequencing several. Marketplaces can link a buyer’s payment, the seller’s asset transfer and a platform fee as dependent steps that either all succeed or all fail, eliminating partially completed trades that leave funds stranded mid-transaction.
Payment companies have been watching the space closely. MoneyGram, which launched its own MGUSD stablecoin on Stellar in June and added Solana ramps in August, is one of several remittance firms building multi-chain flows where a single failed step can strand customer funds. Atomic multi-step transactions reduce that class of failure directly.
Positioning against Ethereum
The timing matters for the competition between the two chains. DeFiLlama data published in SwapSpace’s 2026 report showed Ethereum’s share of global DEX volume falling to 19.3 percent in 2025 from 46.2 percent in 2021, as Solana and BNB Chain absorbed trading activity. Larger transaction capacity strengthens Solana’s argument for hosting complex applications, from privacy tooling to custody workflows that require many signatures at once.
Ethereum developers, meanwhile, are working through their own roadmap, with the Glamsterdam upgrade in development, which targets higher gas limits and parallel processing. The two networks are converging on the same problem from opposite directions: Solana loosening a hard cap, Ethereum trying to lift throughput without giving up decentralization guarantees. Neither chain can claim a permanent edge, since both are iterating faster than users can evaluate the differences.
SOL traded near $102 on Tuesday, roughly flat on the day, as the upgrade drew little immediate price reaction. Market attention this week has centered on the Federal Reserve’s September meeting and the Senate’s procedural vote on the CLARITY Act rather than protocol changes. Bitcoin’s move from below $77,000 to above $81,000 after Fed Governor Christopher Waller backed holding rates has dominated the tape.
For ordinary users, nothing changes today. The upgrade matters most for the applications built on top: privacy protocols that need room for proofs, exchanges settling multi-step trades atomically, and companies running wallets with long approval chains. Those teams can now do in one transaction what previously took three, and the failure modes that came with splitting operations disappear with them.