KOSUNI CRYPTO
Korea's Crypto Pulse, in English
$BTC $ETH $XRP $SOL $DOGE
News
Neutral

Solana v1 Transaction Format Transition Approaching Compatibility Checks

Published September 25, 2026 7:49 PM · 9 views $SOL
Solana v1 Transaction Format Transition Approaching Compatibility Checks

Solana (SOL) is undergoing infrastructure compatibility checks ahead of activating its new v1 transaction format on the mainnet. The upgrade increases single transaction size from 1,232 bytes to 4,096 bytes but focuses on ensuring RPC, indexers, gRPC, and fee sponsors properly handle the new format rather than chain consensus issues.

The Solana Foundation announced Agave 4.2 has gone live on mainnet with 'Larger Transaction Sizes' functionality pending activation until September 4, 2026. The feature expands existing transaction limits by approximately 3.3 times through v1 transactions, which also reduces dependency on address lookup tables from previous transactions and moves fee and resource limit information to a separate transactionConfig setting.

Existing systems may encounter issues reading v1 transactions: indexers and fee sponsors that only scan ComputeBudget instructions might miss the fee cap or read it as zero. The Solana Foundation's transaction-v1 example repository explains v1 messages contain TransactionConfig instead of ComputeBudget instructions. RPC documentation advises adding maxSupportedTransactionVersion: 1 to getTransaction, getBlock, and blockSubscribe calls; omitting this may cause errors in processing v1 transactions.

gRPC and Geyser paths present quieter issues where older protobuf stubs might discard Message.config fields, potentially causing fee configuration omissions without system failure. The Foundation recommends minimum versions including @solana/kit 8.0.0, yellowstone-grpc-proto 12.6.0, and yellowstone-grpc geyser 15.1.1 for proper handling.

While the Solana status page shows no incidents reported on September 4, 2026 for Mainnet Beta RPC nodes, infrastructure compatibility remains critical. The upgrade represents a technical roadmap requiring sequential preparation of wallets, RPC, indexers, and development tools rather than a single event. v1 transactions will not replace legacy v0 format but require supporting applications to enable the new structure.

Service operators must verify their systems handle v1 message structures correctly through key checks including maxSupportedTransactionVersion: 1 configuration, transactionConfig storage path reflection, gRPC protobuf stub regeneration, and recognition of the 0x81 version prefix. The Solana upgrade page currently lists 'Larger Transaction Sizes' as pending activation until September 4, 2026.

Korean Source

This article is an English localization of a Korean-language crypto news report. Original headline: 솔라나 v1 거래 4096바이트 전환 앞두고 호환성 점검