Hidden Solana upgrade bug can freeze network readers and silently disable fee limits

Solana’s v1 transaction format promises more than three times as much room per transaction, but RPC clients, indexers, relayers and fee sponsors that are not ready for it can fail in two very different ways: some systems stop, while others keep running with the wrong resource limits.Solana’s live upgrade page still lists v1 as not activated on mainnet as of Sept. 4. Testnet is active and devnet is live in epoch 1140. A Solana changelog published Aug. 28 said v1 transactions were “coming soon,” leaving infrastructure operators a pre-activation window to update.V1 raises the maximum payload from 1,232 bytes to 4,096 bytes, about a 3.3-fold increase. Legacy and v0 transactions keep their existing limits and behavior, so users and applications that continue using those formats do not need to migrate.RPC consumers must pass the integer maxSupportedTransactionVersion: 1 when using getTransaction, getBlock or blockSubscribe. Without that opt-in, a v1 getTransaction request returns error -32015, one v1 transaction makes getBlock fail for the entire block, and blockSubscribe emits block: null and stops advancing at the first affected slot.The parameter only tells the RPC service the highest...