After #15946 starting a pruned bitcoin-qt with blockfilterindex=1 will give the error message

Error: A fatal internal error occurred, see debug.log for details

It would be more helpful if it gave what's in the debug.log which is

basic block filter index best block of the index goes beyond pruned data. Please disable the index or reindex (which will download the whole blockchain agai

Describe the enhancement

Less than 1 year new listed coins usually have better performance. It will be great if we have an option to filter only newly listed pairs with VolumnPairList.

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

It is hardly readable in dark mode right now if message is saved in receivers's mailbox.

Same issue exists for other info messages.

![Bildschirmfoto 2021-02-24 um 10 24 18](https://user-images.githubusercontent.com/170962/108979066-94dce100-768a-11eb-

Currently the all_burns in debug output of a stacks node is in value-sorted order:

Example: all_burns=[1,1,20000,20000,20000,20000]

This might be useful for determining median value. However, the median value is already indicated in the same output line. The requested functionality has the last 6 burns in chronological order so you can see which blocks you have missed:

e.g. all_burns=[200