There are many reports of the test being flaky: bitcoin/bitcoin#20672 (comment)

Thus, it should be made more robust, as described in bitcoin/bitcoin#20538 (comment)

Useful skills:

• Background in our functional test suite (python3)
• Background in zmq

Want to work on this issue?

For guidance on

When calling /balance command in Telegram bot:
BTCST:
Available: 0.00486000
Balance: 0.00486000
Pending: 0.00000000
Est. BTC: 2.47001423

Seems like wrong formula used: 2.47001423/0.00486 = 508,2333806584
But actual price is 0,0019676 what is 0.00486/2.47001423

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

Description

The navigation would look cleaner and more up to date if we clean out the small lines in between the elements.
I really don't think we need them.

Version

1.5.4

![Frame 4](https://user-images.githubusercontent.com/807505/105564920-44244200-5cf2-11eb-88

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