ACCP 3: Include support for the kMPL/AMPL Uniswap liquidity pool in the Ampleforth sync() function call fired during rebase Source


Simple Summary

This proposal requests a configuration change that will enable the sync() function call that occurs at Ampleforth rebase to include the incentivized kMPL/AMPL Uniswap v2 token pair.


We are requesting a configuration change so that the sync() function called on rebase includes the incentivized kMPL/AMPL Uniswap v2 pair.


The AmpleSense DAO is an independent, community-powered organization. Its mission is to expand the ecosystem of products and services (including in the areas of education, lending, borrowing and elastic finance) surrounding the Ampleforth protocol.

One of the DAO’s critical initial activities was to distribute its governance token KiloAmple (kMPL) to the community via its “kGeyser” liquidity programs. The DAO has committed to distributing 73% of the token supply via these programs. The first kGeyser program, Zeus was launched in early November and rewards AMPL/ETH Uniswap liquidity providers with kMPL tokens.

The second kGeyser liquidity mining program is called Apollo. The AmpleSense DAO’s two-stage governance process revealed (vote) that AMPL was the overwhelming choice of the community to be paired with the kMPL token in the Apollo kGeyser.

The kMPL/AMPL Uniswap v2 pair is currently live on Uniswap and liquidity providers are receiving kMPL rewards for providing liquidity.

However, kMPL/AMPL trading has not yet begun. To activate trading, a configuration change must be made within the Ampleforth protocol to ensure the kMPL/AMPL pair is incorporated into the sync() function call that is fired upon rebase.

The motivation for this ACCP is to request this critical configuration change, which is required to initiate Uniswap trading on the kMPL/AMPL pair.


Copyright and related rights waived via CC0.