From: Laszlo Hanyecz <laszlo@heliacal•net>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Miner dilution attack on Bitcoin - is that something plausible?
Date: Mon, 18 Jun 2018 18:49:09 +0000 [thread overview]
Message-ID: <52ead536-d173-f80b-3ffd-b586a591371f@heliacal.net> (raw)
In-Reply-To: <CAJRVQkDM390Y4sVzA8WwM93PY4UqUa8gvPKkT-iA2UcYL6FQ+g@mail.gmail.com>
On 2018-06-18 18:34, Артём Литвинович via bitcoin-dev wrote:
> Suppose a malicious actor were to acquire a majority of hash power, and
> proceed to use that hash power to produce valid, but empty blocks.
https://github.com/libbitcoin/libbitcoin/wiki/Empty-Block-Fallacy
next prev parent reply other threads:[~2018-06-18 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 18:34 Артём Литвинович
2018-06-18 18:47 ` Alexander Leishman
2018-06-19 13:54 ` Eric Voskuil
2018-06-18 18:49 ` Laszlo Hanyecz [this message]
2018-06-18 20:40 ` Bram Cohen
2018-06-18 20:51 ` Bryan Bishop
2018-06-19 18:58 ` Richard Hein
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=52ead536-d173-f80b-3ffd-b586a591371f@heliacal.net \
--to=laszlo@heliacal$(echo .)net \
--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