Solana: dal preventivo al regolamento
Solana address lookup tables: compressed references, full responsibilities
A shorter transaction encoding does not mean the loaded accounts matter less.
Articoli e grafici tecnici sono in inglese. La navigazione è disponibile in 7 lingue.
Guide di riferimento
Why lookup tables exist
Complex Solana instructions can involve many account addresses. Address lookup tables let supported versioned transactions refer to stored addresses with compact indices instead of repeating every full 32-byte address. A table can hold up to 256 addresses. This is an encoding mechanism, not a grant of unlimited execution capacity: transaction account limits and other runtime constraints remain separate. 1
The transaction version matters
The current Solana guide distinguishes v0 transactions, which support lookup tables, from the V1 format, which carries addresses inline and does not support ALTs. Do not generalise ‘all versioned transactions use tables’ or copy old size limits into a guide without naming the format. Wallet and client support must be checked against the specific transaction being reviewed.
Resolve before interpreting
The compact reference has to be resolved to actual account addresses before a reviewer can understand which programs and accounts an instruction uses. A wallet should make those resolved identities and their permissions understandable. The mere presence of an ALT is not suspicious, just as its absence is not a safety guarantee. What matters is the resulting message and the operations it authorises.
Investigation notes
When documenting a trade or program interaction, retain the signature, transaction version, loaded addresses and relevant instruction decoding. An incomplete screenshot that omits loaded accounts can hide important context from a later reader. Distinguish a serialization convenience from a real reduction in account access. A concise message still needs a complete explanation of its consequences.
Esempio concreto
A route needs accounts from several pools. A v0 message contains indices into a lookup table for some of them. The message is smaller, but the swap still touches the resolved pool accounts. An analyst must include these addresses when reconstructing the route.