Solana v1 upgrade bug can freeze network readers and disable fee limits

Solana's v1 transaction format offers over three times the capacity per transaction, but unprepared RPC clients, indexers, relayers, and fee sponsors may experience failures. Some systems may stop functioning, while others may operate with incorrect resource limits. As of Sept. 4, v1 is not activated on the mainnet, though testnet is active and devnet is live in epoch 1140. A changelog from Aug. 28 indicated that v1 transactions were 'coming soon,' allowing infrastructure operators time to update. V1 increases the maximum payload from 1232 bytes to 4096 bytes. Legacy and v0 transactions retain their limits, so users can continue using those formats without migration. RPC consumers must use the integer maxSupportedTransactionVersion: 1 for getTransaction, getBlock, or blockSubscribe. Without this, a v1 getTransaction request results in error -32015, and a v1 transaction can cause getBlock to fail for the entire block. Other failures are less obvious, as v1 moves compute-unit limits and priority fees into a transactionConfig object, which may lead to zero compute budgets being reported for v1 transactions without errors. Geyser and gRPC consumers may mislabel v1 as v0, preserving an empty budget. Relayers and paymasters must adjust their policy checks since fee caps based on ComputeBudget instructions may not apply in v1. Onchain programs face a challenge as no current sysvar or syscall exposes the v1 message configuration, requiring a shift away from relying on ComputeBudget instructions.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.