Struct index_program::instructions::create_pointer::CreatePointer

pub struct CreatePointer<'info> {
    pub index: Account<'info, Index>,
    pub pointer: Account<'info, Pointer>,
    pub proof: Account<'info, Proof>,
    pub owner: Signer<'info>,
    pub system_program: Program<'info, System>,
}

Fields

index: Account<'info, Index>

pointer: Account<'info, Pointer>

proof: Account<'info, Proof>

owner: Signer<'info>

system_program: Program<'info, System>

Trait Implementations

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

fn try_accounts(
    program_id: &Pubkey,
    accounts: &mut &[AccountInfo<'info>],
    ix_data: &[u8]
) -> Result<Self, ProgramError>

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 CreatePointer<'info> where
    'info: 'info, 

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

program_id is the currently executing program.

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

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

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