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.
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)
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.
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.
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
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.
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.
* 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.
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"
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.