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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y7p5b-0001cS-LG for bitcoin-development@lists.sourceforge.net; Sun, 04 Jan 2015 17:35:43 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.171 as permitted sender) client-ip=209.85.213.171; envelope-from=gmaxwell@gmail.com; helo=mail-ig0-f171.google.com; Received: from mail-ig0-f171.google.com ([209.85.213.171]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Y7p5a-0000OC-ET for bitcoin-development@lists.sourceforge.net; Sun, 04 Jan 2015 17:35:43 +0000 Received: by mail-ig0-f171.google.com with SMTP id z20so1481743igj.16 for ; Sun, 04 Jan 2015 09:35:37 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.42.107.83 with SMTP id c19mr63365126icp.48.1420392937168; Sun, 04 Jan 2015 09:35:37 -0800 (PST) Received: by 10.107.16.30 with HTTP; Sun, 4 Jan 2015 09:35:37 -0800 (PST) In-Reply-To: <54A976C3.1030805@jrn.me.uk> References: <54A95179.2070200@jrn.me.uk> <54A976C3.1030805@jrn.me.uk> Date: Sun, 4 Jan 2015 17:35:37 +0000 Message-ID: From: Gregory Maxwell To: Ross Nicoll Content-Type: text/plain; charset=UTF-8 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 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.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Y7p5a-0000OC-ET Cc: bitcoin-development Subject: Re: [Bitcoin-development] Re-enabling simple 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: Sun, 04 Jan 2015 17:35:43 -0000 On Sun, Jan 4, 2015 at 5:22 PM, Ross Nicoll wrote: > Grabbing a simple test case: > https://chain.so/tx/BTCTEST/f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6ac1f8 > - that won't lock until 0028 UTC on the 5th. > > I've tried closing the wallet, moving the wallet.dat file out of the > way, and then attempting the spend transaction (which can be locked > immediately), and it either rejects it on acceptance to mempool, or it > is never included in a block. Can you send me the actual raw transaction (that site doesn't appear have a way to get it, only some cooked json output; which doesn't include the sequence number). As I said, it's a severe bug if unlocked transactions are being relayed or mempooled far in advance. > They can only replace a non-final transaction with a final transaction, Ah I missed that the replacement had to be final. Thats indeed a much more sane thing to do than I was thinking (sorry for some reason I saw the +1 and thought it was just checking the sequence number was higher.) > I don't think that's a major issue? If they can relay the first one to begin with its an an issue, the replacement just makes it twice an issue. :)