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

我们会在这个 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.

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.

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