Granny is Making the Order Books Thick with Komodo’s Liquidity Pool Multiplier

This article was first published on Komodo Platform | En

Decentralized exchanges (DEXs) have been looking for liquidity solutions for years. Komodo is innovating once again and presenting another unique solution a user-friendly liquidity multiplier that Grandma can use. We took the idea of One-Cancels-the-Other order (OCO) trading styles and merged it with our atomic swap trading process on AtomicDEX.  Now limit orders can be placed against any number of pairs at any number of price levels.

Moving into the initial beta release of AtomicDEX on October 29, the Komodo developer team has had one major goal in mind with polishing and refinement - Grandma-proof everything. With this in consideration, we have implemented an answer to one of the most difficult hurdles that DEXs face - low liquidity.

The Problem 

Swap pool DEXs, like Uniswap, have come up with a solution for attracting liquidity providers in order to overcome the chronic DEX issue of low volume. The pools they generate though are host to a wide range of critical issues. Rugpulls, vampire attacks, and “impermanent loss” due to the bonding curve all create high-risk citations for those participating in these automated market maker pools.

The Solution

While automated market maker pools like Uniswap plus others continue to refine their tech and evolve, Komodo’s AtomicDEX has put forth a solution to create massive amounts of liquidity potential for each liquidity provider or market maker that joins the order books. 

Oh, that’s right! We have decentralized order books. No more curves deciding the order size you get stuck with, or unaudited smart contracts controlling the code behind it. Users get complete control of the trades they place and pick straight from the order book for the trades they want.

So how does it work and how do we fill these order books?  

Well, with a little help ...

To keep reading, please go to the original article at:
Komodo Platform | En

Comments (No)

Leave a Reply