From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <raystonn@hotmail.com>) id 1Z25FM-000718-6T for bitcoin-development@lists.sourceforge.net; Mon, 08 Jun 2015 22:10:20 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of hotmail.com designates 65.55.34.22 as permitted sender) client-ip=65.55.34.22; envelope-from=raystonn@hotmail.com; helo=COL004-OMC1S12.hotmail.com; Received: from col004-omc1s12.hotmail.com ([65.55.34.22]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Z25FL-00087o-B3 for bitcoin-development@lists.sourceforge.net; Mon, 08 Jun 2015 22:10:20 +0000 Received: from COL131-DS15 ([65.55.34.9]) by COL004-OMC1S12.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Mon, 8 Jun 2015 15:10:13 -0700 X-TMN: [Cr/FzDmY6RppPIY9MUdsTI7cAIsxRhN5] X-Originating-Email: [raystonn@hotmail.com] Message-ID: <COL131-DS1513BA5E7AB827EAA819C1CDBF0@phx.gbl> From: "Raystonn ." <raystonn@hotmail.com> To: "Btc Drak" <btcdrak@gmail.com> References: <5574E39C.3090904@thinlink.com> <COL131-DS25374BEFA76744E26EB8CBCDBF0@phx.gbl> <AD4A025F-D782-4094-9CBC-EBEF0DD04838@newcastle.ac.uk> <COL131-DS2729F02884BC43E54C8D63CDBF0@phx.gbl> <7E7DF414-6DDB-48A6-9199-D6883209B67D@newcastle.ac.uk> <COL131-DS61BB9B5776DE65077ED0ACDBF0@phx.gbl> <20150608214443.GC19826@muck> <COL131-DS52C1B18F4EFC4D7D7EEA1CDBF0@phx.gbl> <CADJgMztM1X4qudWocf5eYQ2fALHoWVu33gOkfQ-Co6NzWq8OGw@mail.gmail.com> In-Reply-To: <CADJgMztM1X4qudWocf5eYQ2fALHoWVu33gOkfQ-Co6NzWq8OGw@mail.gmail.com> Date: Mon, 8 Jun 2015 15:10:03 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02C8_01D0A1FD.3264A980" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-OriginalArrivalTime: 08 Jun 2015 22:10:13.0543 (UTC) FILETIME=[E4922B70:01D0A237] X-Spam-Score: -0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (raystonn[at]hotmail.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [65.55.34.22 listed in list.dnswl.org] 1.0 HTML_MESSAGE BODY: HTML included in message 1.0 FREEMAIL_REPLY From and body contain different freemails -0.6 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z25FL-00087o-B3 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 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Mon, 08 Jun 2015 22:10:20 -0000 ------=_NextPart_000_02C8_01D0A1FD.3264A980 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Not forgetting, simply deferring discussion on that. We=E2=80=99ve a = much smaller limit to deal with right now. But even that limit would = have to go to remove this attack. From: Btc Drak=20 Sent: Monday, June 08, 2015 3:07 PM To: Raystonn .=20 Cc: Peter Todd ; Bitcoin Dev ; Patrick Mccorry (PGR)=20 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. ------=_NextPart_000_02C8_01D0A1FD.3264A980 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <HTML><HEAD></HEAD> <BODY dir=3Dltr> <DIV dir=3Dltr> <DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial'; COLOR: #000000"> <DIV>Not forgetting, simply deferring discussion on that. = We=E2=80=99ve a much=20 smaller limit to deal with right now. But even that limit would = have to go=20 to remove this attack.</DIV> <DIV=20 style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: = "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; = DISPLAY: inline'> <DIV style=3D"FONT: 10pt tahoma"> <DIV> </DIV> <DIV style=3D"BACKGROUND: #f5f5f5"> <DIV style=3D"font-color: black"><B>From:</B> <A = title=3Dbtcdrak@gmail.com=20 href=3D"mailto:btcdrak@gmail.com">Btc Drak</A> </DIV> <DIV><B>Sent:</B> Monday, June 08, 2015 3:07 PM</DIV> <DIV><B>To:</B> <A title=3Draystonn@hotmail.com=20 href=3D"mailto:raystonn@hotmail.com">Raystonn .</A> </DIV> <DIV><B>Cc:</B> <A title=3Dpete@petertodd.org=20 href=3D"mailto:pete@petertodd.org">Peter Todd</A> ; <A=20 title=3Dbitcoin-development@lists.sourceforge.net=20 href=3D"mailto:bitcoin-development@lists.sourceforge.net">Bitcoin = Dev</A> ; <A=20 title=3Dpatrick.mccorry@newcastle.ac.uk=20 href=3D"mailto:patrick.mccorry@newcastle.ac.uk">Patrick Mccorry = (PGR)</A> </DIV> <DIV><B>Subject:</B> Re: [Bitcoin-development] New attack identified and = potential solution described: Dropped-transaction spam attack against = the=20 blocksize limit</DIV></DIV></DIV> <DIV> </DIV></DIV> <DIV=20 style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: = "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; = DISPLAY: inline'> <DIV dir=3Dltr> <DIV class=3Dgmail_extra> <DIV class=3Dgmail_quote>On Mon, Jun 8, 2015 at 11:01 PM, Raystonn . = <SPAN=20 dir=3Dltr><<A href=3D"mailto:raystonn@hotmail.com"=20 target=3D_blank>raystonn@hotmail.com</A>></SPAN> wrote:<BR> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc = 1px solid">No,=20 with no blocksize limit, a spammer would would flood the network=20 with<BR>transactions until they ran out of money.</BLOCKQUOTE> <DIV> </DIV> <DIV>I think you are forgetting even if you remove the blocksize limit, = there is=20 still a hard message size limit imposed by the p2p protocol. Block would = de-facto be limited to this=20 size.</DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></HTML> ------=_NextPart_000_02C8_01D0A1FD.3264A980--