Thank you for asking! There are a significant number of advantages over CCXT. I will list some of them here.

1. CCXT is buggy, complicated, and impractical to use in production environments.
2. CCXT is a library. This means there is still a heavy development burden placed on the application developers. When there is a breaking update, the library needs to be updated and redeployed to all of the affected servers.
3. The CCXT library is slow to update. This leaves developers hanging out to dry when a drastic or sudden change is made by one of the exchanges.
4. Using CCXT still means you need to scale a server farm that is capable of handing the requests that are required for your users. This is a complex problem on it’s own that requires a significant amount of resources.
5. Using CCXT means you still need to develop the trading logic, handling of data, and other complex flows.

Building an application on Shrimpy does not have these problems. It’s easy to use, built for production applications, doesn’t require frequent code updates, can be used for mobile or web applications, requires no scaling on the developers end, and handles the complex trading logic for the user.

These are just a few of the advantages, but the list of advantages will continue growing!

Please let me know if you have any other questions!