Chain height out of sync due to BitcoinJ/Bitcoind ping timeout

[ghost]

Description

User's offer was not able to be taken because their chain height was out of sync.
However, user was unaware the problem existed.

Version

All current versions.

Steps to reproduce

Unknown

Expected behaviour

User should be made aware of the issue.

Actual behaviour

No indication shown, or very little indication other than chain height.
You do get notified if actively trying to make or take an offer (#4764), but if a peer fails to take your offer it is only logged and the user is unaware of it.

WARN  b.c.b.s.WalletsSetup: Our chain height: 752462 is out of sync with peer nodes chain height: 752540 
INFO  b.c.o.OpenOfferManager: We got a handleOfferAvailabilityRequest but our chain is not synced. 

Additional info

Logs revealed a repetitive problem of bitcoinj reporting "Too many pending pings, disconnecting" (once every 2 minutes).
The bitcoind node was connected via IP on local area network.
It is unclear if bitcoind has some anti-spam mechanism for ignoring too frequent pings. But this is largely a connection issue between BitcoinJ and bitcoind of which we are out of the loop.

Suggested solution is to alert the user via the status indicator in the footer bar if the chain height falls out of sync.

I'll work on this.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.