Checkpoint Lockin: Difference between revisions
Jump to navigation
Jump to search
Created page with "Every once in a while, an old block hash is hardcoded into Bitcoin software. Different implementations choose different checkpoint locations. Checkpoints prevent various DOS a..." |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Every once in a while, an old block hash is hardcoded into Bitcoin software. Different implementations choose different checkpoint locations. Checkpoints prevent various | Every once in a while, an old block hash is hardcoded into Bitcoin software. Different implementations choose different checkpoint locations. | ||
Checkpoints prevent various DoS attacks from nodes flooding unusable chains and attacks involving isolating nodes and giving them fake chains, but it is primarily an optimization for the initial blockchain download. | |||
Satoshi announced the feature [https://bitcointalk.org/index.php?topic=437 here] and it was discussed to death [https://bitcointalk.org/index.php?topic=1647 here]. | |||
Some alt chains use different forms of checkpointing | Some alt chains use different forms of checkpointing, eg as an ongoing "central checkpointing pulse" that isn't updated only on software updates. | ||
[[Category:Technical]] | [[Category:Technical]] | ||
Latest revision as of 04:12, 8 June 2014
Every once in a while, an old block hash is hardcoded into Bitcoin software. Different implementations choose different checkpoint locations. Checkpoints prevent various DoS attacks from nodes flooding unusable chains and attacks involving isolating nodes and giving them fake chains, but it is primarily an optimization for the initial blockchain download. Satoshi announced the feature here and it was discussed to death here.
Some alt chains use different forms of checkpointing, eg as an ongoing "central checkpointing pulse" that isn't updated only on software updates.