From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WInKZ-0002Au-TW for bitcoin-development@lists.sourceforge.net; Wed, 26 Feb 2014 22:51:59 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.177 as permitted sender) client-ip=74.125.82.177; envelope-from=jgarzik@bitpay.com; helo=mail-we0-f177.google.com; Received: from mail-we0-f177.google.com ([74.125.82.177]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WInKY-0005cP-SP for bitcoin-development@lists.sourceforge.net; Wed, 26 Feb 2014 22:51:59 +0000 Received: by mail-we0-f177.google.com with SMTP id t61so2242340wes.36 for ; Wed, 26 Feb 2014 14:51:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tA9iqUvd2tVLrEg+MeCOz0aBxPL66e3m4i7NG9acM9U=; b=TT4IhvKy2pZ8/HL4s5Q1RQkCzY9QEYdi7BxL429YknMJuFKbcP3SH76v78hU0MgMQM ITcCvgZ55BoHd3Vh7812eGZcdmHmLmyCFDKoNG6ONar63wmtvjQp0HZF0A7us1XRHbdE 4QtfP/azgD1tXQkD45F0+RpAjfU8HGrAzoXrOOfZfMrUPj267MxnjMR5aNP6G0YzijqS j/dOMdbr1Ost9fRi9l+OwNaQjocf5vItu2CwTin1S19xeOIsdCh5eUJxNCGKsTLvk4bW 3n2LEu+XyIY9Xhb4KIuZQaySEq8wecbw3DFS7KB6Zqh5HxVqcF4LBQLkx6iq6/z0Odn1 g+iQ== X-Gm-Message-State: ALoCoQkwNLiHcg4tO5zekfU0sNU2tyJ+oVpzedzE6BFSjUIzii8kucSM7JlYO0ReM3p+F8Q/K6s6 X-Received: by 10.181.13.112 with SMTP id ex16mr6744233wid.23.1393455112691; Wed, 26 Feb 2014 14:51:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.82.197 with HTTP; Wed, 26 Feb 2014 14:51:32 -0800 (PST) In-Reply-To: <20140225044116.GA28050@savin> References: <20140225044116.GA28050@savin> From: Jeff Garzik Date: Wed, 26 Feb 2014 17:51:32 -0500 Message-ID: To: Bitcoin Dev Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 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 X-Headers-End: 1WInKY-0005cP-SP Subject: Re: [Bitcoin-development] Fee drop X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 22:52:00 -0000 Just pushed out a mempool janitor change to https://github.com/bitcoin/bitcoin/pull/3753 The goal was to create a simple bolt-on change, and /not/ rewrite the mempool code. I'll be running some metrics on what does and does not get into the mempools of my public nodes for 48 hours, ending Friday ~midnight EST. On Mon, Feb 24, 2014 at 11:41 PM, Peter Todd wrote: > So, just to be clear, we're adding, say, a memory limited mempool or > something prior to release so this fee drop doesn't open up an obvious > low-risk DDoS exploit.... right? As we all know, the network bandwidth > DoS attack mitigation strategy relies on transactions we accept to > mempools getting mined, and the clearance rate of the new low-fee > transactions is going to be pretty small; we've already had problems in > the past with mempool growth in periods of high demand. Equally it > should be obvious to people how you can create large groups of low-fee > transactions, and then cheaply double-spend them with higher fee > transactions to suck up network bandwidth - just like I raised for the > equally foolish double-spend propagation pull-req. > > Of course, there's also the problem that we're basically lying to people > about whether or not Bitcoin is a good medium for microtransactions. > It's not. Saying otherwise by releasing software that has known and > obvious DoS attack vulnerabilities that didn't exist in the previous > version is irresponsible on multiple levels. > > -- > 'peter'[:-1]@petertodd.org > 0000000000000000b28e2818c4d8019fb71e33ec2d223f5e09394a89caccf4e2 > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/