This can now happen if: - we have a pruned db - we have not connected to the monero network for a while - we connect to a node - that node asks us for history - we only have a pruned version of the most recent common block In that case, it's better to not reply but keep the connection alive, so we can sync off it.pull/6543/head
parent
309211fd6a
commit
44e3782b4d
Loading…
Reference in new issue