From: "Kenshiro []" <tensiam@hotmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Add a moving checkpoint to the Bitcoin protocol
Date: Wed, 31 Jul 2019 12:28:58 +0000 [thread overview]
Message-ID: <DB6PR10MB1832329BC8D151DC18F1E6CEA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hi all,
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.
NXT coin has a N value of 720 blocks, like 12 hours of blocks.
To be more conservative, Bitcoin could have a N value of 144 blocks (like 24 hours). So users and exchanges could plan their operations with big amounts of BTC knowing that only after 24 hours a transaction is truly immutable.
Maybe a 51% attack never happens but if it does it would be nice to be 100% sure that history rewrite is limited to only 24 hours.
Regards,
[-- Attachment #2: Type: text/html, Size: 2598 bytes --]
next reply other threads:[~2019-07-31 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 12:28 Kenshiro [] [this message]
2019-07-31 13:59 ` Alistair Mann
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=DB6PR10MB1832329BC8D151DC18F1E6CEA6DF0@DB6PR10MB1832.EURPRD10.PROD.OUTLOOK.COM \
--to=tensiam@hotmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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