Struct PostUpdateAtomic

pub struct PostUpdateAtomic<'info> {
    pub payer: AccountInfo<'info>,
    pub guardian_set: AccountInfo<'info>,
    pub config: AccountInfo<'info>,
    pub treasury: AccountInfo<'info>,
    pub price_update_account: AccountInfo<'info>,
    pub system_program: AccountInfo<'info>,
    pub write_authority: AccountInfo<'info>,
}

Fields

payer: AccountInfo<'info>

guardian_set: AccountInfo<'info>

Instead we do the same steps in deserialize_guardian_set_checked.

config: AccountInfo<'info>

treasury: AccountInfo<'info>

price_update_account: AccountInfo<'info>

The constraint is such that either the price_update_account is uninitialized or the write_authority is the write_authority. Pubkey::default() is the SystemProgram on Solana and it can’t sign so it’s impossible that price_update_account.write_authority == Pubkey::default() once the account is initialized

system_program: AccountInfo<'info>

write_authority: AccountInfo<'info>

Trait Implementations

impl<'info> ToAccountInfos<'info> for PostUpdateAtomic<'info>

fn to_account_infos(&self) -> Vec<AccountInfo<'info>>

impl<'info> ToAccountMetas for PostUpdateAtomic<'info>

fn to_account_metas(&self, is_signer: Option<bool>) -> Vec<AccountMeta>

is_signer is given as an optional override for the signer meta field. This covers the edge case when a program-derived-address needs to relay a transaction from a client to another program but sign the transaction before the relay. The client cannot mark the field as a signer, and so we have to override the is_signer meta field given by the client.