diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-05-09 17:10:48 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-05-09 17:10:53 +0200 |
| commit | 08c1caf863656e8c4302f0ff392772f0055760e5 (patch) | |
| tree | b1e109fb95037574ce5fc07a167fd93b9d5290d1 /CONTRIBUTING.md | |
| parent | 612ba35ab140db917ac6ce6bfbcd0dd4c484f2df (diff) | |
| parent | a2f678d3552aaaaa8d6f480cf5f2fbc849f376c3 (diff) | |
Merge #13185: Bugfix: the end of a reorged chain is invalid when connect fails
a2f678d Bugfix: the end of a reorged chain is invalid when connect fails (Pieter Wuille)
Pull request description:
Introduced in 4e0eed88acdd41826868c151373068bfad18b84d
When an invalid block is found during a reorg, we know the last of the blocks in the was-to-be-connected chain is invalid, but not necessarily the first. As `vpIndexToConnect` is ordered in decreasing height, the end of the reorg is the front of the vector, and not the back.
This only affected the warning system.
Tree-SHA512: ddf749f8a78083811a5a17152723f545c1463768d09dc9832ec3682e803a3c106fb768de9fa91c03aa95e644d4e41361a7e4ee791940fd7d51cdefea90de31fc
Diffstat (limited to 'CONTRIBUTING.md')
0 files changed, 0 insertions, 0 deletions