Skip to content

replay: use correct rules to resolve address lookup tables - #311

Merged
smcio merged 2 commits into
Overclock-Validator:alpenglow-devfrom
cavemanloverboy:replay-alt-resolution
Oct 18, 2026
Merged

smcio merged 2 commits into
Overclock-Validator:alpenglow-devfrom
cavemanloverboy:replay-alt-resolution

Conversation

@cavemanloverboy

@cavemanloverboy cavemanloverboy commented Oct 18, 2026 •

Copy link
Copy Markdown
  • return an error when block accounts fail to load during replay, so a lookup table that fails to resolve results in rejected block.
  • apply protocol's lookup table rules in replay (owner, lamports, deactivation against the block's SlotHashes, data, index bounds), on both whole-block and streaming paths.
| check  | fails when                                   | error                            |
|--------|----------------------------------------------|----------------------------------|
| exists | table missing, or 0 lamports                 | `AddressLookupTableNotFound`     |
| owner  | not owned by the ALT program                 | `InvalidAddressLookupTableOwner` |
| data   | uninitialized or doesn't decode              | `InvalidAddressLookupTableData`  |
| status | deactivated (out of the block's SlotHashes¹) | `AddressLookupTableNotFound`     |
| index  | any lookup index ≥ the table's active length | `InvalidAddressLookupTableIndex` |

¹ the parent's SlotHashes plus the parent slot; a table deactivated in the current slot is still usable.

@smcio
smcio merged commit 348704c into Overclock-Validator:alpenglow-dev Oct 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants