Struct strategy_vaults::CreateVaultTwo

pub struct CreateVaultTwo<'info> {

    pub vault: Box<Account<'info, Vault>>,
    pub base: Signer<'info>,
    pub manager: Signer<'info>,
    pub payer: Signer<'info>,
    pub system_program: Program<'info, System>,
    pub stake_info_account_v4: Box<Account<'info, RaydiumUserStakeInfoV4>>,
    pub stake_info_account_v5: UncheckedAccount<'info>,
    pub farm_token_a_reward_custody_account: Box<Account<'info, TokenAccount>>,
    pub farm_token_b_reward_custody_account: Box<Account<'info, TokenAccount>>,
    pub farm_lp_token_account: Box<Account<'info, TokenAccount>>,
    pub farm_reward_token_a_account: Box<Account<'info, TokenAccount>>,
    pub farm_reward_token_b_account: Box<Account<'info, TokenAccount>>,
    pub serum_coin_vault_account: Box<Account<'info, TokenAccount>>,
    pub serum_pc_vault_account: Box<Account<'info, TokenAccount>>,
    pub fees_account_a: Box<Account<'info, TokenAccount>>,
    pub fees_account_b: Box<Account<'info, TokenAccount>>,
    pub serum_bids: UncheckedAccount<'info>,
    pub serum_asks: UncheckedAccount<'info>,
    pub serum_event_queue: UncheckedAccount<'info>,
}

Fields

vault: Box<Account<'info, Vault>>

This is a vault info account.

base: Signer<'info>

Base of the Vault address.

manager: Signer<'info>

Manager of the vault.

payer: Signer<'info>

Fee payer.

system_program: Program<'info, System>

System program.

stake_info_account_v4: Box<Account<'info, RaydiumUserStakeInfoV4>>

stake_info_account_v5: UncheckedAccount<'info>

CHECK: this one is created here.

farm_token_a_reward_custody_account: Box<Account<'info, TokenAccount>>

Farm Reward Custody Account TokenAccount

farm_token_b_reward_custody_account: Box<Account<'info, TokenAccount>>

farm_lp_token_account: Box<Account<'info, TokenAccount>>

farm_reward_token_a_account: Box<Account<'info, TokenAccount>>

farm_reward_token_b_account: Box<Account<'info, TokenAccount>>

serum_coin_vault_account: Box<Account<'info, TokenAccount>>

serum_pc_vault_account: Box<Account<'info, TokenAccount>>

fees_account_a: Box<Account<'info, TokenAccount>>

fees_account_b: Box<Account<'info, TokenAccount>>

serum_bids: UncheckedAccount<'info>

CHECK: Raydium verifies

serum_asks: UncheckedAccount<'info>

CHECK: Raydium verifies

serum_event_queue: UncheckedAccount<'info>

CHECK: Raydium verifies

Trait Implementations

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

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.

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

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

program_id is the currently executing program.

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

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

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

impl<'info> Validate<'info> for CreateVaultTwo<'info>

fn validate(&self) -> Result<()>

Validates the account struct.