public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@jtimon•cc>
To: Btc Drak <btcdrak@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT Fork
Date: Wed, 19 Aug 2015 20:22:17 +0200	[thread overview]
Message-ID: <CABm2gDrQ3DEDQLA0b6kTppxU+CL6rYNocymPeVo2eTmLnDUYLw@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzv+cKPY9wrAzbk5pgQJS0=R9KWu-+EuppM=nmXs8RHxYg@mail.gmail.com>

On Wed, Aug 19, 2015 at 7:32 PM, Btc Drak via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Wed, Aug 19, 2015 at 5:53 PM, Adam Back via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>> ignored the warnings.  Many also warned that 75% was an optimally BAD
>> trigger ratio (and that in a hard fork it is not a miner vote really
>> as in soft-forks).  Gavin & Mike ignored that warning to.  I know they
>> heard those warnings because I told them 1:1 in person or via email
>> and had on going conversations.  Others did too.
>
> I would like to add for the record, I also warned Gavin of this in his
> PR to Bitcoin Core, and also suggested a timeout which if
> activation/enforcement did not occur within, hard fork deployment
> would be cancelled. His response was to delete these from the PR
> claiming thresholds were not relevant conversation in his PR and
> belonged elsewhere (even though they had already been discussed
> elsewhere).

I don't know the timeline for this, but maybe he was referring to
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009731.html
(where he is one of the few people that have participated).


  parent reply	other threads:[~2015-08-19 18:22 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 16:53 Adam Back
2015-08-19 17:22 ` Simon Liu
2015-08-19 18:13   ` Peter Todd
2015-08-19 23:37     ` Simon Liu
2015-08-19 17:28 ` Jorge Timón
2015-08-19 17:32 ` Btc Drak
2015-08-19 18:20   ` Peter Todd
2015-08-19 19:15     ` Btc Drak
2015-08-19 19:32       ` odinn
2015-08-19 19:48         ` Eric Lombrozo
2015-08-19 19:58           ` Jorge Timón
2015-08-19 20:04             ` Eric Lombrozo
2015-08-19 22:00               ` Jorge Timón
2015-08-19 23:07                 ` Eric Voskuil
2015-08-19 23:27                   ` Jorge Timón
2015-08-19 23:56                     ` Jorge Timón
2015-08-20  1:00                       ` GC
2015-08-20  1:17                         ` Jorge Timón
2015-08-20  0:08                     ` Eric Voskuil
2015-08-19 18:22   ` Jorge Timón [this message]
2015-08-19 19:12 ` Santino Napolitano
2015-08-19 19:28   ` Eric Lombrozo
2015-08-20  9:00 ` Mike Hearn
2015-08-20  9:13   ` Peter Todd
2015-08-21  3:01     ` odinn
  -- strict thread matches above, loose matches on Subject: below --
2015-08-19  8:25 Btc Drak
2015-08-17 20:24 Theo Chino
2015-08-18  4:56 ` Dave Scotese
2015-08-15 17:43 Satoshi Nakamoto
2015-08-15 19:08 ` Laszlo Hanyecz
2015-08-15 19:10 ` jl2012
2015-08-17 11:40 ` Oliver Egginger
2015-08-17 11:44   ` Jorge Timón
2015-08-17 11:51     ` Oliver Egginger
2015-08-17 16:32       ` Jorge Timón
2015-08-17 17:01         ` Oliver Egginger
2015-08-17 17:15           ` Jorge Timón
2015-08-17 17:30             ` Btc Drak
2015-08-17 17:18       ` Gregory Maxwell
2015-08-17 19:14         ` Peter Todd
2015-08-17 17:28   ` Jeff Garzik
2015-08-17 19:03   ` Warren Togami Jr.
2015-08-17 20:37     ` Oliver Egginger
2015-08-18  5:16       ` Gregory Maxwell
2015-08-18  9:15       ` Warren Togami Jr.
2015-08-18 11:52         ` Micha Bailey
2015-08-18 18:57         ` Oliver Egginger
2015-08-18 20:59           ` Anon Moto
2015-08-19  1:03             ` Sergio Demian Lerner
2015-08-17 19:02 ` Anon Moto
2015-08-17 19:40   ` Marcel Jamin
2015-08-17 19:16 ` Hector Chu
2015-08-17 19:28   ` Gregory Maxwell
2015-08-17 19:39     ` Jorge Timón
2015-08-19  2:54 ` odinn
2015-08-19  2:59   ` Angel Leon

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=CABm2gDrQ3DEDQLA0b6kTppxU+CL6rYNocymPeVo2eTmLnDUYLw@mail.gmail.com \
    --to=jtimon@jtimon$(echo .)cc \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=btcdrak@gmail$(echo .)com \
    /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