Solana v1 Upgrade Bug Could Freeze Network Readers
A potential bug in Solana's upcoming v1 transaction format could freeze network readers and silently disable fee limits, according to an update on the Solana changelog published August 28. The upgrade, which promises more than three times as much room per transaction, has been live on testnet since then but still hasn't activated on mainnet.
RPC clients, indexers, relayers, and fee sponsors that aren't ready for v1 can fail in two ways: some systems will stop working while others will keep running with the wrong resource limits. This is because v1 transactions have a higher maximum payload of 4,096 bytes compared to legacy and v0 transactions.
To avoid these issues, RPC consumers must pass the integer maxSupportedTransactionVersion: 1 when using getTransaction, getBlock or blockSubscribe. Without this opt-in, a v1 getTransaction request will return an error, and other failures can be quieter, affecting indexers that scan ComputeBudget instructions or Geyser and gRPC consumers who may label v1 as v0.