Struct multisig_lite::Approve

pub struct Approve<'info> {
    pub signer: Signer<'info>,
    pub state: Box<Account<'info, State>>,
    pub fund: UncheckedAccount<'info>,
    pub system_program: Program<'info, System>,
}

Accounts for the multisig_lite::approve instruction handler.

Once one of the signer approves, the account is locked for the new transfer unless:

1. Meets the m number of signers approval.
2. Closes the account.

In case of the 1 above, the account will be unlocked and starts to take a new transfer again.

Fields

signer: Signer<'info>

An approver of the current state of the multisg account.

state: Box<Account<'info, State>>

A multisig state PDA account.

fund: UncheckedAccount<'info>

A multisig fund account.

CHECK: Checked by the multisig_lite::approve instruction handler.

system_program: Program<'info, System>

The system program to create a transfer account.

Trait Implementations

impl<'info> Accounts<'info> for Approve<'info>where
    'info: 'info,

fn try_accounts(
    program_id: &Pubkey,
    accounts: &mut &[AccountInfo<'info>],
    ix_data: &[u8],
    __bumps: &mut BTreeMap<String, u8>,
    __reallocs: &mut BTreeSet<Pubkey>
) -> Result<Self>

Returns the validated accounts struct. What constitutes “valid” is program dependent. However, users of these types should never have to worry about account substitution attacks. For example, if a program expects a Mint account from the SPL token program in a particular field, then it should be impossible for this method to return Ok if any other account type is given–from the SPL token program or elsewhere.

impl<'info> AccountsExit<'info> for Approve<'info>where
    'info: 'info,

fn exit(&self, program_id: &Pubkey) -> Result<()>

program_id is the currently executing program.

impl<'info> ToAccountInfos<'info> for Approve<'info>where
    'info: 'info,

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

impl<'info> ToAccountMetas for Approve<'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.