From: Mike Hearn <mike@plan99.net>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Large-blocks and censorship
Date: Thu, 7 Mar 2013 18:42:32 +0100 [thread overview]
Message-ID: <CANEZrP0MHA_Mv37DSv=CLBWLHo_-ajRgNRd1-4EGJ2GZvTxiJQ@mail.gmail.com> (raw)
In-Reply-To: <20130307110018.GA7491@savin>
To summarize your post - it's another go at arguing for strongly
limited block sizes, this time on the grounds that large blocks make
it easier for $AUTHORITY to censor transactions? Is that right?
next prev parent reply other threads:[~2013-03-07 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 11:00 [Bitcoin-development] Large-blocks and censorship Peter Todd
2013-03-07 11:34 ` Peter Todd
2013-03-07 17:42 ` Mike Hearn [this message]
2013-03-07 18:30 ` Peter Todd
2013-03-07 21:19 ` Mike Hearn
2013-03-07 21:31 ` Daniel Lidstrom
2013-03-10 8:18 ` 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='CANEZrP0MHA_Mv37DSv=CLBWLHo_-ajRgNRd1-4EGJ2GZvTxiJQ@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--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