Description
Describe the bug
When attempting to start my node with warp sync enabled, it gets stuck in a loop of banning peers due to "Bad warp proof" and fails to make any progress for an extended period (1–2 hours). The logs show repeated messages like the following:
2025-06-26 14:51:56 Report 12D3KooWG1L4n2tyLxuJ71QhEKQXt1axaYc1dTGXEMv29pgg6SrS: -536870912 to -2012863199. Reason: Bad warp proof. Banned, disconnecting.
2025-06-26 14:51:57 Report 12D3KooWATgqGr2QwYBDjEiwVtVff9u1AdkY9nG6uu2ZQnhk8eae: -536870912 to -2039476556. Reason: Bad warp proof. Banned, disconnecting.
2025-06-26 14:51:59 Report 12D3KooWLe8CkuK1CeEWpBGDcrfineGUmcXmYTJug53exoV1gjCT: -536870912 to -1717011703. Reason: Bad warp proof. Banned, disconnecting.
2025-06-26 14:52:00 ⏩ Warping, Downloading finality proofs, 0.00 Mib (29 peers), best: #0 (0x2f05…6c03), finalized #0 (0x2f05…6c03), ⬇ 34.6kiB/s ⬆ 3.0kiB/s
2025-06-26 14:52:05 ⏩ Warping, Downloading finality proofs, 0.00 Mib (33 peers), best: #0 (0x2f05…6c03), finalized #0 (0x2f05…6c03), ⬇ 33.0kiB/s ⬆ 2.9kiB/s
2025-06-26 14:52:10 ⏩ Warping, Downloading finality proofs, 0.00 Mib (32 peers), best: #0 (0x2f05…6c03), finalized #0 (0x2f05…6c03), ⬇ 14.4kiB/s ⬆ 4.1kiB/s
This state persists indefinitely, and the node does not progress past block #0.
Actual Behavior:
Node remains at block #0 and does not finalize any new blocks.
Peers are repeatedly banned for "Bad warp proof."
No significant data is downloaded.
To Reproduce
Start a new node with warp sync enabled (e.g., using --sync=warp).
Wait for the node to connect to peers.
Observe logs and sync status.
Expected behavior
The node should make forward progress during warp sync, even if some peers provide bad data. It should eventually connect to valid peers and finalize blocks.
Screenshots
No response
Environment
MacOS arm, Linux Ubuntu 24.04.2 LTS x86, multiple versions of subtensor, the last one was v3.1.4
Additional context
Let me know if any logs or debug flags would help—happy to provide more data.