#16083 has been abandoned, so it would be a good first issue to take the branch (bitcoin/bitcoin#16083 (comment)) and submit it as a new pull request.

Useful skills:

Understanding of undo data, the RPC interface and the functional tests.

Want to work on this issue?

The purpose of the good first issue label is to highlight which issues ar

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

What's wrong

@dvf it would be great if you could fix Step 6: Setting up Flask gist, it affects the workflow at the Learn Blockchains by Building One article. Also there is no way to mention someone at the gist comments, so I created this issue instead.

In the past the node and the wallet were in the same repo. When the wallet was extracted into a separate repo, integration tests were moved to - https://github.com/mimblewimble/grin-wallet/tree/master/integration
It would be beneficial to provide a simple way to run integration suits as part of node tests too.
There are several possible options (there are some other for sure):

• Move part of th

To be done on lbrytech repo probably.
The wallet is currently configured as defined originally in ElectrumX, there are some docs for it already in there.

Keep in mind that we added new configuration keys and should clean up the unused ones at some point, so we need something easy

Background

The binaries are built with most of the build flags already set, but when building from source you must specify which tags are desired. This is an important step to building a usable binary from source.

These flags should be listed in the docs, with what their use is for the entire system, and whether or not excluding it would break the normal function of the system.

A sect

When given a wrong argument, some daemon commands fail with "unknown command" error, instead of a meaningful error message.

Examples of useless error messages:

hard_fork_info abc
unknown command: hard_fork_info abc
Monero 'Carbon Chamaeleon' (v0.15.0.0-57854a3e2)
Commands:
  ...

in_peers abcd
unknown command: in_peers abcd
Monero 'Carbon Chamaeleon' (v0.15.0.0-57854a3e2)
Comm

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.

Step 1: Have you search for this issue before posting it?

yes

If you have discovered a bug in the bot, please search our issue tracker.
If it hasn't been reported, please create a new issue.

Step 2: Describe your environment

• platform: Docker - latest build(Digest:sha256:3e8fe20bf6aaad9095e1ba0924ce2af3368cc55d1fe41ee

A user asked me on slack if estimatefee returns BTC per Byte or BTC per Kilobyte... honestly I don't know and it's a bit hard to tell. I compared mainnet full nodes bcoin vs Bitcoin Core and observed a wild divergence (outputs below).

From Bitcoin Core help:

Estimates the approximate fee per kilobyte needed for a transaction to begin
confirmation within conf_target blocks if possible

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!