Key points

  • Solana's Transaction V1 feature activated on mainnet at about 01:00 UTC on September 15, increasing the maximum size from 1,232 to 4,096 bytes.
  • Legacy and v0 transactions remain valid, but applications must opt into v1 to use the larger envelope.
  • Wallets, indexers, RPC providers and fee sponsors may need software changes because v1 removes address lookup tables and moves resource limits into the message.

Solana has activated its Transaction V1 format on mainnet, lifting the network's maximum transaction size from 1,232 bytes to 4,096 bytes. The Solana Foundation says the feature gate became active at the start of epoch 1035 on September 15 at approximately 01:00 UTC, turning a previously planned protocol change into a live network capability.

The increase gives developers about 3.3 times as much space inside one transaction. Solana identifies zero-knowledge proofs, large multisignature arrangements and on-chain signature schemes as examples of workloads that can benefit. CoinDesk reported the activation on September 15, highlighting the additional room for multi-step trades, corporate wallet approvals and privacy-related proofs.

Related reporting: DeFi Development Corp adds 55,491 SOL and opens $300M CHAD program

A larger envelope with a new format

Transaction V1 does more than raise a byte limit. Its specification moves priority fees and resource requests into fixed-position configuration fields, allowing validators to find that information without scanning Compute Budget instructions. It also separates instruction headers from their payloads and places referenced account addresses directly in the transaction.

That design removes Address Lookup Tables from v1. Under the existing v0 format, a transaction can reference accounts through compact lookup-table indexes instead of including every 32-byte public key. V1 writes addresses inline, so part of the new capacity can be consumed by account data that v0 compressed. Solana's own analysis says the practical headroom will vary by workload rather than producing the same gain for every application.

Existing transactions keep working

The activation is backward-compatible at the protocol level: legacy and v0 transactions remain valid, and applications that do not need the larger size can continue using them. Developers must deliberately build and submit v1 transactions to gain the extra capacity. The format still caps referenced accounts at 64 and top-level instructions at 64, so the higher byte ceiling does not remove every constraint on complex operations.

The transition can nevertheless be breaking for software that reads or sponsors transactions. Solana says clients reading blocks or transactions must declare support for version 1. Indexers must obtain resource limits from the new transaction configuration, while fee sponsors and co-signing services can no longer rely on caps derived only from Compute Budget instructions. Applications sending v1 transactions must explicitly set compute-unit and data-size limits because their defaults are zero.

Why the activation matters

For developers, a larger atomic transaction can reduce the need to split one intended operation into several steps or use off-protocol bundles. That may simplify some proof-heavy, multisignature and routing designs, but it does not guarantee cheaper execution or higher throughput. Larger messages still consume bandwidth, and the original improvement proposal identified testing, scheduling and priority-fee treatment as operational considerations.

The immediate effect will depend on adoption by wallets, software libraries, RPC providers and applications. Solana lists minimum supporting releases for its main JavaScript libraries and warns older readers may fail when they encounter v1 data. Operators therefore need to distinguish protocol activation from end-user availability: a live format may remain unusable in a particular wallet, exchange or analytics service until that provider upgrades its transaction parser. The mainnet gate is active, but the upgrade's economic and performance impact will only become measurable as developers begin using the format in production.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.