Supported DEX Pools
 | By: brandoniles July 23, 2020, 12:29 a.m. |
Platforms Requiring Active Support
Pools on Uniswap V2, Balancer, and SushiSwap require active support from the protocol. It is recommended that LPs stay away from AMPL pools on those platforms not included in the lists below:
Uniswap V2
SushiSwap
Balancer
- USDC-AMPL - Smart Rebasing Pool that avoids most impermanent loss. (Read More)
- WBTC-ETH-AMPL - Indexed portfolio with equal weights.
Platforms With Native Support
These platforms require no active support from the Ampleforth protocol. You are free to use AMPL pools here like you would any other pool.
- Mooniswap
- Uniswap V1
- KyberSwap
- Bancor V1
Why do some DEX pools require "support" and what does "support" mean?
The AMPL has a unique supply adjustment mechanism, called rebase. The rebase operation automatically updates all wallet balances according to demand in the marketplace. This also includes all contract balances, including DEX pools.
Some platforms are coded to read AMPL balances directly from the underlying token. These work natively with AMPL, and add no extra risk to Liquidity Providers or traders compared to other pools on those platforms. (See: "Platforms with Full Native Support")
However, other DEXes cache a copy of token balances in their own contract code, separate from the normal token accounting. This parallel accounting can get out-of-sync with the actual AMPL balances when a rebase happens. These platforms therefore require notification to re-read the underlying AMPL balance and update their internal accounting numbers.
Active Support means these pool updates occur atomically within the rebase transaction itself. Actively supported pools add no extra risk to LPs compared to other non-AMPL pools on those platforms.
For Uniswap V2, this is done via the sync() call.
For Balancer, this is done via the gulp() call.
Requests for New Pools
If you would like a new pool to be added, please follow the Ampleforth Configuration Change Proposal (ACCP) process. It may be helpful to first consult with the community to see if there's sufficient support. A good place to do that is in the Ampleforth Discord.
Overall, the intention is to be conservative with what's added. Each supported pool adds gas requirements onto the rebase transaction, and once a pool is supported it's difficult to remove safely for LPs.
Finally--because of the risks involved to LPs, please coordinate support before creating the pool!
Hello!
Could we please get at least a response if AMPL support is possible for our pool in the future and a rough timeframe if and when, since it is a bit risky to keep a pool like this at the current state of deflationary and rebase token support of balancer. There are some people that want to join our liquidity pool but do not, because they are waiting for an official response by AMPL. If a pool like ours is not possible to be supported this is totally fine. But at the point, every day running this pool holds a certain risk of getting attacked.
Also creating a balancer pool is expensive and I need to know if its better to pull liquidity at this point and wait for an more official support response.
Thank you!
Hey Titus!
In that case I recommend minimizing risk for right now because we expect to be slow to move here.
For context on how we're approaching this in the beginning... we need to be very conservative with what we add because once we include support it will be very difficult to remove safely. LPs of pools who don't get the message to pull funds, should we get there, could lose a lot. On top of that, the AMM space is changing rapidly and we don't want too much churn.
I know this isn't what you were hoping for right now, but hope that makes sense.
Find me on twitter at @brandoniles
Hello brandoniles thank you very much for your answer.
I got one question concerning a potential fix for balancer pools.
Would it possible work to use an AMPL / ETH uniswap pool token for a balancer pool like the UNI-V2 pool token used in geyser to avoid the sync() issues? If this would indeed be a potential fix, I would give a new pool with a setup like this a try.
Downside of this is of course that those pool tokens are not whitelisted by balancer and no BAL tokens will be collected, but this is a small downside considering the pool will be bullet proof from the sync() flash loan attacks. Also the volume might be smaller.
Best Regards
Titus.
Yes, that definitely works as long as you use a liquidity token from a supported Uniswap pool. The downside is that traders wouldn't be able to trade AMPL natively on the platform (only the liquidity tokens that contain ample). LPs still get some exposure to AMPL, though, which I think is what you're looking for.
Find me on twitter at @brandoniles
Okay thanks brandoniles.
The experiment of my pool ended yesterday when someone attacked it and drained like 1000$ in total. The attacker seemed to perform the same type of attack like on those other pools.....
https://etherscan.io/tx/0xa6a7de3ad8f54be247f02603600cabe4a52651d804aa6f93ba404e10ef18572d
1000$ is not the end of the world for us. But the question remains why this thread here suggests, that there is a chance to get a pool officially supported, while in reality it is not. AMPL should make this more clear!
Best Regards.
Titus.
Connect with Twitter
Hello I requested support for a community pool.
Here is the thread with all infor: https://www.ampltalk.org/app/forum/governance-20/topic/request-to-add-support-for-community-balancer-pool-62/
Cheers