Struct strategy_vaults::accounts::CreateVaultThree

pub struct CreateVaultThree {
    pub vault: Pubkey,
    pub base: Pubkey,
    pub manager: Pubkey,
    pub payer: Pubkey,
    pub system_program: Pubkey,
    pub stake_info_account: Pubkey,
    pub stake_info_account_v5_mainnet: Pubkey,
    pub stake_info_account_orca: Pubkey,
}

Generated client accounts for CreateVaultThree.

Fields

vault: Pubkey

This is a vault info account.

base: Pubkey

Base of the Vault address.

manager: Pubkey

Manager of the vault.

payer: Pubkey

Fee payer.

system_program: Pubkey

System program.

stake_info_account: Pubkey

stake_info_account_v5_mainnet: Pubkey

stake_info_account_orca: Pubkey

Trait Implementations

impl BorshSerialize for CreateVaultThree where
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize,
    Pubkey: BorshSerialize, 

fn serialize<W: Write>(&self, writer: &mut W) -> Result<(), Error>

fn try_to_vec(&self) -> Result<Vec<u8, Global>, Error>

Serialize this instance into a vector of bytes.

impl ToAccountMetas for CreateVaultThree

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.