From: "Raystonn ." <raystonn@hotmail•com>
To: "Gavin Andresen" <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
Date: Tue, 9 Jun 2015 12:03:13 -0700 [thread overview]
Message-ID: <COL131-DS897EBDD5B5E7BD300318CCDBE0@phx.gbl> (raw)
In-Reply-To: <CABsx9T0TzRCr7DRzALymWiNJ2oA_MuZZQ8jFD+z4-cUaiSsE1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
You are right of course. This will work. I like this idea more than my own proposed fix, as it doesn’t make any big changes to the economics of the system in the way that burning would have.
From: Gavin Andresen
Sent: Tuesday, June 09, 2015 11:25 AM
To: Raystonn .
Cc: Loi Luu ; Bitcoin Dev
Subject: Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
On Tue, Jun 9, 2015 at 1:52 PM, Raystonn . <raystonn@hotmail•com> wrote:
That does sound good on the surface, but how do we enforce #1 and #2? They seem to be unenforceable, as a miner can adjust the size of the memory pool in his local source.
It doesn't have to be enforced. As long as a reasonable percentage of hash rate is following that policy an attacker that tries to flood the network will fail to prevent normal transaction traffic from going through and will just end up transferring some wealth to the miners.
Although the existing default mining policy (which it seems about 70% of hashpower follows) of setting aside some space for high-priority transactions regardless of fee might also be enough to cause this attack to fail in practice.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 2931 bytes --]
next prev parent reply other threads:[~2015-06-09 19:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 0:36 [Bitcoin-development] Block Size Experiment Underway Tom Harding
2015-06-08 20:07 ` [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit Raystonn .
[not found] ` <AD4A025F-D782-4094-9CBC-EBEF0DD04838@newcastle.ac.uk>
2015-06-08 21:14 ` Raystonn .
2015-06-08 21:33 ` Peter Todd
2015-06-08 21:40 ` [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit Raystonn .
[not found] ` <4A74E0B9-869E-448A-BFC7-7FD2F50F142F@newcastle.ac.uk>
2015-06-08 22:26 ` [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit Peter Todd
[not found] ` <7E7DF414-6DDB-48A6-9199-D6883209B67D@newcastle.ac.uk>
2015-06-08 21:33 ` Raystonn .
2015-06-08 21:44 ` Peter Todd
2015-06-08 22:01 ` [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit Raystonn .
2015-06-08 22:07 ` Btc Drak
2015-06-08 22:10 ` Raystonn .
2015-06-08 22:18 ` Peter Todd
2015-06-08 22:46 ` Raystonn .
2015-06-08 22:06 ` [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit Bob McElrath
2015-06-08 22:28 ` Peter Todd
2015-06-09 9:33 ` Loi Luu
2015-06-09 13:36 ` Gavin Andresen
2015-06-09 14:18 ` Tier Nolan
2015-06-09 17:52 ` Raystonn .
2015-06-09 18:25 ` Gavin Andresen
2015-06-09 19:03 ` Raystonn . [this message]
2015-06-20 3:49 ` David Vorick
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=COL131-DS897EBDD5B5E7BD300318CCDBE0@phx.gbl \
--to=raystonn@hotmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(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