Once again the game-changing DEX 🦄 👑

Image source: https://uniswap.org/blog/uniswap-v3/

The announcement of Uniswap v3 is no doubt one of the most exciting news in the DeFi place recently 🔥🔥🔥

While most have talked about the impact v3 can potentially bring on the market, seldom explain the delicate implementation techniques to realize all those amazing features, such as concentrated liquidity, limit-order-like range orders, etc.

Since I’ve covered Uniswap v1 & v2 (if you happen to know Mandarin, here are v1 & v2), there’s no reason for me to not cover v3 as well!

Thus, this article aims to guide readers through Uniswap v3, based on their official whitepaper and examples made on the announcement page. However, one needs not to be an engineer, as not many codes are involved, nor a math major, as the math involved is definitely taught in your high school, to fully understand the following content 😊

If you really make it through but still don’t get shxt, feedbacks are welcomed! 🙏

There should be another article focusing on the codebase, so stay tuned and let’s get started with some background noise!

Before diving in, we have to first recap the uniqueness of Uniswap and compare it to traditional order book exchanges.

Uniswap v1 & v2 are a kind of AMMs (automated market marker) that follow the constant product equation x * y = k, with x & y stand for the amount of two tokens X and Y in a pool and k as a constant.

Comparing to order book exchanges, AMMs, such as the previous versions of Uniswap, offer quite a distinct user experience:

In an order book, each price (whether in green or red) is a tick. Image source:

¹ though the price gets worse over time; AMM of constant sum such as mStable does not have infinite liquidity

² the range is in fact [-∞,∞], while a price in most cases won’t be negative

³ AMM of constant sum does not have price slippage

For those unfamiliar with what is a tick:

Source: https://www.investopedia.com/terms/t/tick.asp

By slicing the price range [0,∞] into numerous granular ticks, trading on v3 is highly similar to trading on order book exchanges, with only three differences:

With the tick design, Uniswap v3 possesses most of the merits of both AMM and an order book exchange! 💯💯💯

This question is actually somewhat related to the tick explanation above: the minimum tick size for stocks trading above 1$ is one cent.

The underlying meaning of a tick size traditionally being one cent is that one cent (1% of 1$) is the basis point of price changes between ticks, ex: 1.02 — 1.01 = 0.1.

Uniswap v3 employs a similar idea: compared to the previous/next price, the price change should always be 0.01% = 1 basis point.

However, notice the difference is that the traditional basis point is in absolute value 0.1, which means the price change is defined with subtraction, while here in v3 the basis point is in percentage 0.1%, which is defined with division.

This is how price ranges of ticks are decided⁴:

Image source: https://uniswap.org/whitepaper-v3.pdf

With the above equation, the tick/price range can be recorded in the index form [i, i+1], instead of some crazy numbers such as 1.0001¹⁰⁰ = 1.0100496621.

As each price is the multiplication of 1.0001 of the previous price, the price change is always 1.0001 — 1 = 0.0001 = 0.01%.

For example, when i=1, p(1) = 1.0001; when i=2, p(2) = 1.00020001.

p(2) / p(1) = 1.00020001 / 1.0001 = 1.0001

See the connection between the traditional basis point 1 cent (=1% of 1$) and Uniswap v3’s basis point 0.01%?

Image source: https://tenor.com/view/coin-master-cool-gif-19748052

But sir, are prices really granular enough? There are many shitcoins with prices less than 0.000001$. Will such prices be covered as well?

To know if an extremely small price is covered or not, we have to figure out the max & min price range of v3 by looking into the spec: there is a int24 tick state variable in UniswapV3Pool.sol.

Image source: https://uniswap.org/whitepaper-v3.pdf

The reason for a signed integer int instead of an uint is that negative power represents prices less than 1 but greater than 0.

24 bits can cover the range between 1.0001 ^ (2²³ — 1) and 1.0001 ^ -(2)²³. Even Google cannot calculate such numbers, so allow me to offer smaller values to have a rough idea of the whole price range:

1.0001 ^ (2¹⁸) = 242,214,459,604.341

1.0001 ^ -(2¹⁷) = 0.000002031888943

I think it’s safe to say that with a int24 the range can cover > 99.99% of the prices of all assets in the universe 👌

⁴ For implementation concern, however, a square root is added to both sides of the equation.

How about finding out which tick does a price belong to?

The answer to this question is rather easy, as we know that p(i) = 1.0001^i, simply takes a log with base 1.0001 on both sides of the equation⁴:

Image source: https://www.codecogs.com/latex/eqneditor.php

Let’s try this out, say we wanna find out the tick index of 1000000.

Image source: https://ncalculators.com/number-conversion/log-logarithm-calculator.htm

Now, 1.0001¹³⁸¹⁶² = 999,998.678087146. Voila!

⁵ This formula is also slightly modified to fit the real implementation usage.

Now that we know how ticks and price ranges are decided, let’s talk about how orders are executed in a tick, what is concentrated liquidity and how it enables v3 to compete with stablecoin-specialized DEXs (decentralized exchange), such as Curve, by improving the capital efficiency.

Concentrated liquidity means LPs (liquidity providers) can provide liquidity to any price range/tick at their wish, which causes the liquidity to be imbalanced in ticks.

As each tick has a different liquidity depth, the corresponding pricing function x * y = k also won’t be the same!

Each tick has its own liquidity depth. Image source: https://uniswap.org/blog/uniswap-v3/

Mmm… examples are always helpful for abstract descriptions!

Say the original pricing function is 100(x) * 1000(y) = 100000(k), with the price of X token 1000 / 100 = 10 and we’re now in an arbitrary price range [9.08, 11.08].

If the liquidity of the price range [11.08, 13.08] is the same as [9.08, 11.08], we don’t have to modify the pricing function if the price goes from 10 to 11.08, which is the boundary between two ticks.

The price of X is 1052.63 / 95 = 11.08 when the equation is 1052.63 * 95 = 100000.

However, if the liquidity of the price range [11.08, 13.08] is two times that of the current range [9.08, 11.08], balances of x and y should be doubled, which makes the equation become 2105.26 * 190 = 400000, which is (1052.63 * 2) * (95 * 2) = (100000 * 2 * 2).

We can observe the following two points from the above example:

What’s more, compared to liquidity on v1 & v2 is always spread across [0,∞], liquidity on v3 can be concentrated within certain price ranges and thus results in higher capital efficiency from traders’ swapping fees!

Let’s say if I provide liquidity in the range [1200, 2800], the capital efficiency will then be 4.24x higher than v2 with the range [0,∞] 😮 There’s a capital efficiency comparison calculator, make sure to try it out!

Image source: https://uniswap.org/blog/uniswap-v3/

(The content of this section is updated on May 8; the previous description of excluding the last scenario of the three of being also range orders was wrong.)

As explained in the above section, LPs of v3 can provide liquidity to any price range/tick at their wish. The behaviour of LPs providing liquidity on v3 is called (creating) range orders.

Depending on the current price and the targeted price range, there are three scenarios:

These three scenarios have disparities in whether both or only one of the two tokens and also the number of (which) tokens is required/allowed when providing liquidity.

Case 1 can be further divided into even two more cases: the current price is central to the targeted price range, or not.

If the current price happens to be central to the targeted price range (current price = 10 when the price range is [8, 12]), it’s the exact same liquidity providing mechanism as the previous versions: LPs provide liquidity in both tokens of the same value (= amount * price).

If the current price is not central to the price range, LPs still have to provide liquidity in both tokens, while the amount of each token depends on the distance between the current price and the price range, which will be explained in the next section (though not explicitly).

There’s a similar product to the case: grid trading, a very powerful investment tool for a time of consolidation. Dunno what’s grid trading? Check out Binance’s explanation on this, as this topic won’t be covered!

In fact, LPs of Uniswap v1 & v2 are grid trading with a range of [0,∞] and the entry price as the baseline.

Unlike Case 1 where both tokens are required for providing liquidity, in Cases 2 and 3 only one of the two tokens is required/allowed.

To understand the reason for the above statement, we’d have to first revisit how price is discovered on Uniswap with the equation x * y = k, for x & y stand for the amount of two tokens X and Y and k as a constant.

The price of X compared to Y is y / x, which means how many Y one can get for 1 unit of X, and vice versa the price of Y compared to X is x / y.

For the price of X to go up, y has to increase and x decrease.

With this pricing mechanism in mind, it’s example time!

Say an LP plans to place liquidity in the price range [15.625, 17.313], higher than the current price of X 10, when 100(x) * 1000(y) = 100000(k), which is Case 2.

If now the price of X reaches 15.625, the only way for the price of X to go even higher is to further increase y and decrease x, which means exchanging a certain amount of X for Y.

Thus, to provide liquidity in the range [15.625, 17.313], an LP needs only to prepare 80 — 76 = 4 of X. If the price exceeds 17.313, all 4 X of the LP is swapped into 1315.789 — 1250 = 65.798 Y, and then the LP has nothing more to do with the pool, as his/her liquidity is drained.

What if the price stays in the range? It’s exactly what LPs would love to see, as they can earn swapping fees for all transactions in the range! Also, the balance of X will swing between [76, 80] and the balance of Y between [1250, 1315.789].

This might not be obvious, but the example above shows an interesting insight: if the liquidity of one token is provided, only when the token becomes more valuable will it be exchanged for the less valuable one.

…wut?

Remember that if 4 X is provided within [15.625, 17.313], only when the price of X goes up from 15.625 to 17.313 is 4 X gradually swapped into Y, the less valuable one!

This is the reason why in Cases 2 & 3 only one of the two tokens is required/allowed when providing liquidity: in fact, LPs providing liquidity is essentially providing a token for others to exchange when that token becomes more valuable!

What if the price of X drops back to 15.625 immediately after reaching 17.313? As X becomes less valuable, others are going to exchange Y for X, which can eventually make the 65.798 Y (previously swapped from 4 X) be swapped back into 4 X.

The below image illustrates the scenario of DAI/USDC pair with a price range of [1.001, 1.002] well: the pool is always composed entirely of one token on both sides of the tick, while in the middle 1.001499⁷ is of both tokens.

Image source: https://uniswap.org/blog/uniswap-v3/

Similarly, to provide liquidity in a price range < current price, which is Case 3, an LP has to prepare a certain amount of Y for others to exchange Y for X within the range.

To wrap up such an interesting feature, we know that:

I will be discussing more the impacts of v3 in 5. Impacts of v3.

⁷ 1.001499988 = √(1.0001 * 1.0002) is the geometric mean of 1.0001 and 1.0002. The implication is that the geometric mean of two prices is the average execution price within the range of the two prices.

As the example in the last section demonstrates, if there is 4 X in range [15.625, 17.313], the 4 X will be completely converted into 65.798 Y when the price goes over 17.313.

We all know that a price can stay in a wide range such as [10, 12] for quite some time, while it’s unlikely so in a narrow range such as [15.6, 15.7].

Thus, if an LP provides liquidity in [15.6, 15.7], we can expect that once the price of X goes over 15.6 and immediately also 15.67, and does not drop back, all X are then forever converted into Y.

The concept of having a targeted price and the order will be executed after the price is crossed is exactly the concept of limit orders! The only difference is that if the range of a range order is not narrow enough, it’s highly possible that the conversion of tokens will be reverted once the price falls back to the range.

Thus, providing liquidity on v3, namely range orders, are essentially fee-earning reversible limit orders.

As price ranges follow the equation p(i) = 1.0001 ^ i, the range can be quite narrow and a range order can thus effectively serve as a limit order:

A range of 0.0016 is not THAT narrow but can certainly satisfy most limit order use cases!

⁸ As mentioned previously in note #4, there is a square root in the equation of the price and index, thus the numbers here are for explanation only.

Higher capital efficiency, LPs become arbitrageurs… as v3 has made tons of radical changes, I’d like to summarize my personal takes of the impacts of v3:

Anyway, personal opinions can be biased and seriously wrong. I’m merely throwing out a sprat to catch a whale. Having a different voice? Leave your comment down below!

That was kinda tough, isn’t it? Glad you make it through here 🥂

There are actually many more details and also a huge section of Oracle yet to be covered. However, since this article is more about features and targeting normal DeFi users, I’ll leave those to the next one; hope there is one :)

If you have any doubt or find any mistake, please feel free to reach out to me and I’d try to reply AFAP.

Stay tuned and in the meantime let’s wait and see how Uniswap v3 is again pioneering the innovation of DeFi!