While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

When I change Demomode=true and run docker-compose up it does exit with code 1.

When looking at the logs it shows this

blackbird_1 | Blackbird is running... (pid 7) blackbird_1 | compose.cli.verbose_proxy.proxy_callable: docker wait <- ('7166aee47fa032ac92beca8ecd15d8a624b3526c5ce5eb4bcb70ffb4dbf81206') compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('7166aee47fa032ac9

The title pretty much says it all.
I start the trader up and it runs normally. It then makes a purchase successfully.

Followed by sell orders. Checking Binance.com, these sell orders are also successful.
![screen shot 2018-01-30 at 10 48 32 pm](https:/

Exchange Details ✏️

• Name of exchange: dex.blue
• Exchange URL: dex.blue
• Link to API docs: https://docs.dex.blue/
• Type of exchange: [ ] Centralized [X] Decentralized
• Requester details: Are you affiliated with the exchange? [ x] yes [ ] no
  • If yes, what is your role? Market Maker

Rationale / impact ✏️

(Describe your rationale for building this exchan

close and add doc in 0.4 ?

Originally posted by @GuillaumeDSM in Drakkar-Software/OctoBot#156 (comment)

Hi and thanks for CCXT-REST!

I am having trouble understanding what advantage CCXT-REST has over CCXT?

I understood that CCXT already provided the unified API to interact with the exchanges.

Would you be able to explain how one might have advantage using CCXT-REST?

Thank you!

I have a bad english, so if someone can help and find mistakes. that would be awesome.

The documentation for this project is great, but I'm still a little confused on what to put in the CODE and ISSUER variables of each GROUPS.ASSETS segments.

My best guess was to go to the Stellar X market, choose an asset like this one, and then (using that as an example), set CODE="USD" and `ISSU

Enable SMTP to send emails to configured recipients for two events:

• Entered a position
• Exited a position

Having a “push” style notification would be helpful to avoid having to constantly look at the logs.