From: Bryan Bishop <kanzure@gmail•com>
To: Bram Cohen <bram@chia•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Bryan Bishop <kanzure@gmail•com>
Subject: Re: [bitcoin-dev] Miner dilution attack on Bitcoin - is that something plausible?
Date: Mon, 18 Jun 2018 15:51:33 -0500 [thread overview]
Message-ID: <CABaSBayDe=92BFQXyX8oan4ptbOmQGHuAhEPjvq78MmazZFJ3g@mail.gmail.com> (raw)
In-Reply-To: <CAHUJnBAU2exMFgPTQx_+h_bktL3Z3B3rsh09aciVtRnGrHJBEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
On Mon, Jun 18, 2018 at 3:40 PM, Bram Cohen via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Not sure what you're saying here. The block rate can't be particularly
> increased or decreased in the long run due to the work difficulty
> adjustment getting you roughly back where you started no matter what.
> Someone could DOS the system by producing empty blocks, sure, that's a
> central attack of what can happen when someone does a 51% attack with no
> special countermeasures other than everything that Bitcoin does at its
> core. An attacker or group of attackers could conspire to reduce block
> sizes in order to increase transaction fees, in fact they could do that
> with a miner activated soft fork. That appears both doable and given past
> things which have happened with transaction fees in the past potentially
> lucrative, particularly as block rewards fall in the future. Please don't
> tell the big mining pools about it.
>
Bram, actually I thought the previous discussions determined that less than
51% hashrate would be required for certain soft-hard-forks employing empty
blocks?
I don't have a specific reference:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012377.html
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012457.html
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-December/013332.html
- Bryan
http://heybryan.org/
1 512 203 0507
[-- Attachment #2: Type: text/html, Size: 3004 bytes --]
next prev parent reply other threads:[~2018-06-18 20:51 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
2018-06-18 20:40 ` Bram Cohen
2018-06-18 20:51 ` Bryan Bishop [this message]
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='CABaSBayDe=92BFQXyX8oan4ptbOmQGHuAhEPjvq78MmazZFJ3g@mail.gmail.com' \
--to=kanzure@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bram@chia$(echo .)net \
/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