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

Clients that are built around the API need some additional information to work effectively. This is the following:

1. Peer list API: show more information about connected peers including the block height / cumulative difficulty of the peer. Basically, so the API provides at least as much information as the server TUI does.

2. Status information: Similarly, the minimum amount of info the stat

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

I can't find doc on /dial_peers endpoint in https://tendermint.com/rpc/

Problem

Currently when a user receives a PN, we show a very generic message (no indication of sender, body, etc). This will change in the future (e.g. with status-im/status-react#7043), so it would be good to be more explicit about the fact that we are showing a generic PN message due to the db being locked. Also, since we may receive PNs from users we've since removed

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.

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!