From: Peter Todd <pete@petertodd•org>
To: Filipe Farinha <filipe@ktorn•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Mempool size consensus + dynamic block size re-targetting
Date: Tue, 23 Jun 2015 22:43:44 -0400 [thread overview]
Message-ID: <20150624024344.GA3647@savin.petertodd.org> (raw)
In-Reply-To: <558A14C3.2040908@ktorn.com>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
On Wed, Jun 24, 2015 at 10:24:03AM +0800, Filipe Farinha wrote:
> On 24/06/2015 10:15, Mark Friedenbach wrote:
> >
> >Anyone could lie.
> >
> True.
> What would be the incentive for the majority of transaction
> broadcasting full-nodes to lie about the mempool size?
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?
--
'peter'[:-1]@petertodd.org
00000000000000001256cc4d7dc7b68be627cbbf65f2b7827fb3e2cc41cf2517
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-06-24 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 2:02 Filipe Farinha
2015-06-24 2:15 ` Mark Friedenbach
2015-06-24 2:24 ` Filipe Farinha
2015-06-24 2:43 ` Peter Todd [this message]
2015-06-24 3:02 ` Filipe Farinha
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=20150624024344.GA3647@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=filipe@ktorn$(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