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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1USp2A-0005H2-02 for bitcoin-development@lists.sourceforge.net; Thu, 18 Apr 2013 13:37:54 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.178 as permitted sender) client-ip=74.125.82.178; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f178.google.com; Received: from mail-we0-f178.google.com ([74.125.82.178]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1USp29-0004Sp-7T for bitcoin-development@lists.sourceforge.net; Thu, 18 Apr 2013 13:37:53 +0000 Received: by mail-we0-f178.google.com with SMTP id z53so2263732wey.37 for ; Thu, 18 Apr 2013 06:37:47 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.109.197 with SMTP id hu5mr18469132wib.22.1366292266882; Thu, 18 Apr 2013 06:37:46 -0700 (PDT) Received: by 10.194.143.36 with HTTP; Thu, 18 Apr 2013 06:37:46 -0700 (PDT) In-Reply-To: References: <453bfc69-b2ab-4992-9807-55270fbda0db@email.android.com> <20130418090444.GA30995@savin> <20130418100806.GA13908@savin> Date: Thu, 18 Apr 2013 09:37:46 -0400 Message-ID: From: Gavin Andresen To: Mike Hearn Content-Type: multipart/alternative; boundary=e89a8f2356f73a209b04daa2b568 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1USp29-0004Sp-7T Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Anti DoS for tx replacement 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: Thu, 18 Apr 2013 13:37:54 -0000 --e89a8f2356f73a209b04daa2b568 Content-Type: text/plain; charset=ISO-8859-1 > sure it's worth doing, at least immediately. Weakening the non-final == >> > non-standard test to give a window of, say, 3 blocks, would be fine I >> think. >> > > Sure. I think Gavin wants some kind of wider memory pool limiter policy > which would encompass such a thing already. > Yes. I don't want to spend any time thinking about memory pool transaction replacement until after we pay some technical debt: + Memory-limited memory pool, with relay policy matching block-creation policy + Child-pays-for-parent fees + Auto-computed fees, based on transactions moving from the memory pool into blocks -- -- Gavin Andresen --e89a8f2356f73a209b04daa2b568 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable =A0
sure it's worth doing, at leas= t immediately. Weakening the non-final =3D=3D
=
non-standard test to give a window of, say, 3 blocks, would be fine I
think.

Sure. I think Gavin wants = some kind of wider memory pool limiter policy which would encompass such a = thing already.

Yes.

I don't want to spend any time thinking a= bout memory pool transaction replacement until after we pay some technical = debt:

+ Memory-limited memory pool, with relay pol= icy matching block-creation policy
+ Child-pays-for-parent fees
+ Auto-computed fees, based on = transactions moving from the memory pool into blocks


--
--
Gavin Andresen
--e89a8f2356f73a209b04daa2b568--