From: "Raystonn ." <raystonn@hotmail•com>
To: "Btc Drak" <btcdrak@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
"Patrick Mccorry \(PGR\)" <patrick.mccorry@newcastle•ac.uk>
Subject: Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
Date: Mon, 8 Jun 2015 15:10:03 -0700 [thread overview]
Message-ID: <COL131-DS1513BA5E7AB827EAA819C1CDBF0@phx.gbl> (raw)
In-Reply-To: <CADJgMztM1X4qudWocf5eYQ2fALHoWVu33gOkfQ-Co6NzWq8OGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Not forgetting, simply deferring discussion on that. We’ve a much smaller limit to deal with right now. But even that limit would have to go to remove this attack.
From: Btc Drak
Sent: Monday, June 08, 2015 3:07 PM
To: Raystonn .
Cc: Peter Todd ; Bitcoin Dev ; Patrick Mccorry (PGR)
Subject: Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
On Mon, Jun 8, 2015 at 11:01 PM, Raystonn . <raystonn@hotmail•com> wrote:
No, with no blocksize limit, a spammer would would flood the network with
transactions until they ran out of money.
I think you are forgetting even if you remove the blocksize limit, there is still a hard message size limit imposed by the p2p protocol. Block would de-facto be limited to this size.
[-- Attachment #2: Type: text/html, Size: 2314 bytes --]
next prev parent reply other threads:[~2015-06-08 22:10 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 . [this message]
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 .
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-DS1513BA5E7AB827EAA819C1CDBF0@phx.gbl \
--to=raystonn@hotmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=btcdrak@gmail$(echo .)com \
--cc=patrick.mccorry@newcastle$(echo .)ac.uk \
/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