TransactionView: Static Account Keys Meta

[apfitzge]

Problem

• Task in [Tracking] TransactionView #2255
• Parse static accounts

Summary of Changes

• Parse static accounts
• Additional checks that number of static accounts is valid

Fixes #

[LucasSte]

Is StaticAccountMeta going to represent AccountMeta?

agave/sdk/program/src/instruction.rs

Lines 544 to 551 in 51208f8

	pub struct AccountMeta {
	/// An account's public key.
	pub pubkey: Pubkey,
	/// True if an `Instruction` requires a `Transaction` signature matching `pubkey`.
	pub is_signer: bool,
	/// True if the account data or metadata may be mutated during program execution.
	pub is_writable: bool,
	}

I was wondering if you should account for the two booleans in addition to the public key.

[apfitzge]

no unrelated to that struct. Have just been naming all my internal transaction view structs holding offsets/sizes with Meta suffixes.

The is_signer and is_writable are not part of the actual packet and are implied by combination of account index and information from the header.
So these will be functions on the wrapping transaction_view once I add the accessor functions.

[LucasSte]

I mixed up the names and thought they were related. How about calling the struct StaticAccountKeyMeta?

[apfitzge]

59cdc7c

[apfitzge]

@LucasSte I rebased with #2408 to rename the functions