Struct hpl_asset_assembler::instructions::nft::BurnNFT

pub struct BurnNFT<'info> {

    pub project: Box<Account<'info, Project>>,
    pub assembler: Box<Account<'info, Assembler>>,
    pub nft: Box<Account<'info, NFT>>,
    pub nft_mint: Account<'info, Mint>,
    pub nft_metadata: AccountInfo<'info>,
    pub nft_master_edition: AccountInfo<'info>,
    pub token_account: Account<'info, TokenAccount>,
    pub unique_constraint: Option<Account<'info, NFTUniqueConstraint>>,
    pub delegate_authority: Option<Account<'info, DelegateAuthority>>,
    pub authority: Signer<'info>,
    pub payer: Signer<'info>,
    pub vault: AccountInfo<'info>,
    pub system_program: Program<'info, System>,
    pub hive_control: Program<'info, HplHiveControl>,
    pub token_program: Program<'info, Token>,
    pub token_metadata_program: AccountInfo<'info>,
    pub instructions_sysvar: AccountInfo<'info>,
}

Accounts used in the burn nft instruction

Fields

project: Box<Account<'info, Project>>

assembler: Box<Account<'info, Assembler>>

Assembler state account

nft: Box<Account<'info, NFT>>

NFT account

nft_mint: Account<'info, Mint>

NFT mint account

nft_metadata: AccountInfo<'info>

Metadata account of the NFT CHECK: This is not dangerous because we don’t read or write from this account

nft_master_edition: AccountInfo<'info>

Master Edition account of the NFT CHECK: This is not dangerous because we don’t read or write from this account

token_account: Account<'info, TokenAccount>

NFT token account

unique_constraint: Option<Account<'info, NFTUniqueConstraint>>

NFT unique constraint

delegate_authority: Option<Account<'info, DelegateAuthority>>

authority: Signer<'info>

The wallet that holds the pre mint authority over this NFT

payer: Signer<'info>

Payer account

vault: AccountInfo<'info>

CHECK: This is not dangerous because we don’t read or write from this account

system_program: Program<'info, System>

NATIVE SYSTEM PROGRAM

hive_control: Program<'info, HplHiveControl>

HIVE CONTROL PROGRAM

token_program: Program<'info, Token>

SPL TOKEN PROGRAM

token_metadata_program: AccountInfo<'info>

METAPLEX TOKEN METADATA PROGRAM CHECK: This is not dangerous because we don’t read or write from this account

instructions_sysvar: AccountInfo<'info>

NATIVE Instructions SYSVAR CHECK: This is not dangerous because we don’t read or write from this account

Trait Implementations

impl<'info> Accounts<'info> for BurnNFT<'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 BurnNFT<'info>

where 'info: 'info,

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

program_id is the currently executing program.

impl<'info> ToAccountInfos<'info> for BurnNFT<'info>

where 'info: 'info,

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

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