Upgradeable InfinityPools architecture

• The above is accomplished by making the InfinityPoolsFactory an UpgradeableBeacon. When InfinityPools are deployed, they are deployed as BeaconProxies. Each BeaconProxy queries the UpgradeableBeacon for the current InfinityPool implementation and then uses delegateCall to that implementation.
• This design makes it easier to upgrade all the InfinityPools simultaneously. The InfinityPoolsFactory owner deploys a new InfinityPools implementation and updates it in the UpgradeableBeacon. All the InfinityPools will now delegateCall to the same updated contract.
• The periphery contract is a UUPSUpgradeable contract. Its implementation can be changed by the same owner of the InfinityPoolsFactory.

InfinityPoolsPeriphery

Users interact with InfinityPools through InfinityPoolsPeriphery for both liquidity management and swapper creation. InfinityPoolsPeriphery mints liquidity providers and traders unique NFTs that represent their positions.

Pool Selection

Based on the provided token0, token1 and splits, InfinityPoolsPeriphery determines the correct InfinityPool by calling getPool from InfinityPoolsFactory.

LPing

1. Creating an LP Position:

   • For adding liquidity, the user calls the addLiquidity function, passing these arguments

     struct AddLiquidityParams {
             address token0;
             address token1;
             int256 splits;
             int256 startEdge;
             int256 stopEdge;
             uint256 amount0Desired;
             uint256 amount1Desired;
             uint256 amount0Min;
             uint256 amount1Min;
         }
     

   • The (startEdge, stopEdge) identifies a range where the liquidity should be added

   • The amount0Min, amount0Desired and amount1Min, amount1Desired define the ranges of the token0 and token1 amounts for the LPing TX to succeed

   • For creating a swapper, the user calls the newLoan function.

• Start Earning
  • For the provided liquidity to be able to start earning, this has to be "tapped" which is done by calling the tap()
  • For this to be possible, the liquidity has to match 2 criteria
    • have been just added and
    • a certain amount of time has to be passed
  • The minimum amount of time required by the LPing position to be able to accrue yield is called earnEra
• Collecting LPing Yield
  • The LPing yield can be collected by calling the collect() function
  • Calling that API results in withdrawing all the yield accrued up to that point in time
  • As long as the position has not been tapped, it does not accrue any yield
• Withdrawing Liquidity
  • The liquidity withdrawal is not immediate, it can happen gradually and depending on the available liquidity in the pool
  • It is started by calling drain() and a minimum time has to be passed for this to be possible
  • Once that liquidity has been marked as "drainable" it stops accruing yield and it is possible to withdraw it gradually over time by calling collect() which allows for withdrawing both the principal and accumulated yield if any remaining