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] BIP 100 specification
Date: Thu, 3 Sep 2015 18:13:34 +0200	[thread overview]
Message-ID: <CABm2gDqY5=2WB4D1E-r9QfEBbreYPzq7dou9SYH3HCLzfpKLPg@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzsXrrY+-OHzUmnaDmFkqvDr29eHuwOvovSnUwjVnOiZOQ@mail.gmail.com>

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

On Sep 3, 2015 5:58 PM, "Btc Drak via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> On Thu, Sep 3, 2015 at 3:34 PM, Jeff Garzik <jgarzik@gmail.com> wrote:
> > A discussion of rolling out BIP 100 will not be avoided :)
> >
> > It is a hard fork; it would be silly to elide discussion of these key
> > issues.
> >
> > I don't get the community's recent interest in avoiding certain topics.
>
> It's not a matter of avoiding the subject, it's a whole separate
> discussion and in the interests of efficient discussion, it is best
> done separately. There's a whole BIP dedicated to the discussion of
> consensus forks which you should probably give some input in also,
> BIP99 [1]
>
> Once we come to an agreement and can say "here's what we're doing
> about blocksize, it will be X, or we'll raise by this algo", then we
> can discuss the best way to implement the hard fork.
>
> [1] https://github.com/bitcoin/bips/pull/181

In fact, that discussion can happen in parallel. But it is more efficient
to do so in one place instead of in each of the 5+ hardfork proposals
(bip99 itself has a hardfork proposal with its code ready).

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

  reply	other threads:[~2015-09-03 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03  3:33 [bitcoin-dev] BIP 100 specification Jeff Garzik
2015-09-03  4:45 ` Dave Scotese
2015-09-03  7:57 ` jl2012
2015-09-03 11:20   ` Btc Drak
2015-09-03 14:34     ` Jeff Garzik
2015-09-03 15:58       ` Btc Drak
2015-09-03 16:13         ` Jorge Timón [this message]
2015-09-03 11:59   ` Tier Nolan
2015-09-03 16:32     ` jl2012
2015-09-03 16:35       ` Jeff Garzik
2015-09-03 17:32         ` Btc Drak
2015-09-03 17:52           ` Peter Todd
2015-09-04  7:53     ` Andy Chase
2015-09-04 15:37       ` Simon Liu
2015-09-04 15:40         ` Btc Drak
2015-09-03 14:35   ` Jeff Garzik
2015-09-03 19:40 ` Simon Liu
2015-09-03 20:15   ` Oliver Petruzel
2015-09-03 20:34     ` Dave Scotese
2015-09-04  3:50       ` Peter Todd

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='CABm2gDqY5=2WB4D1E-r9QfEBbreYPzq7dou9SYH3HCLzfpKLPg@mail.gmail.com' \
    --to=jtimon@jtimon.cc \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=btcdrak@gmail.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