public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bryan Bishop <kanzure@gmail.com>
To: Adam Back <adam@cypherspace.org>,
	Bryan Bishop <kanzure@gmail.com>,
	 Bryan Bishop <bryan@ledgerx.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	libbitcoin@lists.dyne.org
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
Date: Sat, 14 Feb 2015 13:29:16 -0600	[thread overview]
Message-ID: <CABaSBay6DZdvbfXG=jwxNkWtcZVjhw7Bi6Ro1e3mLTmCWdn8zQ@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTFDVfOai0Y=O7UWrk5pk5pWSMz+FGedJngEZ-V=bDjGTg@mail.gmail.com>

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

On Sat, Feb 14, 2015 at 1:04 PM, Adam Back <adam@cypherspace.org> wrote:

> That its highly complex to maintain strict consensus between bitcoin
> versions, does not justify consensus rewrite experiments


Correct. However, those maintenance costs absolutely do justify working
towards formal proofs of correctness for the existing implementation. These
plans are no secret and are publicly discussed, but I think it would be
instrumental to outsiders if the correctness plans and ongoing progress
could be mentioned whenever a warning is made about unjustified and
dangerous Bitcoin consensus rewrite attempts.

- Bryan
http://heybryan.org/
1 512 203 0507

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

  reply	other threads:[~2015-02-14 19:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABm2gDpReRty6TdfMDssjF27XgC_SYs_U__SFBNdsYW24Mzh8w@mail.gmail.com>
     [not found] ` <54CC0E1D.7030409@voskuil.org>
     [not found]   ` <CABm2gDqM6q24tPEBKSHbbVQu-mvfV37PNc4hD=VjyRHk2jujZw@mail.gmail.com>
     [not found]     ` <54D0414F.6030806@voskuil.org>
     [not found]       ` <CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
     [not found]         ` <54DE7601.4070509@voskuil.org>
     [not found]           ` <CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
     [not found]             ` <54DF07A5.1060004@voskuil.org>
     [not found]               ` <CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
     [not found]                 ` <54DF2E80.5060506@voskuil.org>
2015-02-14 13:13                   ` [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?) Peter Todd
2015-02-14 14:23                     ` Tamas Blummer
2015-02-14 19:04                       ` Adam Back
2015-02-14 19:29                         ` Bryan Bishop [this message]
2015-02-15 17:11                         ` Peter Todd
2015-02-14 20:00                       ` Jorge Timón
2015-02-15  0:05                       ` Luke Dashjr
2015-02-15 17:02                       ` Peter Todd
2015-02-15 17:13                         ` Tamas Blummer
2015-02-15 17:21                           ` Peter Todd
2015-02-15 21:48                           ` joliver
2015-02-19  3:32                           ` Troy Benjegerdes
2015-02-19  3:44                             ` Peter Todd
2015-02-19  5:22                               ` Tamas Blummer
2015-02-19  5:27                                 ` Tamas Blummer
2015-02-19 14:03                                 ` Bryan Bishop
2015-02-19 14:09                                   ` Tamas Blummer
2015-02-19 17:16                                     ` Jorge Timón
2015-02-19 17:30                                       ` Mike Hearn
2015-02-19 21:43                                         ` Sean Gilligan
2015-02-19 22:53                                           ` Angel Leon
2015-02-20  3:47                                         ` Jorge Timón
     [not found]                     ` <54EE17DD.7050309@voskuil.org>
2015-03-25  8:04                       ` Eric Voskuil

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='CABaSBay6DZdvbfXG=jwxNkWtcZVjhw7Bi6Ro1e3mLTmCWdn8zQ@mail.gmail.com' \
    --to=kanzure@gmail.com \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bryan@ledgerx.com \
    --cc=libbitcoin@lists.dyne.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