public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
Date: Wed, 16 Nov 2016 15:38:21 +0100	[thread overview]
Message-ID: <1797370.j3ssDbnHdc@strawberry> (raw)
In-Reply-To: <CEDAD65E-512A-43CA-9BD6-56F7D9E6897C@voskuil.org>

Here is my thinking.

The BIP process is about changes to a living project which is the bitcoin 
prptocol.
This specific BIP got accepted and we know in the blockchain that
this event (the acceptance) is recorded.
Before a certain block the rules were one way, after they were changed.

I have no problem with changing the *code* to be less complex because it 
already knows the past. A checkpoint is the same, it is the registeration of 
a past event.
This makes software less complex and still capable of checking the entire 
blockchain from genesis.

I don’t see any harm in this change. I see prudent software engineering 
practices.


On Monday, 14 November 2016 10:47:35 CET Eric Voskuil via bitcoin-dev wrote:
> NACK
> 
> Horrible precedent (hardcoding rule changes based on the assumption that
> large forks indicate a catastrophic failure), extremely poor process
> (already shipped, now the discussion), and not even a material
> performance optimization (the checks are avoidable once activated until a
> sufficiently deep reorg deactivates them).


-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


      parent reply	other threads:[~2016-11-16 14:38 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
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 [this message]

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=1797370.j3ssDbnHdc@strawberry \
    --to=tomz@freedommail.ch \
    --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