Solana v1 raises the transaction-size limit to 4,096 bytes, but it is not a drop-in replacement for legacy or v0 transactions. Builders must move resource settings into the message configuration, remove address lookup table assumptions, and readers must opt in to v1 explicitly. Legacy and v0 remain limited to 1,232 bytes.
What changes with Solana v1 transactions?
The familiar 1,232-byte ceiling still applies to legacy and v0 transactions. V1 introduces a separate transaction format with a 4,096-byte maximum, inline addresses, and resource settings stored in the message configuration. These are format-level changes: software that constructs, submits, decodes, or analyzes transactions needs to recognize which version it is handling.
As an Amazon Associate I earn from qualifying purchases.
| Format | Maximum serialized transaction size | Address representation and documented limit | Resource settings | Priority fee representation |
|---|---|---|---|---|
| Legacy | 1,232 bytes (Solana Documentation, 2026) | Inline addresses; the documented comparison lists 32 addresses (Solana Documentation, 2026) | ComputeBudget instructions | Micro-lamports per compute unit, multiplied by the requested compute limit |
| v0 | 1,232 bytes (Solana Documentation, 2026) | Address lookup tables can supply addresses; the documented comparison lists 256 addresses (Solana Documentation, 2026) | ComputeBudget instructions | Micro-lamports per compute unit, multiplied by the requested compute limit |
| v1 | 4,096 bytes (Solana Documentation, 2026) | Inline addresses only; 64-address format limit (Solana Documentation, 2026) | Message configuration; omitted compute-unit and loaded-account-data limits default to zero | Total fee in lamports |
The 1,232-byte figure is also the value of Solana’s PACKET_DATA_SIZE constant. It describes the MTU-derived packet payload, not the maximum serialized size of a v1 transaction. A larger v1 transaction can be carried over QUIC in multiple frames; this does not mean a single network packet grew to 4,096 bytes.
Which existing code breaks, and why?
Builders that rely on address lookup tables
V1 does not support address lookup tables (ALTs). V0 can use an ALT to refer to addresses compactly; v1 carries addresses inline, with a format limit of 64 addresses. A builder that creates lookup references must use a compatible format or construct the v1 message with inline addresses. The larger byte envelope does not raise the address limit.
#1 Best Overall
- EAL5+ CERTIFIED SECURE ELEMENT + FINGERPRINT PROTECTION — Your private keys stay encrypted offline on a certified EAL5+ chip, the same security tier used in EMV bank cards. Built by DCENT, securing crypto since 2018. Fingerprint authentication adds a second layer no PIN-only wallet can match.
- 10,000+ ASSETS NATIVE ON 100+ BLOCKCHAINS — Hold Bitcoin, Ethereum, XRP, Solana, Cardano, popular stablecoins (USDT, USDC), and NFTs in one wallet. No third-party apps, no fragmented setup — every supported asset works straight out of the box.
- TAP-TO-SIGN MOBILE EXPERIENCE — Pair your wallet with the DCENT mobile app over Bluetooth. Manage tokens, review transactions, and access in-app swap features directly from your phone — no cables, no desktop required.
- WEB3 & dAPP ACCESS VIA METAMASK — Connect to MetaMask and other browser extension wallets to manage NFTs, claim airdrops, and access dApps. A large screen and intuitive 4-button interface keep every transaction clearly visible before you sign.
- SEAMLESS FIRMWARE UPDATES & 30-DAY MONEY-BACK GUARANTEE — Apply security updates without resetting your wallet or migrating funds. Backed by Amazon's 30-day money-back guarantee — your purchase is risk-free.
Builders that set budgets with ComputeBudget instructions
In v1, compute-unit and loaded-account-data limits belong in the message’s transactionConfig, not in ComputeBudget instructions. The configuration is signed message content and uses fixed-position fields; parsers must account for those fields and reject unknown config bits.
V1 ComputeBudget instructions are not rejected, but they do not set resource limits. They execute as successful no-ops, consume 150 compute units each, and use one of the 64 instruction slots. Remove them from v1 transactions rather than relying on them to configure the budget.
Fee calculations copied from legacy or v0
Legacy and v0 represent the priority fee as a micro-lamports-per-compute-unit price multiplied by the requested compute limit. V1 represents the priority fee as a total number of lamports. Reusing the older multiplication or rounding calculation can therefore produce an incorrect v1 fee.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
Readers that assume every message has the old shape
A v1 JSON message includes a transactionConfig object; legacy and v0 messages do not. Code that decodes only the older message shape, or analytics that infer budgets and fees solely by scanning ComputeBudget instructions, will miss v1 settings.
How should a transaction builder migrate to v1?
- Choose the format deliberately. Keep legacy or v0 for flows that need the existing format or depend on ALTs. Use v1 when the transaction needs its larger size envelope and its address and client requirements fit v1.
- Replace ALT references with inline addresses. Check the total address count against v1’s 64-address limit, and measure the resulting serialized message rather than assuming a larger byte limit removes all constraints.
- Set both resource limits in the v1 message configuration. Provide a compute-unit limit and a loaded-account-data limit. Unset values default to zero, which can make execution fail.
- Estimate limits by simulation. Solana’s documentation recommends simulating with both limits maximized, then using the returned
unitsConsumedandloadedAccountsDataSize. For loaded-account data, round up to the next 32 KiB page to provide headroom. This is the documented procedure, not a guarantee that a particular transaction will succeed. - Move the priority fee to the v1 representation. Encode the intended total fee in lamports; do not calculate it by multiplying a per-compute-unit price by the compute limit.
- Remove v1 ComputeBudget instructions. They will not configure the limits or fee in v1 and still consume compute and an instruction slot.
- Serialize and submit using a compatible client path. For transactions larger than 1,232 bytes, Solana’s documentation recommends base64 for submission and client-side decoding. Base58 remains subject to the older size cap.
How do RPC readers and indexers opt in to v1?
Set the supported transaction version to the JSON integer 1
For transaction and block RPC reads, specify maxSupportedTransactionVersion as the JSON number 1, not the string "1". Omitting the setting or passing 0 causes v1 reads to fail. A v1 transaction can cause an entire getBlock response to fail rather than yielding a partial block.
{
"maxSupportedTransactionVersion": 1
}Apply the same version-awareness to blockSubscribe consumers: they must handle v1 messages and the version-aware behavior described in Solana’s versioned-transaction documentation.
Rank #3
- 【Military‑grade EAL6+ security&Easy to Use】Safnect crypto wallet eatures the top-tier EAL6+ security technology and a sealed secure-element chip — No Bluetooth. No Wi‑Fi. No battery. No seed phrase to manage. Your cryptocurrencies stay strongly protected from online attackers, it is immune to remote hacks and effortless for first-time users.
- 【3-Pack Backup = Double Secure】This 100% offline hardware wallet not just a 3‑pack. It's a breakthrough in key management.You can store these three cold crypto wallets in separate locations for safer, decentralized asset protection.
- 【Instant Tap Connection&Friendly for Begginer】Simply tap the crypto wallet card against your mobile device to pair with the Safnect App in seconds. Effortlessly buy, sell and transfer crypto assets safely through the app. Experience the fast convenience of a hot wallet, paired with the robust security of genuine cold storage.
- 【Multi-Chain & Multi-Account Management】 The Safnect cold crypto wallet seamlessly manages Bitcoin, Ethereum, Solana, and over 2,800 tokens across 54+ mainstream blockchains, giving you complete multi-chain and multi-account control.You can buy, sell, swap, stake, and spend cryptocurrency directly any time any way.
- 【Basically Indestructible&Easy to Carry】Only 2 mm thin with a credit-card sized design, this crypto wallet features IP66 waterproofing and bend-resistant construction. If you're a crypto holder who travels for work or just moves around a lot, you already know the struggle: Safnect crypto wallet that actually fits your life.
Decode configuration instead of inferring it from instructions
When a returned message is v1, parse its transactionConfig to read resource and fee settings. Keep legacy and v0 parsing paths for messages that do not include that object. Analytics that continue to scan only ComputeBudget instructions will not capture v1’s configured limits or total fee.
Recommended Free Tools
Check SDK support before upgrading a client
Solana’s documentation lists @solana/kit 8.0+, Agave 4.2.x-generation Rust crates, and web3.js v3 among the recent support generations. It says web3.js v1 can read v1 beginning at 1.99.0 but cannot build or send v1 transactions. Treat these as documentation-listed compatibility points, not a substitute for checking the exact package or crate version in your application.
Is the 4,096-byte limit active, and what can it enable?
The Solana Foundation’s upgrade page, updated September 2026, reports v1 active on mainnet, testnet, and devnet. It gives mainnet activation as the beginning of epoch 1035 on September 15, 2026, at approximately 01:00 UTC.
Rank #4
- All your digital assets in one place. You can manage thousands of crypto including Bitcoin, Ethereum, Solana, Tether and more.
- Connectivity: USB-C cable connection only. No Bluetooth.Compatible with the Ledger Wallet crypto app, both desktop (Windows, macOS, Linux) and mobile (Android only). Not compatible with iOS.
- Protect your digital assets with the industry's best security: keep your private keys offline in your private signer, battle-tested by the Donjon's white hat hackers, CC EAL 6+ certified Secure Element, constantly updated Ledger OS.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Choose the colors that match your style: express your personality and your crypto management mood, color code your signers, one for each use (trading, staking, HOLDing...).
The Foundation identifies larger ZK proofs, Confidential Transfer proofs, Winternitz one-time signatures, nested multisigs, and BLS signature schemes as potential beneficiaries of the larger envelope. More bytes alone do not increase compute budget or account capacity. Before switching a workload, consider four constraints together:
- Serialized bytes: Does the encoded transaction exceed the 1,232-byte legacy/v0 ceiling?
- Addresses: Can the transaction fit within v1’s 64 inline addresses without ALTs?
- Compute and account data: Can the transaction’s resource needs be configured and fit within applicable limits?
- Compatibility: Can every builder, signer, RPC reader, and indexer in the path handle v1?
For an application that depends on ALTs or clients that cannot yet construct and read v1, v0 remains a valid choice. V1 is useful when its additional byte capacity solves a real transaction-size problem and the entire transaction path supports the format.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
