You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support Uniswap V3 alongside Uniswap V2 as a liquidity source.
Motivation
As liquidity is migrating from Uniswap V2 to Uniswap V3, it looks appropriate for RigoBlock to supporting the further source of liquidity.
Specification
RigoBlock supports Uniswap V2 through AUniswapV2. A similar adapter should be created and plugged into the RigoBlock protocol in order to pull from Uniswap V3 liquidity. A further adapter is required, as liquidity providing in Uniswap V3 is now managed through NonfungiblePositionManager.sol.
Rationale
Just as with the Uniswap V2 adapter, the Uniswap V3 adapter should mirror all methods implemented in the Uniswap V3 periphery, so that external applications can bundle encoded Uniswap RPC calls to be routed through RigoBlock pools.
Summary
Support Uniswap V3 alongside Uniswap V2 as a liquidity source.
Motivation
As liquidity is migrating from Uniswap V2 to Uniswap V3, it looks appropriate for RigoBlock to supporting the further source of liquidity.
Specification
RigoBlock supports Uniswap V2 through AUniswapV2. A similar adapter should be created and plugged into the RigoBlock protocol in order to pull from Uniswap V3 liquidity. A further adapter is required, as liquidity providing in Uniswap V3 is now managed through NonfungiblePositionManager.sol.
Rationale
Just as with the Uniswap V2 adapter, the Uniswap V3 adapter should mirror all methods implemented in the Uniswap V3 periphery, so that external applications can bundle encoded Uniswap RPC calls to be routed through RigoBlock pools.
Notes
Uniswap V3 periphery contracts
AUniswapV2
The text was updated successfully, but these errors were encountered: