AIKIDO-2026-347090

TL;DR

When a block fails contextual verification Zebra records its hash in an in-memory map and propagates that failure to any child whose parent is in the map. The entry is only removed by a fixed-size limit or a restart, never when the canonical block at that hash later commits successfully. A peer can get a poisoned block sharing a canonical block's header hash rejected first, so the stale entry then blocks the canonical successor and stalls the node at that height. The fix removes the hash from the map when the canonical block at that hash commits.