I understand the problem but I don't think this is a good approach for several reasons:

• It uses low level ws state that should be handled by chronik-client, if anything made accessible
• We have a keepalive already, and websocket has pings which seems a better/cleaner option
• You have events when the app goes to/resumes from background. Why do you need to check the ws status at all ? Can't you just blindly resubscribe? Do you get twice the notifications if subscribed twice to the same things ?

@bot guix-linux guix-osx guix-win

Rename in tests

@bot build-ibd

@bot build-master build-chronik

Same as D18929 the test plan is not good

The test plan is not covering the change

Can this be automated ?

if that doesn't work we should consider another kind of captcha

@bot preview-e.cash

In D18867#430878, @bytesofman wrote:

• would also split out the ecash-lib changes here into a separate diff with version bump and land that before this lands

You need to update the CONTRIBUTING.md document accordingly

why did you skip the linter ?

NVM it's not the scripts but their tests which are worthless

Please don't do this until we backported all the security improvements first. They serve as tests for these features in the meantime