Deposit

There are 2 ways to deposit to Tempest's Rebalancing Symetric Strategy Vault:

• Deposit single-side token by using deposit function

• Deposit dual-side token by using deposits function

Single-side token deposit

Anyone can perform an single-side token depositing by calling this function:

/// @param amount The amount of tokens to deposit
/// @param receiver The address that will receive the shares of the deposit
/// @param checkSlippage When providing liquidity to Ambient Pool, Tempest's Vault checks the slippage of the pool price vs oracle price to prevent attacker from manipulating pool price and arbitrage provided liquidity.
///                      However, in some cases, user is too bullish in the vault and want to deposit regardless of the price. Checking slippage may cause the deposting failed, especially if the price moves rapidly.
///                      So that checkSlippage indicates that the vault should check slippage when providing liquidity or not.
///                      Be careful when deposit with checkSlippage = false because of the chance to be arbitraged.
/// @return shares The amount of shares minted for the deposited amount
function deposit(
    uint256 amount,
    address receiver,
    bool checkSlippage
  ) external payable returns (uint256 shares)

Basically, we have to send 2 tokens (token 0 and token 1) at the rate equivalent to the current pool price when providing liquidity to Ambient's Pool.

But by using deposit function, only single-side token need to be deposited to Tempest's Vault (only token 0 or only token 1). Before providing liquidity to Ambient Pool, Tempest's Vault automatically performs a swap at oracle price with a small slippage. Tempest's Vault performs the swap via the Ambient Pool directly. This function brings the convenience for the client because the client does need to calculate how many token 0 and token 1 needed for providing liquidity. All is handled by Tempest's Vault.

Dual-side token deposit

Dual-side token depositing can be performed by calling:

/// @param amounts An array of token amounts to deposit [amount0, amount1]
/// @param receiver The address that will receive the shares of the deposit
/// @param checkSlippage When providing liquidity to Ambient Pool, Tempest's Vault checks the slippage of the pool price vs oracle price to prevent attacker from manipulating pool price and arbitrage provided liquidity.
///                      However, in some cases, user is too bullish in the vault and want to deposit regardless of the price. Checking slippage may cause the deposting failed, especially if the price moves rapidly.
///                      So that checkSlippage indicates that the vault should check slippage when providing liquidity or not.
///                      Be careful when deposit with checkSlippage = false because of the chance to be arbitraged.
/// @return shares The amount of shares minted for the deposited amount
function deposits(
    uint256[] memory amounts,
    address receiver,
    bool checkSlippage
  ) external payable returns (uint256 shares)

If the client uses deposits, it requires the client to calculate amount of token 0 and token 1 to be provided as liquidity to Ambient Pool. The client can use these functions from Tempest's Vault for the calculation:

/// @notice Calculates the amount of token1 needed for a given amount of token0
/// @param amountToken0 The amount of token0
/// @return The calculated amount of token1
function calculateAmount1ForAmount0(uint256 amountToken0) external view returns (uint256)

/// @notice Calculates the amount of token0 needed for a given amount of token1
/// @param amountToken1 The amount of token1
/// @return The calculated amount of token0
function calculateAmount0ForAmount1(uint256 amountToken1) external view returns (uint256)

Dual-side depositing should be used in case of the new pool or a large depositing when the pool does not have enough liquidity so the swap in single-side depositing can not be performed successfully.