Overview
- The Solana network activated the V1 transaction format on Tuesday, Sept. 15, increasing the maximum serialized transaction size from 1,232 bytes to 4,096 bytes while remaining opt-in and backward compatible.
- V1 moves account addresses and compute/fee limits into transaction metadata, supports up to 64 direct accounts, and lets developers pack complex actions such as zero‑knowledge proofs and large multisignature approvals into a single atomic transaction.
- Services that do not recognize V1 metadata can see request failures, misreported fees or incorrect compute limits, so wallets, RPC providers, indexers and validators must update parsing, fee handling and scheduling code to avoid errors.
- Network activity and on‑chain revenue are at record levels — Solana reported 5.2 billion non‑vote transactions in August and rising Q3 revenue — which raises immediate questions about validator bandwidth, priority‑fee pressure and real developer adoption.
- The protocol’s slot‑time roadmap is also moving forward, with the 250ms slot stage reported in final activation steps and expected to take effect around Sept. 18, and a final 200ms target remaining on the roadmap.