public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Filipe Farinha <filipe@ktorn.com>
To: Peter Todd <pete@petertodd.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Mempool size consensus + dynamic block size re-targetting
Date: Wed, 24 Jun 2015 11:02:37 +0800	[thread overview]
Message-ID: <558A1DCD.8030702@ktorn.com> (raw)
In-Reply-To: <20150624024344.GA3647@savin.petertodd.org>

On 24/06/2015 10:43, Peter Todd wrote:
> It might help you to answer the following: If your mempool consensus 
> idea worked, could you use it to replace proof-of-work? Why? Why not? 
I shouldn't have to answer that, but the answer is clearly no.

Please consider this argument when evaluating the pros and cons of BIP 100.

Filipe Farinha


      reply	other threads:[~2015-06-24  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  2:02 [bitcoin-dev] Mempool size consensus + dynamic block size re-targetting Filipe Farinha
2015-06-24  2:15 ` Mark Friedenbach
2015-06-24  2:24   ` Filipe Farinha
2015-06-24  2:43     ` Peter Todd
2015-06-24  3:02       ` Filipe Farinha [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=558A1DCD.8030702@ktorn.com \
    --to=filipe@ktorn.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.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