The Solana transaction format that supports address lookup tables. Version 0 transactions can reference far more accounts than a legacy transaction, and clients and wallets must support the format to read and sign them.
Why it matters
Versioned transactions are the only way to use address lookup tables, so any app with large transactions depends on them. Wallets, RPC providers and indexers have to handle the format, and some older tooling does not.
What to check
- Ask which transaction version the app sends and whether every wallet and RPC provider you rely on supports it.
- Ask how the indexer reads version 0 transactions.
How it works in practice
Legacy transactions list every account in the message. Version 0 transactions can also load accounts through lookup tables, which makes room for more accounts in the same size limit.
Code that reads transactions has to ask for version 0 support explicitly. A client that does not do so can miss or reject these transactions.
Common mistakes
- Reading transactions with a client that does not request version 0, so some transactions seem to be missing.
- Building a version 0 transaction for a wallet that only signs legacy ones.
- Not testing the largest realistic transaction before launch.
Related terms
- Address lookup tableAn on-chain account that stores a list of addresses.
- RPC nodeA server that applications use to read Solana data and submit transactions.
- IndexerAn off-chain service that reads Solana transactions and accounts and stores them in a queryable database, so applications can show history and aggregated data quickly.
- Compute units (CU)The measure of computation a Solana transaction may use.
Guides
Describe your project in plain English. Smart Match suggests verified Solana providers with a reason for each match. Free for teams.
Get matched →