Struct tulipv2_sdk_common::config::strategy::withdraw::WithdrawAddresses

pub struct WithdrawAddresses {
    pub authority: Pubkey,
    pub multi_vault: Pubkey,
    pub multi_vault_pda: Pubkey,
    pub multi_burning_shares_token_account: Pubkey,
    pub withdraw_burning_shares_token_account: Pubkey,
    pub receiving_underlying_token_account: Pubkey,
    pub multi_underlying_withdraw_queue: Pubkey,
    pub multi_shares_mint: Pubkey,
    pub platform_config: PlatformConfigAddresses,
    pub tulip_standalone_addresses: Option<TulipStandaloneAddresses>,
    pub solend_standalone_addresses: Option<SolendStandaloneAddresses>,
    pub mango_standalone_addresses: Option<MangoStandaloneAddresses>,
}

Fields

authority: Pubkey

multi_vault: Pubkey

multi_vault_pda: Pubkey

multi_burning_shares_token_account: Pubkey

withdraw_burning_shares_token_account: Pubkey

receiving_underlying_token_account: Pubkey

multi_underlying_withdraw_queue: Pubkey

multi_shares_mint: Pubkey

platform_config: PlatformConfigAddresses

tulip_standalone_addresses: Option<TulipStandaloneAddresses>

solend_standalone_addresses: Option<SolendStandaloneAddresses>

mango_standalone_addresses: Option<MangoStandaloneAddresses>

Implementations

impl WithdrawAddresses

pub fn new(
    user: Pubkey,
    vault: Pubkey,
    vault_pda: Pubkey,
    shares_mint: Pubkey,
    underlying_mint: Pubkey,
    underlying_withdraw_queue: Pubkey,
    platform_config: PlatformConfigAddresses,
    standalone_config: (&[Pubkey], Platform)
) -> Result<WithdrawAddresses, Error>

Trait Implementations

impl Clone for WithdrawAddresses

fn clone(&self) -> WithdrawAddresses

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl WithdrawMultiOptimizerVault for WithdrawAddresses

fn authority(&self) -> Pubkey

fn multi_deposit_vault(&self) -> Pubkey

the main vault that users interact with, which is called a MultiDepositOptimizerVaultV1

fn multi_deposit_vault_pda(&self) -> Pubkey

fn withdraw_vault(&self) -> Pubkey

to enable maximal defi legos, multiple “standalone vaults” may exist, where a single standalone vault is deposits one asset (ie USDC) into one protocol (ie Tulip), this allows the standalone vaults to be reused by any of tulip’s v2 vaults for maximal composability

fn withdraw_vault_pda(&self) -> Pubkey

fn platform_information(&self) -> Pubkey

an account which stores information related to the platform/protocol a standalone vault is deposited into

fn platform_config_data(&self) -> Pubkey

an account which stores configuration information related to the standalone vault for the platform/protocol being farmed

fn lending_program(&self) -> Pubkey

fn multi_burning_shares_token_account(&self) -> Pubkey

the token account owned by the caller/authority which holds onto the tokenized shares issued by the multi deposit vault. these would be the tokens that you remove from a deposit tracking account with the withdraw_deposit_tracking instruction

fn withdraw_burning_shares_token_account(&self) -> Pubkey

just like other v2 vaults, the standalone vaults issue shares, however these shares are held, and managed by the multi deposit vault

fn receiving_underlying_token_account(&self) -> Pubkey

the token account which will receive the underlying assets backing the shares once the shares have been burned

fn multi_underlying_withdraw_queue(&self) -> Pubkey

a token account that holds onto assets in between various steps of the withdraw flow

fn multi_shares_mint(&self) -> Pubkey

the mint of the tokenized shares issued by the multi deposit vault

fn withdraw_shares_mint(&self) -> Pubkey

the mint of the tokenized shares issued by the standalone vault which we are withdrawing from

fn withdraw_vault_underlying_deposit_queue(&self) -> Pubkey

the deposit queue account used by the standalone vault to hold funds while they are being deposited. even though this is a withdraw instruction, the deposit queue account is needed so that when the vault rebases before the withdraw happens, all assets are accounted for

fn standalone_vault_accounts(&self) -> Option<Vec<AccountMeta>>

returns accounts specific to the standalone vault being used

fn instruction(&self, amount: u64) -> Option<Instruction>

returns the Instruction object which can be used to invoke the withdraw_multi_optimizer_vault instruction via CPI, or off-chain clients

fn ix_data(&self) -> Option<[u8; 8]>

fn to_account_meta(&self, _is_signer: Option<bool>) -> Vec<AccountMeta>

please note the _is_signer variable is ignored, it’s simply here to provide compatibility

impl Copy for WithdrawAddresses