Timeline for What are checkpoints?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2017 at 10:21 | comment | added | user153465 | @ThePiachu Thanks for the answer. But, the question is, in a case where there's no checkpoint, why would client accept a chain shorter than what he already has? | |
| Jun 1, 2015 at 21:04 | comment | added | Pieter Wuille | They are chain-specific data, and have thus been moved to chainparams.cpp now. | |
| May 31, 2015 at 21:05 | comment | added | Aliakbar Ahmadi | @PieterWuille@ThePiachu: I didn't find any checkpoints hardcoded in main.cpp, checkpoints.h, checkpoints.cpp...Can you tell where the first checkpoint is placed? | |
| Sep 14, 2014 at 20:47 | comment | added | Pieter Wuille | We really plan to get rid of checkpoints, or at least significantly reduce their power. They don't actually add any security (if they would actually affect the chain, the system is already broken). | |
| Aug 22, 2012 at 7:02 | comment | added | ThePiachu | @DanielH I don't see why some automatic algorithm couldn't be implemented that would be choosing suitable checkpoints during each code update. I guess you can propose such a feature on the forum or the github project page. | |
| Aug 21, 2012 at 22:02 | comment | added | Daniel H | Would there be any way to make this behavior official? Something like "If the block was published to the network over a year ago, it is set in stone" which does not rely on the developers? This seem to be one of the few places where Bitcoin developers have a lot of authority, and it seems they generally work to keep that authority minimal. | |
| Nov 2, 2011 at 1:33 | vote | accept | nmat | ||
| Nov 2, 2011 at 1:12 | comment | added | ThePiachu | As far as I know, yes, but it is all in the hands of the developers. | |
| Nov 2, 2011 at 1:05 | comment | added | nmat | So a checkpoint is usually created everytime the client is updated? | |
| Oct 29, 2011 at 20:18 | history | answered | ThePiachu | CC BY-SA 3.0 |