On: Gryphon: An open-source framework for algorithmic trading in cryptocurrency

[reso]

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 → reso]

Would CCXT be useful here? https://github.com/ccxt/ccxt

> The ccxt library currently supports the following 135 cryptocurrency exchange markets and trading APIs:

[reso → westurner]

It'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 → reso]

Thanks!

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 → thomasfromcdnjs]

Gemini 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.