The way this seems to work is (in order of "resolved" accounts array):
Message (static) accounts have source = Transaction.
ALT writable accounts with source = LookupTable.
ALT readonly accounts with source = LookupTable.
I'm not sure where in the struct hierarchy this belongs as LoadedAddresses are in Meta, while Accounts is on Transaction.Message), so possibly at the Transaction level?
We should have this but I would like to keep type.Transaction more primitive atm. Maybe I will declare a new struct ParsedTransaction to implement this. Let me think about it.
Should solana-go-sdk expose something like this on the Client interface?
https://github.com/solana-labs/solana/pull/27552/files
The way this seems to work is (in order of "resolved" accounts array):
I'm not sure where in the struct hierarchy this belongs as LoadedAddresses are in Meta, while Accounts is on Transaction.Message), so possibly at the Transaction level?