Initial malfeasance proofs sync stuck

[poszu]

Description

A user reported the initial sync of malfeasance proofs hangs. Link to the discussion on Discord: https://discord.com/channels/623195163510046732/1275118578361958400.

Logs:
sm_node.log
spacemesh-log-7c8cef2b.txt.0.gz

Clues based on the initial log analysis:

• the syncer constantly receives updates about malfeasance proofs
• it is unable to download these proofs because the identity doesn't exist
• the initial malfeasance sync never reaches the end condition if nothingToDownload

A possible scenario that comes to mind, in which it could happen is:

1. The node finished ATX sync. It has all the ATXs known in the network at that time.
2. It started malfeasance proofs sync
3. A new contextually invalid initial ATX "BAD" is published on the network. The node doesn't receive it because it's not listening to gossip
4. It syncs the malfeasance proof about "BAD" but cannot process it because the identity that produced the "BAD" ATX is not known