Earn yield without Impermanent Loss risks!
Chainflip provides people the ability to earn a liquidity provisioning fee of 0.05% on every swap which uses the liquidity pool the user has deposited funds in.
The way Chainflip liquidity provisioning works is by having limit and range orders in a liquidity pool. While range orders are passive in nature, they are a lower class citizen compared to limit orders. Limit orders need to be actively managed however.
This managing can be done manually via the Chainflip LP Dashboard, or automatically via the Chainflip LP API. The manual approach is still in reach for retail users but requires constant babysitting to place new orders. The automated way is too complicated for retail users.
This bot automates limit orders according to a user their price preferences, automatically placing new limit orders when balance is available.
The orders are limited to the USDT/USDC/arbUSDC stablecoin pools since they do not require tracking index prices and are low risk because there is no impermanent loss risk. A dollar for a dollar.
- Slides are available at drive.google.com/file/d/1rjavro4P2e0Z0Im4BeMyipPK5Ra-mpb4
- Presentation is available at youtube.com/watch?v=iaxfLvpclaQ
- A recent Docker version: docs.docker.com/engine/install/ubuntu/
- The
docker-compose-plugin
installed. This should be present if you followed the Docker installation instructions. - If you want to run as root, make sure to add
-u root
to everydocker run
command below.
Start by downloading the docker-compose.yml
file, or copying it:
Linux users can also run wget https://github.com/raw/CumpsD/chainflip-lp/main/docker-compose.yml
services:
lp:
image: chainfliplabs/chainflip-lp-api:1.5
pull_policy: always
stop_grace_period: 5s
stop_signal: SIGINT
restart: unless-stopped
environment:
- RUST_LOG=info
volumes:
- .:/etc/chainflip/keys
entrypoint:
- /usr/local/bin/chainflip-lp-api
command:
- --state_chain.ws_endpoint=wss://mainnet-rpc.chainflip.io:443
cf-lp:
image: ghcr.io/cumpsd/chainflip-lp:v8.0.9
pull_policy: always
restart: unless-stopped
working_dir: "/app"
environment:
- DOTNET_PRINT_TELEMETRY_MESSAGE=false
- Bot__EnableLp=true
- Bot__QueryDelay=60000
- Bot__NodeRpcUrl=https://mainnet-rpc.chainflip.io
- Bot__LpRpcUrl=http://lp
- Bot__LpAccount=cF_YOUR_LP_ACCOUNT
- Bot__DustOrderSize=5
- Bot__MinimumOrderSize=20
- Bot__TelegramChannelId=-1001234567890
- Bot__Pools__0__Chain=Ethereum
- Bot__Pools__0__Asset=USDT
- Bot__Pools__0__Slice=80
- Bot__Pools__0__MinBuyTick=0
- Bot__Pools__0__MaxBuyTick=1
- Bot__Pools__0__MinSellTick=0
- Bot__Pools__0__MaxSellTick=-1
- Bot__Pools__1__Chain=Arbitrum
- Bot__Pools__1__Asset=USDC
- Bot__Pools__1__Slice=20
- Bot__Pools__1__MinBuyTick=0
- Bot__Pools__1__MaxBuyTick=1
- Bot__Pools__1__MinSellTick=0
- Bot__Pools__1__MaxSellTick=-1
- Serilog__MinimumLevel__Override__ChainflipLp=Information
depends_on:
- lp
We start by generating a new signing key for the Chainflip LP API. This will be your LP account. Run the following command and save the Validator Account ID and Seed Phrase!
docker run -v .:/etc/chainflip --entrypoint=/usr/local/bin/chainflip-cli chainfliplabs/chainflip-cli:1.4 generate-keys --path .
The following steps need to be followed to fund your LP account with FLIP, which is needed to submit transactions to the Chainflip network. These steps are explained in detail in the Chainflip Funding documentation.
Note: The minimum funding amount for registering as a Broker or LP role is technically 1 FLIP. However, we recommend funding your accounts with at least 5 FLIP to account for transaction fees.
- Make sure you have
$FLIP
(ERC-20) in your EVM crypto wallet. - Go to Chainflip Auctions Dashboard > "My Nodes".
- Connect your crypto wallet containing the
$FLIP
. - Click the button "+ Add Node" > You should see the "Register new node" dialog.
- Enter the Validator ID you got during the previous step — your
Validator Public Key (SS58)
— and the amount of$FLIP
you want to fund. Click on "Add Funds". - Your crypto wallet will ask you to sign two transactions. The first one is a token approval and the second one transfers and add funds to your validator.
- Congratulations! Your LP account is now funded, you can now jump ahead to the All Users steps below.
Either:
- Add your
signing_key_file
next to thedocker-compose.yml
file if you have an existing one. - Create a
signing_key_file
containing the private key of your Chainflip LP account and make sure it has no trailing newline!
If you do not have your private key anymore, but you have your seed phrase, run the following:
docker run -v .:/etc/chainflip --entrypoint=/usr/local/bin/chainflip-cli chainfliplabs/chainflip-cli:1.4 generate-keys --path . --seed-phrase "12 words here"
Proceed to the All Users steps below once you have this.
- Create a new group.
- Invite
@chainflip_lp_bot
to the new group. - Find the group channel id, you can do this by getting the link to the group, it is the number behind the
#
sign. (For example https://web.telegram.org/k/#-1001234567890)
- Open the
docker-compose.yml
file. - Replace
cF_YOUR_LP_ACCOUNT
with your LP account. - Replace
-1001234567890
with the telegram channel id. - If needed, configure the
_Slice
settings to how you would like to balance your funds between USDT and arbUSDC. The total needs to be 100! (In the example above, it is divided in 80/20) - Save the file.
- Run
docker compose up -d
to start the bot. - Run
docker compose logs -f -n 100
to follow the logs. - Every minute it will output the status of your balance, open orders and perform order placing activity.
- Go to Chainflip Liquidity Dashboard.
- If needed, install Polkadot.js and import your Chainflip LP account.
- Deposit USDC, USDT or arbUSDC into your account.
This project uses:
To simplify setup for a user, Docker has been used to bundle the LP API in a preconfigured way with the public Chainflip Node RPC. Thanks to this a user only has to provide their keys to run the Liquidity Bot, and not have to set up an LP API themselves.
The RPC methods are used to retrieve a user their available undeployed balance. Based on the available balance and the configured minimum order amount it then proceeds to place a limit order.
This limit order takes into account the user their share preference between the USDT/USDC and arbUSDC/USDC pools. (solUSDC can easily be added when it launches). Additionally the limit order also respects the configured tick price for each pool.
When an order is placed, a Telegram bot informs the user about this as well.