chains coordinator: re-validate anchor blocks against pox bitvector on boot-up?

[jcnelson]

If for some reason the Stacks node is stopped and restarted after being in a state where it had processed one or more reward cycles without anchor blocks, but for which anchor blocks existed, it won't ever invalidate the old sortitions. I think what needs to happen is that the node should verify on boot-up that the PoX bitvector at the sortition tip is consistent with the last anchor block processed -- if there's a false where there should be a true, then the sortitions should be invalidated directly.

[stale[bot]]

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.

[stale[bot]]

This issue has been automatically closed. Please reopen if needed.