diff options
| author | Gregory Maxwell <gmaxwell@gmail.com> | 2012-10-26 10:17:04 -0400 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2012-10-26 14:17:10 +0000 |
| commit | b997a856dbe47906739d595a00786ebb693349f5 (patch) | |
| tree | 28b662b18d7da06d65634ac7feb8d3201a017846 /e0/c9290ddf53387fe8710716e8a9ffbaa41a2568 | |
| parent | 7089cc70c0247bb786391fa753a72843e2f980c3 (diff) | |
| download | pi-bitcoindev-b997a856dbe47906739d595a00786ebb693349f5.tar.gz pi-bitcoindev-b997a856dbe47906739d595a00786ebb693349f5.zip | |
Re: [Bitcoin-development] Draft BIP for Bloom filtering
Diffstat (limited to 'e0/c9290ddf53387fe8710716e8a9ffbaa41a2568')
| -rw-r--r-- | e0/c9290ddf53387fe8710716e8a9ffbaa41a2568 | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/e0/c9290ddf53387fe8710716e8a9ffbaa41a2568 b/e0/c9290ddf53387fe8710716e8a9ffbaa41a2568 new file mode 100644 index 000000000..8d819b628 --- /dev/null +++ b/e0/c9290ddf53387fe8710716e8a9ffbaa41a2568 @@ -0,0 +1,77 @@ +Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] + helo=mx.sourceforge.net) + by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <gmaxwell@gmail.com>) id 1TRkik-00058G-Gf + for bitcoin-development@lists.sourceforge.net; + Fri, 26 Oct 2012 14:17:10 +0000 +Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.223.175 as permitted sender) + client-ip=209.85.223.175; envelope-from=gmaxwell@gmail.com; + helo=mail-ie0-f175.google.com; +Received: from mail-ie0-f175.google.com ([209.85.223.175]) + by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1TRkij-0006hj-Qd + for bitcoin-development@lists.sourceforge.net; + Fri, 26 Oct 2012 14:17:10 +0000 +Received: by mail-ie0-f175.google.com with SMTP id c13so4112762ieb.34 + for <bitcoin-development@lists.sourceforge.net>; + Fri, 26 Oct 2012 07:17:04 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.43.7.132 with SMTP id oo4mr19655066icb.6.1351261024572; Fri, + 26 Oct 2012 07:17:04 -0700 (PDT) +Received: by 10.64.171.73 with HTTP; Fri, 26 Oct 2012 07:17:04 -0700 (PDT) +In-Reply-To: <CANEZrP2sBZL=UYAxtjU2Su13Z12wB7s04LxmcyUR2hH51tcN9g@mail.gmail.com> +References: <CANEZrP0XALwBFJyZTzYd5xBp4MRrjv0s_y2tOXbO7UgjWF2HzA@mail.gmail.com> + <CAAS2fgScydOWz_eqnhWxQNVUOtzvSBwkj7tttP3_DLdW+=3CTQ@mail.gmail.com> + <CANEZrP2sBZL=UYAxtjU2Su13Z12wB7s04LxmcyUR2hH51tcN9g@mail.gmail.com> +Date: Fri, 26 Oct 2012 10:17:04 -0400 +Message-ID: <CAAS2fgSPk8QgYq2zcV+G2GoQyo5AfnRj4=+sURr34KZakhqazQ@mail.gmail.com> +From: Gregory Maxwell <gmaxwell@gmail.com> +To: Mike Hearn <mike@plan99.net> +Content-Type: text/plain; charset=UTF-8 +X-Spam-Score: -1.4 (-) +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 + (gmaxwell[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from + author's domain + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature + 0.2 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1TRkij-0006hj-Qd +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Draft BIP for Bloom filtering +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: Fri, 26 Oct 2012 14:17:10 -0000 + +On Fri, Oct 26, 2012 at 10:01 AM, Mike Hearn <mike@plan99.net> wrote: +> If you just want to waste bandwidth of nodes you can connect to nodes +> and repeatedly download blocks, or fill the network with fake nodes +> that spam random generated transactions to whoever connects. I don't +> see how to avoid that so it seems odd to worry about a much more +> complicated attack. + +Because I can potentially waste bandwidth of all nodes forever (well as long +as users are still scanning blocks with my transactions in them) with O(1) work. + +Though I'm not sure how much of a threat is vs just paying 1e-8 btc to lots of +addresses which would only be less bad by some constant factor as worse. +I guess I should try to attack it and see how bad the pollution I can construct +should be. (offline, of course) + + |