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

It's not clear from the current docs whether you buy or sell stock for a company that Trump complains about.

You should state your bias about your expectation about Trump's tweets effect on stock prices. (Note that Nordstorm stock went up after Trump complained about them).

我们会在这个 Issue 中持续 refer 比较典型的 Issue，也希望您能持续通过 issue 来与我们讨论各种问题，这样都可以为其他人提供参考，也避免我们重复回答同样的问题。

• 如果您刚开始接触 RQAlpha 请先阅读文档 http://rqalpha.io
• 如果您在使用过程中遇到了问题，请先查看下文罗列的FAQ是否可以解决您的问题，或者您也可以利用 Issue 的搜索和过滤功能来试图找到类似问题的讨论。
• 如果以上方式仍然没有解决您的问题的，请您 创建Issue, 按照创建时给出的规范模板来描述您的问题
• 善用截图功能，github 上是可以在 issue 的提问和回复中直接 ctrl + v 来上传图片的，很方便。

RQAlpha 2.0.0

I would love to add some new exchanges in there for you (and me) and would be happy to do so with just a little guidance as to which objects you're using for it without me doing a full code dig.

Assuming this is easily extensible. If not, I guess that would be my feature request... lol. Extensible exchange objects with documentation.

It look like some currencies have more precision in the mouseover display on the plot than others. For example, EOS shows many digits past the decimal while ETH only shows two. Adding a few more digits would make interpreting the charts much easier. The left plot shows the rounding I'm describing and the right shows the higher precision that EOS displays.

![rounding](https://user-images.githubu

Hi,

I the documentation here it says: "Support for accessing multiple exchanges per algorithm, which opens the door to cross-exchange arbitrage opportunities."

Does catalyst really support multiple exchanges using the same algorithm? If so - how this can be done? (no documentation for it)

Thanks!

Is your feature request related to a problem? Please describe.
Paper https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3010414 describes the algorithm to be implemented.

See api documentation at https://www.bitmex.com/app/restAPI

• feature request (1): get and plot market data for symbol XBT, (bitcoin)
• feature request (2): get account data and plot on dashboard, (account balance, open positions, etc.)
• feature request (3): create, modify and cancel limit orders

As a 3rd party developer there is a reasonable expectation of accuracy when reading the published api documentation and additional tools from same org keep valid URL’s and service references.

Expected:

• this repo and readme linked via Alpaca docs would be valid

Actual:

• GDAX still referenced working and dead links to this service (the coinbase pro rebrand > 1year ago)

Hi,

As per title, it would be a nice improvement to add the tickets reference and links to the release notes and in the change log.

Skill Set Challenge!

Hudson & Thames has provided the following skillset challenge to allow potential researchers to gauge if they have the required skil

I'd love to use TradingVue in a Nuxt Universal App. I tried getting the simple example to work in Nuxt 2.6.2, but just the import declaration causes the ReferenceError: window is not defined.

I created a simple example for demonstration / debugging purposes:
nuxt-trading-vue

Just:
$ npx create-nuxt-app nuxt-trading-vue
$ yarn add trading-v

Hi people,
Good night, I was developing an bot application using this API (python-bittrex v 1.1) and when my bot will go buy the currency with the method buy_limit(market, quantity, rate) it can't buy the currency, and return of this call with the method buy_limit() it's:
{'success': False, 'message': 'INVALID_MARKET', 'result': None}.

I just pass the name of market with less "BTC-",