Solana v1 Upgrade Exposes Hidden Bugs
Solana's upcoming upgrade, v1, promises to increase transaction space by over three times. However, this change has exposed several bugs that could potentially freeze network readers and disable fee limits silently.
The Solana team has listed v1 as not activated on the mainnet as of September 4, but testnet is active with devnet live in epoch 1140. A pre-activation window was given to infrastructure operators to update their systems before the upgrade went live.
RPC clients and indexers can fail silently if they don't opt-in for v1 transactions by passing maxSupportedTransactionVersion: 1 when using getTransaction, getBlock or blockSubscribe. Without this, a v1 getTransaction request returns an error -32015, while a single v1 transaction makes the entire block fail for getBlock.
The upgrade has also changed how compute-unit limits and loaded-account data limits are handled in transactions. If these systems don't update to handle v1 transactions correctly, they may report a zero compute budget or empty budgets.