liquidity & slippage docs
This commit is contained in:
13
src/slippage.md
Normal file
13
src/slippage.md
Normal file
@@ -0,0 +1,13 @@
|
||||
# Slippage
|
||||
|
||||
The term [slippage](https://en.wikipedia.org/wiki/Slippage_(finance)) refers to the difference between the price you expected, or the original market price, and the actual price you got when the trade was completed. The more volume you want to trade, the higher your slippage becomes.
|
||||
|
||||
In DeFi, slippage can be mechanically caused by [MEV](https://ethereum.org/en/developers/docs/mev) actors within a single block, so proper slippage controls use either oracle prices or something like a time-weighted average price (TWAP) as the "true" price.
|
||||
|
||||
Dexorder uses the 10-second TWAP as reported by the Uniswap v3 price oracles. If a price oracle has not been configured for a particular pool, Dexorder uses the pool's current reported price instead. The order's slippage control is then applied to this "true" price and the price limit is passed to the pool during the swap.
|
||||
|
||||
Slippage is set to 0.30% by default, and may not be lower than 0.01%.
|
||||
|
||||
If an attempted execution hits the slippage control, then it fills partially and enters a brief cooldown period before attempting the trade again.
|
||||
|
||||
If your order is large enough to move the market and trigger slippage controls, consider using Dexorder's DCA or Dates tool to split up your order.
|
||||
Reference in New Issue
Block a user