Skip to content

Use best header chain timestamps to detect partitioning#6256

Merged
laanwj merged 1 commit intobitcoin:masterfrom
gavinandresen:PartitionCheck_Issue6251
Jun 12, 2015
Merged

Use best header chain timestamps to detect partitioning#6256
laanwj merged 1 commit intobitcoin:masterfrom
gavinandresen:PartitionCheck_Issue6251

Conversation

@gavinandresen
Copy link
Contributor

The partition checking code was using chainActive timestamps
to detect partitioning; with headers-first syncing, it should use
(and with this pull request, does use) pIndexBestHeader timestamps.

Fixes issue #6251

The partition checking code was using chainActive timestamps
to detect partitioning; with headers-first syncing, it should use
(and with this pull request, does use) pIndexBestHeader timestamps.

Fixes issue bitcoin#6251
@laanwj
Copy link
Member

laanwj commented Jun 12, 2015

utACK

@laanwj laanwj merged commit 65b9454 into bitcoin:master Jun 12, 2015
laanwj added a commit that referenced this pull request Jun 12, 2015
65b9454 Use best header chain timestamps to detect partitioning (Gavin Andresen)
gavinandresen added a commit that referenced this pull request Jun 15, 2015
The partition checking code was using chainActive timestamps
to detect partitioning; with headers-first syncing, it should use
(and with this pull request, does use) pIndexBestHeader timestamps.

Fixes issue #6251

Github-Pull: #6256
Rebased-From: 65b9454
@laanwj
Copy link
Member

laanwj commented Jun 15, 2015

Cherry-picked to 0.11 as fce474c

laanwj added a commit that referenced this pull request Jun 21, 2015
…6251)"

Re-enable partition check, it should be safe again after #6256.

This reverts commit 3eada74.
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants