public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alistair Mann <al@pectw.net>
To: "Kenshiro []" <tensiam@hotmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
Date: Wed, 31 Jul 2019 14:59:33 +0100	[thread overview]
Message-ID: <28454621.Lge63Ifvux@dprfs-d5766> (raw)
In-Reply-To: <DB6PR10MB1832329BC8D151DC18F1E6CEA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM>

On Wednesday 31 Jul 2019 12:28:58 Kenshiro [] via bitcoin-dev wrote:

> I would like to propose that a "moving checkpoint" is added to the Bitcoin
> protocol. It's a very simple rule already implemented in NXT coin:
> 
> - A node will ignore any new block under nodeBlockHeight - N, so the
> blockchain becomes truly immutable after N blocks, even during a 51% attack
> which thanks to the moving checkpoint can't rewrite history older than the
> last N blocks.

How would a (potentially, state-sponsored) netsplit lasting longer than N be 
handled?  
-- 
Alistair Mann



  reply	other threads:[~2019-07-31 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 12:28 [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol Kenshiro []
2019-07-31 13:59 ` Alistair Mann [this message]
2019-07-31 14:40   ` Kenshiro []
2019-07-31 14:53     ` Kenshiro []
2019-07-31 23:28       ` Alistair Mann
2019-08-01 10:17         ` Kenshiro []
2019-08-02 12:19       ` Ethan Heilman
2019-08-02 13:08         ` Kenshiro []
2019-08-03  0:51           ` LORD HIS EXCELLENCY JAMES HRMH
2019-08-03 10:35             ` Kenshiro []

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=28454621.Lge63Ifvux@dprfs-d5766 \
    --to=al@pectw.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=tensiam@hotmail.com \
    /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