An on-chain account that stores a list of addresses. A versioned transaction can refer to an address by its index in the table, one byte instead of 32, so it can touch many more accounts within the transaction size limit.
Why it matters
A transaction has a size limit, and every account address costs 32 bytes. Lookup tables are how programs with many accounts, such as swaps across several pools, stay within it. If your team builds that kind of instruction, they need to know how to create, extend and use tables.
What to check
- Ask whether the program needs lookup tables and who creates and maintains them.
- Ask how the client falls back when a table is missing or not yet active.
How it works in practice
A lookup table is created and filled with an on-chain instruction, and a table can hold up to 256 addresses. An address added to a table can be used from a later slot, not in the same slot it was added.
A table has an authority that can extend or close it. Tables that many users rely on are usually controlled by the team that runs the app.
Common mistakes
- Building the transaction with a table that is not active yet, so it fails right after creation.
- Leaving the table authority on a single key with no plan for rotation.
- Assuming every wallet will accept a transaction that uses a table.
Related terms
- Versioned transactionThe Solana transaction format that supports address lookup tables.
- ProgramSolana’s term for a smart contract: executable code deployed to an account.
- AccountThe unit of storage on Solana.
- CPI (cross-program invocation)A call from one Solana program to another within the same transaction, for example a DeFi program calling the Token Program to move tokens.
Describe your project in plain English. Smart Match suggests verified Solana providers with a reason for each match. Free for teams.
Get matched →