3 ms·
Shouldn't be, you just need to write a wrapper for the exchange API with the interface defined in 'gryphon.lib.exchange.exchange_api_wrapper'. I'll add an artic
by reso 7y ago
Shouldn't be, you just need to write a wrapper for the exchange API with the interface defined in 'gryphon.lib.exchange.exchange_api_wrapper'. I'll add an article to the docs with more about that soon.
- westurner 7y agoWould CCXT be useful here? https://github.com/ccxt/ccxt https://github.com/ccxt/ccxt > The ccxt library currently supports the following 135 cryptocurrency exchange markets and trading APIs:
- reso 7y agoIt's possible CCXT could be used to easily wrap other exchanges into gryphon. I'm not familiar with the library so hard to guess if it would be a net win or not.
- thomasfromcdnjs 7y agoThanks! Which exchange is a good example? I find the directory structure just a confusing, why does each exchange-market get it's own file, wouldn't it be better for the exchange just to define some markets as hashes?
- reso 7y agoGemini is probably the best one, code-quality wise. Agreed, the way the trading-pair-to-exchange relationship works right now is imperfect. It's ripe for a good refactor.