Some suggestions for improvements, or at least for discussion between major releases:

• Read suspicious hosts (and ASNs) from a file instead of hardcoding
• Determinism could be improved (this is useful for cross-checking)
• [A max of 2 se

Send / Receive messages using local client XMLRPC

so others know how to add new ones if they need to

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

The documentation website needs a major overhaul. Many of the examples and sample code are not up to date with the latest release.

This is definitely affecting users, see #1786 for example.

At traders chat, received messages are getting wrong time stamps. My messages are ok, but the other party ones are not. It might be due to his/her local time or wrong time set. Anyway, the chat is ordering the messages in the wrong order due to that.

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

Adding an option to find the optimal MA value for a given timeperiod within a timeframe in indicator hyperspace, instead of fixed values.