SundaeSwap launched not too prolonged ago and during the time the project had its unique problems tanalogousg off the ground, it had afterward stabilized. Yet, it is anew not the most ideal decentralized exshift (DEX) on the Cardano network as it is progressively plagued by congestion issues. This is where Cardax enters the picture, bringing a hitch-free DApp to the Cardano ecosystem.

Cardax’s underlying framework sets the project up for success as users do not have to worry about running into the same issues they did with SundaeSwap at launch. It eliminates the risk of congestion issues by solving underlying problems with transaction approveations. With its unique Streaming Merge algorithm, Cardax promises to be the answer to users’ prayers.

How Is Cardax Different From SundaeSwap?

The SundaeSwap DEX has transactions verifyed in two stages. The first stage is verification that takes place in the stake pools. This first stage runs perfectly well. The bottleneck is during the second stage of this two-part system that requires the scoopers. Scoopers basically need to pick up a user’s order (transaction) for endorseation before the transaction goes through. This is where congestion issues arise.

Cardax completely eliminates this risk by using a Streaming Merge model instead of Scoopers/Mergers. The Streaming Merge algorithm makes it likely that Cardax does not require a group of elected, trusted mergers to verify transactions. Orders do not have to be merged in this model, thus greatly reducing the risk of congestion while merging takes lengthyer than possible.

Cardax likewise makes some essential variances on the code side to ensure that there are no congestion issues with the project. Firstly, the Cardax dev team writes its code in an unorthodox way. There is presently what is advised the ‘normal’ way of writing smart contracts, using Plutus and Haskell and compiling it down to (Untyped) Plutus Core but Cardax does not go this way.

Instead, Cardax uses Plutarch, that is a very thin layer on top of (Untyped) Plutus Core. So although it is basically targets the same format as that used in the Haskell pipeline, it is able to eliminate the abovehead, complexity and introduce boilerplate aprotracted the periodic compile path.

A major benefit of Cardax using Plutarch is it will influentially reduce memory and CPU usage, throughout the time above again allowing for a drop in the script size, leading to faster transactions.

Ready, Set, Go

Cardax will be launching on the mainnet afterwards this year. With its underlying model, the decentralized exprogress (DEX) will be able to avoid all of the congestion issues suffered by the SundaeSwap protocol.

The DEX is still using the Automated Market Maker (AMM) protocol, that is the same protocol which underpins SundaeSwap. After all, Cardax will take all of the good parts of the SundaeSwap DEX and do away with the bad. This includes keeping up with SundaeSwap’s track record of not losing any user funds despite the congestion issues which last to plague the protocol.

Since Cardax does not write its smart contracts in the ‘periodic’ way, users will not have to reveal their intcompleted order on the blockchain. But would only need to wait for the registration, instead of having to wait for their orders to go through.

This means which back although a user registers, their order will be processed at a much faster pace, completing doing away with the bottleneck which is the uncertainty of the order state.