Transaction version (0) is not supported

The RPC node, wallet, or program does not support versioned transactions (version 0). It only understands legacy transactions.

Common causes

1. Old RPC node. The node runs a Solana validator version that predates versioned transaction support (pre-1.13).
2. Legacy SDK code. Your code sends a VersionedTransaction to an endpoint that expects a legacy Transaction.
3. Wallet does not support v0. Some older wallet adapters do not handle versioned transactions.
4. RPC method parameter missing. Methods like getBlock and getTransaction require maxSupportedTransactionVersion: 0 to return versioned transactions.

How to fix

1. Add maxSupportedTransactionVersion. When calling RPC methods, include the parameter:

const block = await connection.getBlock(slot, {
  maxSupportedTransactionVersion: 0,
});

const tx = await connection.getTransaction(signature, {
  maxSupportedTransactionVersion: 0,
});

2. Update your RPC node. Ensure the node runs Solana validator v1.13 or later.
3. Use a legacy transaction. If you do not need Address Lookup Tables, use a legacy Transaction instead of VersionedTransaction.
4. Update wallet adapter. Use the latest version of @solana/wallet-adapter which supports versioned transactions.

Legacy vs. versioned transactions

FAQ

What is a versioned transaction? Version 0 (v0) transactions support Address Lookup Tables, which allow referencing up to 256 accounts without increasing transaction size. They were introduced in Solana v1.13.

Do all RPC providers support versioned transactions? Yes, all modern RPC providers support v0 transactions. If you encounter this error, check that you are passing maxSupportedTransactionVersion: 0 in your RPC calls.

Can I mix legacy and versioned transactions? Yes. You choose per transaction. Use legacy when you do not need lookup tables, and versioned when you do.

Updated: 2026-10-21