Checkpoint at block 193,000 #1698

1. 
   gavinandresen commented at 8:07 PM on August 21, 2012: contributor

   Replace the checkpoint at 185,333 with block 193,000.

   (edited, was 195,000)

2. 
   gmaxwell commented at 8:30 PM on August 21, 2012: contributor

   This is way too close to current right now. How long are we planning on staying in RC? (Not that I'm aware of a fork this would conflict with, of course, but I like keeping the high ground of saying we've never released a checkpoint remotely near the tip)

3. 
   gavinandresen commented at 8:37 PM on August 21, 2012: contributor

   It's been a while (and quite a lot of code changes) since 0.6.3, so I assume we'll be in RC for at least two weeks.

   How far back is "long enough" for a checkpoint?

4. 
   jgarzik commented at 8:39 PM on August 21, 2012: contributor

   3 months?

5. 
   sipa commented at 8:52 PM on August 21, 2012: member

   Meh, I'd say 1 or 2 difficulty-adjust-cycles (2 or 4 weeks)?

6. 
   gmaxwell commented at 9:05 PM on August 21, 2012: contributor

   I think I'd claimed "8000 blocks" in some discussion before, I'm not seriously married to any specific value. I think it should be at least 1 difficulty cycle. 2 difficulty cycles sounds good. Sort of a bummer that we don't lock in the new difficulty when it's increasing like now, but it doesn't really matter.

7. 
   gavinandresen commented at 11:57 PM on August 21, 2012: contributor

   ok. I'll go ~2000 blocks (~2 weeks) back, and assuming we're in RC for 2 more weeks that'll be ~2 difficulty cycles at release. So block 193,000 or thereabouts...

8. Checkpoint at block 193,000 80cfc3a485
9. 
   BitcoinPullTester commented at 9:16 AM on August 22, 2012: none

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

10. 
    sipa commented at 12:01 PM on August 25, 2012: member

    ACK

11. gavinandresen merged this on Aug 25, 2012
12. gavinandresen closed this on Aug 25, 2012

    ---

13. KolbyML referenced this in commit 2037003b68 on Dec 5, 2020
14. DrahtBot locked this on Sep 8, 2021

Milestone
0.7.0