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 your environment

• Operating system: Manjaro
• Python V

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

The links to http. proto and annotations. proto no longer exist
Lower versions of GRPC may no longer work with existing code
I cannot access the public IP according to the documentation
Then I upgraded the GRPC to 1.36.0, the os-maven-plugin to 1.6.2, and the protobuf-maven-plugin to 0.6.1, everything was fine

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 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