Back to Ccxt

Awesome CCXT

wiki/Awesome.md

4.5.5217.2 KB
Original Source

Awesome CCXT

Suggestions and contributions are always welcome! Make sure to read the contribution guidelines

Trading bots

Signals

Trading toolkits

Trading terminals

  • Kupi-terminal - Customized, extendable trading platform based on js, vue, react, express (rest api), mongo. Can: plot OHLCV, buy/sell, show balances, history balances, orders, trades, my orders, my trades.
  • ccxt-trading-cp - Trading terminal in console: plot OHLCV, find arbitrage signals, buy/sell, show balances.
  • Auto-Trade-Crypto-Bot - Crypto trading #bot in #python with #telegram.
  • ccxt-exchange-template - python

Analytics platforms

API

AI

  • Taurus - A cryptocurrency trading platform using deep reinforcement learning.

Utils

  • bitcoin-chart-cli by madnight – a command-line console util that draws Bitcoin, Ether, Litecoin and many altcoin charts right in the terminal!
  • node-red-contrib-ccxt - Node-red integration.
  • freqcache - A environment to control egress and ingress data from ccxt fronted trading bots for security and scalability
  • candlestick-convert - [Object,Object] => [[],[]]
  • crypto-exporter - An exporter capable of connecting to multiple exchanges and getting account balances and exchange rates
  • ccxtreplay - collect data from ccxt exchanges and replay it for backtesting

Languages

Javascript examples

Python examples

PHP examples

Articles

Videos

Other

  • Projects based on ccxt – A list of hundreds of ccxt-based projects by developers from all over the world!
  • LOC-Extension – a LibreOffice extension which embeds ccxt to provide cryptocurrency price lookup in your spreadsheets.
  • exchange-connector - Exchange connector over ccxt and kafka
  • ccew - has the same scheme as ccxt, but provide data by websocket

Contributing

Please ensure your pull request adheres to the following:

  • Search previous suggestions before making a new one to ensure yours is not a duplicate.
  • Make an individual pull request for each suggestion.
  • Use the following format: NAME - DESCRIPTION.
  • Keep descriptions simple.
  • New categories, or improvements to the existing ones are welcome.
  • End all descriptions with a period.
  • Try to ensure your pull requests only have one commit if possible. You can squash your commits into one before submitting.
  • Make your pull request titles and descriptions as detailed as possible. Explain why an asset or resources deserves to be added to the list.
  • Make sure your additions are in alphabetical order. This includes the headers and items themselves.
  • Ensure that assets you submit are of high quality, documented well, and are recently maintained. It also helps if they're popular so I can research them before adding them to the list.
  • This is not meant to be used as a list to advertise your own assets. Free or open-source assets should be prioritized over paid assets if they are of similar quality and feature sets.

Special thanks

This was forked from /sindresorhus/awesone. Special thanks to for starting this list and those that contributed to it contributors, this wouldn't be possible without you!