From: Mike Hearn <hearn@vinumeris•com>
To: Allen Piscitello <allen.piscitello@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Is it possible for there to be two chains after a hard fork?
Date: Tue, 29 Sep 2015 20:02:06 +0200 [thread overview]
Message-ID: <CA+w+GKRPNneye6=pJ5R1n3q-8h621gw=UcgyBooJLXuTQ3z1Zg@mail.gmail.com> (raw)
In-Reply-To: <CAJfRnm4WwtNvChcCGCzDLJZrg3VZqJz-X-XXC0Ftyga3x=P8-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
>
> Mining empty blocks is not fraud.
>
I didn't say it was, sorry, the comma was separating two list items. By
"fraud" I meant double spending. Mining only empty blocks would be a DoS
attack rather than double spending.
[-- Attachment #2: Type: text/html, Size: 523 bytes --]
prev parent reply other threads:[~2015-09-29 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 14:04 Gavin Andresen
2015-09-29 14:17 ` Jonathan Toomim (Toomim Bros)
2015-09-29 14:59 ` Mark Friedenbach
2015-09-29 17:24 ` Allen Piscitello
2015-09-29 17:35 ` Gavin Andresen
2015-09-29 17:43 ` Allen Piscitello
2015-09-29 17:51 ` Mike Hearn
2015-09-29 17:55 ` Allen Piscitello
2015-09-29 18:01 ` Gavin Andresen
2015-09-29 18:23 ` Allen Piscitello
2015-09-30 16:14 ` Jorge Timón
2015-09-29 18:02 ` Mike Hearn [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='CA+w+GKRPNneye6=pJ5R1n3q-8h621gw=UcgyBooJLXuTQ3z1Zg@mail.gmail.com' \
--to=hearn@vinumeris$(echo .)com \
--cc=allen.piscitello@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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