public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tier Nolan <tier.nolan@gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
Date: Wed, 16 Nov 2016 14:18:44 +0000	[thread overview]
Message-ID: <CAE-z3OXdiyS_5HEFu1VLG1DH_K1QUBTSy49nXh1M4tcuoi6D_w@mail.gmail.com> (raw)
In-Reply-To: <A98BB7F2-7AE2-4D84-9F38-7E7E9D5D3210@voskuil.org>

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

On Wed, Nov 16, 2016 at 1:58 PM, Eric Voskuil via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Are checkpoints good now? Are hard forks okay now?
>

I think that at least one checkpoint should be included.  The assumption is
that no 50k re-orgs will happen, and that assumption should be directly
checked.

Checkpointing only needs to happen during the headers-first part of the
download.

If the block at the BIP-65 height is checkpointed, then the comparisons for
the other ones are automatically correct.  They are unnecessary, since the
checkpoint protects all earlier block, but many people would like to be
able to verify the legacy chain.

This makes the change a soft-fork rather than a hard fork.  Chains that
don't go through the checkpoint are rejected but no new chains are allowed.

[-- Attachment #2: Type: text/html, Size: 1243 bytes --]

  reply	other threads:[~2016-11-16 14:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 18:17 [bitcoin-dev] [BIP Proposal] Buried Deployments Suhas Daftuar
2016-11-14 18:47 ` Eric Voskuil
2016-11-15 14:42   ` Suhas Daftuar
2016-11-15 17:45   ` Btc Drak
2016-11-15 22:42     ` Eric Voskuil
2016-11-16 13:29       ` Jameson Lopp
2016-11-16 13:58         ` Eric Voskuil
2016-11-16 14:18           ` Tier Nolan [this message]
2016-11-16 14:32             ` Alex Morcos
2016-11-16 21:01               ` Peter Todd
2016-11-16 22:21                 ` Eric Voskuil
2016-11-17  3:06                 ` Luke Dashjr
2016-11-16 14:18           ` Thomas Kerin
2016-11-16 23:58             ` Jorge Timón
2016-11-17  0:00               ` Eric Voskuil
2016-11-17  1:24                 ` Alex Morcos
2016-11-17  1:41                   ` Eric Voskuil
2016-11-17  0:13             ` Eric Voskuil
2016-11-16 23:48           ` Jorge Timón
2016-11-17  1:50           ` Pieter Wuille
2016-11-17  2:16             ` Eric Voskuil
2016-11-17  2:47               ` Pieter Wuille
2016-11-17 10:10                 ` Eric Voskuil
2016-11-16 14:38   ` Tom Zander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAE-z3OXdiyS_5HEFu1VLG1DH_K1QUBTSy49nXh1M4tcuoi6D_w@mail.gmail.com \
    --to=tier.nolan@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox