Skip to content

Checkpoint at first 25-btc-reward block (210,000) #2087

Merged
merged 1 commit into from Dec 13, 2012

5 participants

@gavinandresen
Bitcoin member

Adds a new checkpoint at block 210,000.

@BitcoinPullTester

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/5d32d3f8cd14f259cea92dfb5df07ead33b4bfb7 for binaries and test log.

@jgarzik
Bitcoin member
jgarzik commented Dec 10, 2012

ACK

@gmaxwell

ACK— I'm glad the timestamps allowed setting one right at 210000. It shouldn't be merged until it is burred a little more.

@jgarzik
Bitcoin member
jgarzik commented Dec 10, 2012

I don't see any harm in merging to HEAD (not 0.7.2) now, as 0.8 is still a long way off.

@gmaxwell

Oh is this just for 0.8? Yea— I don't mind merging something early for a release thats a ways off.

@sipa
Bitcoin member
sipa commented Dec 10, 2012

ACK

@gavinandresen
Bitcoin member

I created a 0.7.2 branch, with:

0.7.2rc2
a commit so gitian-descriptors point to github instead of gitorious
this commit, to checkpoint @ 210,000

I'm in the middle of sanity testing it by doing a complete blockchain re-download. If it is sane, and when y'all are comfortable the checkpoint is buried deep enough (I think we said "past one difficulty adjustment", which was 14 blocks ago at 211,680), I want to tag and spin a 0.7.2 final release (I don't think we need a rc3 for those two trivial commits).

@gmaxwell

"One difficulty adjustment" being 2016 blocks, e.g. 212016, which should be in a couple days.

@sipa
Bitcoin member
sipa commented Dec 13, 2012

Which would be now.

@sipa sipa merged commit da8c5c9 into bitcoin:master Dec 13, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.