diff options
author | Martin Zumsande <mzumsande@gmail.com> | 2024-06-20 16:14:22 -0400 |
---|---|---|
committer | Martin Zumsande <mzumsande@gmail.com> | 2024-07-11 13:06:22 -0400 |
commit | 55b6d7be68a6f6c3882588ffd5b9349d885ed953 (patch) | |
tree | 55aa3e2d62f6afb61d510e7255cbb2cf1fffd4ec /SECURITY.md | |
parent | e5a5497d9815ec3fc2f2d89e2dcf28eada408881 (diff) | |
download | bitcoin-55b6d7be68a6f6c3882588ffd5b9349d885ed953.tar.xz |
validation: Don't load a snapshot if it's not in the best header chain.
If the snapshot is not an ancestor of the most-work header (m_best_header),
syncing from that alternative chain should be prioritised.
Therefore don't accept loading a snapshot in this situation.
If that other chain turns out to be invalid, m_best_header
would be reset and loading the snapshot should be possible again.
Because of the work required to generate a conflicting headers chain,
this should only be possible under extreme circumstances, such as major forks.
Diffstat (limited to 'SECURITY.md')
0 files changed, 0 insertions, 0 deletions