Skip to content

node: use loaded addresses for Solana ALT resolution #4649 - #4950

Closed
ayushmishra2005 wants to merge 1 commit into
wormhole-foundation:mainfrom
ayushmishra2005:fix/solana-alt-loaded-addresses-#4649
Closed

node: use loaded addresses for Solana ALT resolution #4649#4950
ayushmishra2005 wants to merge 1 commit into
wormhole-foundation:mainfrom
ayushmishra2005:fix/solana-alt-loaded-addresses-#4649

Conversation

@ayushmishra2005

Copy link
Copy Markdown

Fixes #4649.

Summary

For versioned Solana transactions, use TransactionMeta.LoadedAddresses to populate lookup-table account keys when the metadata contains the complete set of loaded addresses.

This avoids fetching historical ALT accounts when the resolved addresses are already available in the transaction metadata, so transactions can still be processed after an ALT has been closed.

If LoadedAddresses is missing or incomplete, the watcher falls back to the existing ALT RPC lookup path.

Changes

  • Use loaded writable and readonly addresses from transaction metadata when complete.
  • Preserve Solana account ordering: static keys, writable loaded addresses, then readonly loaded addresses.
  • Keep the existing ALT lookup path as a fallback.
  • Add coverage for deleted ALTs, missing/incomplete metadata, and loaded-address ordering.

@djb15

djb15 commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

@djb15 djb15 closed this Aug 24, 2026
@ayushmishra2005

Copy link
Copy Markdown
Author

Thanks @djb15 for pointing me to the contribution policy. I understand and won’t open further PRs without coordinating first. I’m actively interested in contributing to Wormhole, particularly around Solana protocol/watcher work. If there’s an appropriate issue or area where an external contributor would be useful, I’d appreciate any guidance.

@djb15

djb15 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Thanks for understanding. Glad to hear you're interested in contributing. Generally we aim to avoid changing Watcher related components where possible since they're high risk areas of the codebase. One area we can improve in that's low risk is test coverage. If you're interested in Solana specifically you could consider adding test coverage there. Specifically I would suggest looking at basing any changes off of #4924 which makes some small refactors to the Solana watcher to aid in writing effective tests.

@ayushmishra2005

Copy link
Copy Markdown
Author

Thanks, that’s helpful.

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.

Solana Account Lookup Table (ALT) Message Dropping

2 participants