Checkpointing

[jubalix]

I would be glad if some one could explain check pointing for me or point me to a good resource

[1714760134]

1714760134

[1714760134]

1714760134

[1714760134]

1714760134

[1714760134]

1714760134

[1714760134]

1714760134

[D.H.]

Quote from StackExchange:

The checkpoints are hard coded into the standard client. The concept is, that the standard client will accept all transactions up to the checkpoint as valid and irreversible. If anyone tries to fork the blockchain starting from a block before the checkpoint, the client will not accept the fork. This makes those blocks "set in stone".

[jubalix]

Quote from StackExchange:

The checkpoints are hard coded into the standard client. The concept is, that the standard client will accept all transactions up to the checkpoint as valid and irreversible. If anyone tries to fork the blockchain starting from a block before the checkpoint, the client will not accept the fork. This makes those blocks "set in stone".

so it just because the majority everyone is using the same client with the checkpoint in it...?

any pointers on how the code works....*I guess should go and read the code*

(I think I just made a C/C++ joke)

[gmaxwell]

That SXC answer isn't really great.

This has been covered a number of times times in this forum, I suggest finding one of my posts. E.g. https://bitcointalk.org/index.php?topic=194078.msg2014204#msg2014204

In the reference client checkpoints will play less of a role in the future as better (but more complicated) solutions to the issues mention in that post are deployed.

[jubalix]

That SXC answer isn't really great.

This has been covered a number of times times in this forum, I suggest finding one of my posts. E.g. https://bitcointalk.org/index.php?topic=194078.msg2014204#msg2014204

In the reference client checkpoints will play less of a role in the future as better (but more complicated) solutions to the issues mention in that post are deployed.

thank you