From: Luke Dashjr <luke@dashjr•org>
To: Peter Todd <pete@petertodd•org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
Date: Thu, 17 Nov 2016 03:06:01 +0000 [thread overview]
Message-ID: <201611170306.02406.luke@dashjr.org> (raw)
In-Reply-To: <20161116210100.GC5639@savin.petertodd.org>
On Wednesday, November 16, 2016 9:01:00 PM Peter Todd via bitcoin-dev wrote:
> So, conceptually, another way to deal with this is to hardcode a blockhash
> where we allow blocks in a chain ending with that blockhash to _not_ follow
> BIP65, up until that blockhash, and any blockchain without that blockhash
> must respect BIP65 for all blocks in the chain.
>
> This is a softfork: we've only added rules that made otherwise valid chains
> invalid, and at the same time we are still accepting large reorgs (albeit
> under stricter rules than before).
>
> I'd suggest we call this a exemption hash - we've exempted a particular
> blockchains from a soft-forked rule that we would otherwise enforce.
While this is technically a softfork, I think it may behave somewhat like a
hardfork if we're not careful. Particularly, is the chain up to the block
immediately before the checkpoint itself valid on its own, or does it simply
become retroactively valid when it hits that checkpoint?
P.S. Your PGP signature is invalid?
next prev parent reply other threads:[~2016-11-17 3:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:17 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
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 [this message]
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=201611170306.02406.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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