THORChain are please to unveil the @gauntletnetwork analysis of the liquidity-sensitive fee (slip-based) model of THORChain's continuous liquidity pools.

This work was commissioned to validate some assumptions around the model and to get a neutral third-party to challenge it.
Gauntlet set a scenario where liquidity would choose between an XYK exchange (uniswap) and a CLP exchange (THORChain).

Three agents (LP, demand trader and arb trader) each with competing priorities interacted.

A "secondary market" provided the price paths. Image
LPs monitored both exchanges and would move their funds where the ROI is highest.

This behaviour has already been seen today between Uniswap and Sushiswap (multiple times liquidity sloshed between both) Image
Arbitrage agents simply pick the best execution, the size of which depends on the depth of the market, plus the fee they incur (30 BP XYK vs Variable CLP).

Noting that under low demand, CLP fees go to zero, but in high demand, CLP fees can be far higher than 30 BP. Image
Finally the Demand Trader chooses an exchange where they get the best execution.

This is purely a function of the depth of the market for CLP, the deeper, the less fee. Image
The key takeaways
* Slip-based fee improves returns for LPs in almost all market conditions
* IL is greatly reduced for CLP, and there are some price paths where LPs are in profit, despite IL.
* Slip-based fee can result in less volume, since demand traders may go elsewhere Image
This conclusion is consistent with THORChain's philosophy since the start:

"optimise for liquidity first, everything else comes later"

By driving maximal ROI for LPs, pools can become deep, which drives up volume, but reduces fees for traders.
This is serious validation for the liquidity-sensitive fee model, despite industry criticism since the start.

THORChain believe is it the correct approach and will continue to build.

Full report:
github.com/thorchain/Reso… Image

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with THORChain ⚡️(ᚱ)

THORChain ⚡️(ᚱ) Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @thorchain_org

9 Nov
THORChain is not built to skirt rules, it's built to operate in a way that the rules are no longer applicable.

A centralised exchange has to follow KYC/AML because they hold user funds and have a legal relationship with their users.

Instead, THORChain is a protocol. /n
If you hold a Bitcoin UTXO that you can spend, you sign a tx and broadcast it. Individual Bitcoin miners can choose to not to process it, but they cannot stop it being eventually processed.

Bitcoin users do not have a relationship with miners, and miners don't hold funds.
If you sign a tx spending Bitcoin into THORChain, it will get processed by miners, then witnessed by THORNodes into the state machine. Any THORNode can choose not to witness it, but they will get unavoidably slashed.

So it will eventually end up in the state machine.
Read 11 tweets
9 Nov
Legacy markets are centralised against a custodial hub, so speed counts to favour those who can scalp the fastest.

However this is irrelevant to a global decentralised market.

Thread on why pursuing speed/latency is a fool's errand for a DEX.

/n
An asset's price is simply net buyers meeting net sellers, and the balance of the two depends purely on information about that asset.

If new information about an asset is found, then the price will change in response to that information.
How fast the price changes depends purely on how fast information about that asset can propagate across the market participants.

The "real" price of an asset does not change every 5ms. For a 24/7 global market with no centralised hub, price changes should be much slower.
Read 13 tweets
10 Aug
Why is THORChain called THORChain?

* Because the team recognised early that memetic growth of the network is an important driver to gaining widespread adoption. *

Simply, because it's a meme.

/thread
Decentralised crypto money networks are held together by the people who make it.

The more they can identify with each other, share their ideas, spread their memes, the stronger the network is.

Norse mythology is as old as time itself, arguably one of the strongest memes ever
Norse Mythology likely descends from the Old Testament (Book of Genesis) containing similar ideas (even a version of Adam & Eve - Aska & Embla, with similar fates).

It's a rich brand, woven in and out of culture for thousands of years, including recent comics and movies.
Read 8 tweets
3 Aug
Many new projects claiming "cross-chain".

To cut thru the noise, ask these questions:

1) Are the assets wrapped or pegged?

If they are wrapped/pegged, the project is out-sourcing security to another protocol.

THORChain secures native assets.
2) Is the security model scalable?

If the security model is "proof of stake" but does not couple the security of vaulted assets with their value, then the protocol can become unsafe.

THORChain uses an Incentive Pendulum - which is scalable and autonomous.
3) Does the protocol use Atomic Swaps?

Atomic Swaps are a deal-breaker for incentivised liquidity pools, since Atomic Swaps cannot be pooled or incentivised, and is vulnerable to the "American Call Option"

THORChain uses always-on pooled liquidity.
Read 9 tweets
29 Jun
Ethereum Testnet Update

Latest update using a method suggested by @0xEther

Thread on how it works.

rinkeby.etherscan.io/address/0x1069…
Step 1)

Call `deposit()` with 0.1 ETH, and memo:

SWAP:ETH.TKN-0x6D052e01B0C60d8c1aBB6C936651f9bf55633CD4:0x<yourAddress>

Remember - you are trying to pass transaction intent through to THORChain.
The contract will receive the deposit and emit an event once confirmed on-chain.

This only happens once it is confirmed. Every THORNode is hooked to an Ethereum node and will receive the event logs.
Read 10 tweets
14 Jun
THORChain's Bifröst protocol today is a substantial different design from the original concept and other bridges.

The Bifröst does not seek to prove an event observed and reported actually did occur via validation.

Instead THORChain only seeks "observation consensus"
Nodes are connected to a plurality of chains. Everytime they see a transaction concerning a THORChain vault, the bundle up their observation into a witness transaction.

A client sits between each chain-node and the Observer, which abstracts away chain nuances
The witness transaction object looks like the following, where, no matter the originating chain, all witness transactions are the same.
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!