Address Lookup Table Account

Overview

Solana transactions can involve many accounts, but the serialized transaction has a size limit. An address lookup table stores frequently used account addresses in a dedicated on-chain account. A versioned transaction can then include the table’s address and compact indexes identifying entries in that table.

This reduces the number of bytes needed for account references and allows a transaction to use more accounts than would otherwise fit. The table does not replace authorization. Signers, writable accounts, and program accounts still have their normal roles; the lookup table only supplies addresses.

Lookup tables have lifecycle and operational rules. They must be created and extended before use, and recently added addresses may not be immediately usable in the same slot. Applications need to fetch the correct table state and ensure that referenced indexes resolve to the intended addresses. A stale, unavailable, or incorrectly selected table can cause transaction construction or simulation to fail.

The term is specific to Solana’s versioned transaction design. It should not be generalized to every blockchain account model.

Applications usually create a lookup table in advance and extend it with addresses that will be reused. A versioned transaction then lists the table and the indexes needed for that operation. This can support complex swaps, routing, and multi-program transactions that would exceed the normal account-address limit.

Operationally, the client must fetch the correct table state and wait until newly added entries are active under Solana’s slot rules. If a table is deactivated, closed, stale, or referenced with the wrong index, transaction compilation or execution can fail. Wallets and signing devices also need to resolve the looked-up addresses so users can understand what they are authorizing.