I spent too long to figure out I was putting mainnet addresses to regtest node, errors weren't helpful at getaddressinfo and validateaddress.

Seems like a good first issue to augment the error messages when prefix/hrp don't match current network.

Describe your environment

• Operating system: Linux
• Python Version: 3.8.6
• CCXT version:1.40.99
• Freqtrade Version: 2021.1

Describe the enhancement

Add ping support to the rest_client.py script.

I'm using the rest_client.py script to monitor my freqtrade bot using a custom shell+python script, and it looks like I cannot use the ping command to verify that

Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

I just recognized in the German translation that the truncation of the new trigger price feature is not configured properly. Also the provided text is not properly translated (I'll take care of this on Transifex myself).

Currently Clarity's stx-transfer? function doesn't let you include a memo