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

For a university school project I will be making some edits to your documentation which will aim to make writing more technical

Please add edits if you would like :)

The -s flag is very useful, on smaller terminals, to limit output.

Would it be possible to add a feature: ability to limit the coin price accuracy to a fixed amount of decimal places (or better yet, total digits - useful for low value coins)

Example: The current bitcoin price shows "6282.25189496", but just "6282" would be fine...

Note: The screenshot on Readme.MD shows bitcoin price limi

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:/

What problem does this feture solve?

Currently, privatekey, xpriv, xpub cannot be initialized.

Describe what you've considered?

Code sample / Spec

    public init(_ base58: Base58Check) throws {
        guard let raw = Base58.decode(base58) else {
            throw AddressError.invalid
        }
        let checksum = raw.suffix(4)
        let pubKeyHash = raw.dropLast(4)

Instead of having 3 parameters to handle HSM vs non-HSM, signed vs unsigned and testnet vs mainnet, we should we have a single parameter (which picks among 4 profiles).
The 4 profiles would be:

• dev-without-hsm = no HSM, btc-testnet
• dev-with-hsm = HSM, unsigned, btc-testnet
• staging = HSM, signed, btc-testnet
• prod = HSM, signed, btc-mainnet

See https://github.com/square/subze

If you nadd new rule and give it some custom description like for example "Sell if BTC drops under xxxx$" it will be saved under this name properly.

But when you will go and edit this rule, default desciption will be automatycally given, and if you want to stay with your custom description, you must retype it again.

I'dont think this is the right behavior, instead custom desciption should st

ChainX桌面钱包在投票选举页面会展示各个节点logo。
在此收集各节点logo，不定期更新(每周一次)到桌面钱包到展示中，若节点不提供则会展示默认logo。
请需要展示logo的节点在本issue回复。

回复格式如下
节点名：
logo：上传大小为 80*80, 格式为 PNG 的 logo 图片, 也可以选择直接给出 logo 的 URL 地址。

ChainX desktop wallet will display a logo of each node in the staking page in the future version. The default logo will be used instead if some node doesn't provide one.

Please comment as follows:

node name

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!

The /detail page should have a header-level element showing the document hash that is being viewed.