Note that the regtests are currently flaky (failing about 20% of the time) . I'm still investigating this issue, and this simplification should make my debugging easier.

@bot build-win64 build-linux64

Update the circular dependency, update the files.md doc, remove the debugging log and fix the copyright year.

I don't think we can expect the avg chronik-client user to know what the interval value should be. Once we have to validate for "must be at least 20 seconds" ... might as well just fix it at a value that is working well empirically.

Also, we could mention the new file in files.md

Good point

There is a linter issue.
Also, we could mention the new file in files.md

In D14832#333157, @Fabien wrote:

What is the problem with the actual warning ? It feels more secure to me.

Add a release note

What is the problem with the actual warning ? It feels more secure to me.

I restarted the builds

This needs a release note, will rebase

In D14728#333005, @Fabien wrote:

wait for a new block to be found and observe the "New block found, refreshing alias prices" message in console

I think this message has been removed ?

The failure seems unrelated. That test attempts to cause a race in wallet loading, so it would make sense that it can sometimes fail, but it should be really really unlikely.

investigating the build failure

@bot build-asan

use uint32_t for random IP

Remove the unused peerid from the file

additional rationale: this is a dependency of a dependency of another PR touching code that is moved around and touched by other more important backports (in net_processing.cpp)

wait for a new block to be found and observe the "New block found, refreshing alias prices" message in console

I think this message has been removed ?