Struct quarry_mine::ExtractFees

source · [−]

pub struct ExtractFees<'info> {
    pub rewarder: Account<'info, Rewarder>,
    pub claim_fee_token_account: Account<'info, TokenAccount>,
    pub fee_to_token_account: Account<'info, TokenAccount>,
    pub token_program: Program<'info, Token>,
}

Expand description

Accounts for quarry_mine::extract_fees.

Fields

rewarder: Account<'info, Rewarder>

Rewarder to extract fees from.

claim_fee_token_account: Account<'info, TokenAccount>

TokenAccount which receives claim fees.

fee_to_token_account: Account<'info, TokenAccount>

TokenAccount owned by the addresses::FEE_TO. Holds DAO claim fees.

token_program: Program<'info, Token>

Token program

Trait Implementations

source

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

source

fn try_accounts(
 program_id: &Pubkey,
 accounts: &mut &[AccountInfo<'info>],
 ix_data: &[u8 ],
 __bumps: &mut BTreeMap<String, u8>
) -> 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. Read more

source

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

source

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

program_id is the currently executing program.

source

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

source

fn to_account_infos(&self) -> Vec<AccountInfo<'info>>ⓘNotable traits for Vec<u8, A>`impl<A> Write for Vec<u8, A> where A: Allocator,`

source

impl<'info> ToAccountMetas for ExtractFees<'info>

source

fn to_account_metas(&self, is_signer: Option<bool>) -> Vec<AccountMeta>ⓘNotable traits for Vec<u8, A>`impl<A> Write for Vec<u8, A> where A: Allocator,`

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. Read more

source