Struct Modify

pub struct Modify<'info> {
    pub merkle_tree: UncheckedAccount<'info>,
    pub authority: Signer<'info>,
    pub noop: Program<'info, Noop>,
}

Context for modifying a tree: inserting, appending, or replacing a leaf in the existing tree and setting the canopy or finalizing a prepared tree.

Modification instructions also require the proof to the leaf to be provided as 32-byte nodes via “remaining accounts”.

Fields

merkle_tree: UncheckedAccount<'info>

CHECK: This account is validated in the instruction

authority: Signer<'info>

Authority that controls write-access to the tree Typically a program, e.g., the Bubblegum contract validates that leaves are valid NFTs.

noop: Program<'info, Noop>

Program used to emit changelogs as cpi instruction data.

Trait Implementations

impl<'info> Accounts<'info, ModifyBumps> for Modify<'info>

where 'info: 'info,

fn try_accounts( __program_id: &Pubkey, __accounts: &mut &'info [AccountInfo<'info>], __ix_data: &[u8], __bumps: &mut ModifyBumps, __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 Modify<'info>

where 'info: 'info,

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

program_id is the currently executing program.

impl<'info> Bumps for Modify<'info>

where 'info: 'info,

type Bumps = ModifyBumps

Struct to hold account bump seeds.

impl<'info> ToAccountInfos<'info> for Modify<'info>

where 'info: 'info,

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

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