Struct ValidateReferrer 

pub struct ValidateReferrer<'info> {
    pub buddy_link_program: AccountInfo<'info>,
    pub payer: AccountInfo<'info>,
    pub authority: AccountInfo<'info>,
    pub referee_buddy_profile: AccountInfo<'info>,
    pub referee_buddy: AccountInfo<'info>,
    pub referee_treasury: AccountInfo<'info>,
    pub referee_member: AccountInfo<'info>,
    pub referrer_member: Option<AccountInfo<'info>>,
    pub referrer_treasury: Option<AccountInfo<'info>>,
    pub referrer_treasury_for_reward: Option<AccountInfo<'info>>,
    pub referrer_token_account: Option<AccountInfo<'info>>,
    pub mint: Option<AccountInfo<'info>>,
}

Fields

buddy_link_program: AccountInfo<'info>

CHECK: The buddylink program

payer: AccountInfo<'info>

CHECK: Payer of the transaction

authority: AccountInfo<'info>

CHECK: Authority

referee_buddy_profile: AccountInfo<'info>

CHECK: Buddy Link Profile of the referee.

referee_buddy: AccountInfo<'info>

CHECK: Buddy Link Paid buddy of the referee (could be the same as above).

referee_treasury: AccountInfo<'info>

CHECK: Referee treasury (is owned by above).

referee_member: AccountInfo<'info>

CHECK: Referee member (account of the referee within your organization).

referrer_member: Option<AccountInfo<'info>>

CHECK: Referrer member (account of the referrer within your organization) (if you want to validate the referrer of the current referee).

referrer_treasury: Option<AccountInfo<'info>>

CHECK: Referrer treasury (treasury that owns the referrer member ) (if you want to validate the referrer of the current referee).

referrer_treasury_for_reward: Option<AccountInfo<'info>>

CHECK: Referrer treasury for reward (treasury that is linked to the current mint, could be the same as above) (if you want to validate the referrer of the current referee).

referrer_token_account: Option<AccountInfo<'info>>

CHECK: Token account linked to the mint (if you want to validate the referral tree with a specific mint)

mint: Option<AccountInfo<'info>>

CHECK: The mint

Trait Implementations

impl<'info> Accounts<'info, ValidateReferrerBumps> for ValidateReferrer<'info>

where 'info: 'info,

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

where 'info: 'info,

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

program_id is the currently executing program.

impl<'info> Bumps for ValidateReferrer<'info>

where 'info: 'info,

type Bumps = ValidateReferrerBumps

Struct to hold account bump seeds.

impl<'info> ToAccountInfos<'info> for ValidateReferrer<'info>

where 'info: 'info,

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

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