From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UUEbL-0001Ta-0f for bitcoin-development@lists.sourceforge.net; Mon, 22 Apr 2013 11:08:03 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.174 as permitted sender) client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f174.google.com; Received: from mail-ob0-f174.google.com ([209.85.214.174]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UUEbK-0006Jh-6G for bitcoin-development@lists.sourceforge.net; Mon, 22 Apr 2013 11:08:02 +0000 Received: by mail-ob0-f174.google.com with SMTP id wc20so2316208obb.19 for ; Mon, 22 Apr 2013 04:07:56 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.179.42 with SMTP id dd10mr14937328oec.51.1366628876770; Mon, 22 Apr 2013 04:07:56 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.167.169 with HTTP; Mon, 22 Apr 2013 04:07:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Apr 2013 13:07:56 +0200 X-Google-Sender-Auth: -kO_SwHN55smD0lEXrnFFr-ZVxo Message-ID: From: Mike Hearn To: Jeremy Spilman Content-Type: multipart/alternative; boundary=089e01161588bd662004daf114ea X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1UUEbK-0006Jh-6G 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: Mon, 22 Apr 2013 11:08:03 -0000 --089e01161588bd662004daf114ea Content-Type: text/plain; charset=UTF-8 Yes, this is an excellent observation. Thanks Jeremy and Peter. It's much less general than full blown tx replacement+lock times, but for the case of a channel between two people that only ever increases in one direction, it can work. Thanks. I will try implementing this myself for testing on the main network. --089e01161588bd662004daf114ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, this is an excellent observation. Thanks Jeremy and P= eter. It's much less general than full blown tx replacement+lock times,= but for the case of a channel between two people that only ever increases = in one direction, it can work. Thanks. I will try implementing this myself = for testing on the main network.

--089e01161588bd662004daf114ea--