Introduction
Last updated
Last updated
Clipper has a hybrid onchain/offchain infrastructure. We expose an API to you with price feeds and a k-parameter, and give you the formula that we use to quote prices based on those + onchain data. That way you can route based on predictions of what clipper will quote, and then once you’re ready to actually use Clipper in a route you request a quote from our servers. Output scales with input so you can compose in multihop trades.
Clipper prioritizes protecting LP yield and restricts toxic bot flow. We value real users. To ensure we’re prevention of toxic flow we have verification methods in place. Specifically we make a verification on the wallets used for the swaps and we check whether they are EOA (not contracts), have a min amount of ETH, and have done previous txs.
Client retrieves pool information
Client inputs pool information (price feeds, k factor, etc) in the formula to predict quotes.
Client retrieves a firm quote from API
Client creates a swap transaction in the clipper pool contract using values from previous step.
For more details about integration check How to use clipper RFQ API?
Ethereum Mainnet
1
Polygon Mainnet
137
Optimism Mainnet
10
Moonbeam Mainnet
1284
Mantle Mainnet
5000
Arbitrum One
42161
If you want to review our contracts for each supported network, please refer to this link
Interacting with Clipper Exchange
To see who else has integrated with Clipper, checkout the data page: https://clipper.exchange/data
If you want to integrate with Clipper send us a message here
