summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoss Nicoll <jrn@jrn.me.uk>2015-01-04 17:45:01 +0000
committerbitcoindev <bitcoindev@gnusha.org>2015-01-04 17:45:10 +0000
commitf2234ea241e638fe3d2e5a96e1e4ed85f9c403ed (patch)
treefb8fc52de6fec74da2a7d2606cd54c23146ed690
parent3518314e2f2dd181a527922be7a9e2e42536fb29 (diff)
downloadpi-bitcoindev-f2234ea241e638fe3d2e5a96e1e4ed85f9c403ed.tar.gz
pi-bitcoindev-f2234ea241e638fe3d2e5a96e1e4ed85f9c403ed.zip
Re: [Bitcoin-development] Re-enabling simple tx replacement
-rw-r--r--66/132eb6f977966b6df35d25c590d6a59c11f046109
1 files changed, 109 insertions, 0 deletions
diff --git a/66/132eb6f977966b6df35d25c590d6a59c11f046 b/66/132eb6f977966b6df35d25c590d6a59c11f046
new file mode 100644
index 000000000..a822b455b
--- /dev/null
+++ b/66/132eb6f977966b6df35d25c590d6a59c11f046
@@ -0,0 +1,109 @@
+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 <jrn@jrn.me.uk>) id 1Y7pEk-0000Wa-Ae
+ for bitcoin-development@lists.sourceforge.net;
+ Sun, 04 Jan 2015 17:45:10 +0000
+X-ACL-Warn:
+Received: from s3.neomailbox.net ([178.209.62.157])
+ by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
+ id 1Y7pEi-0000ul-35 for bitcoin-development@lists.sourceforge.net;
+ Sun, 04 Jan 2015 17:45:10 +0000
+Message-ID: <54A97C1D.1080604@jrn.me.uk>
+Date: Sun, 04 Jan 2015 17:45:01 +0000
+From: Ross Nicoll <jrn@jrn.me.uk>
+User-Agent: Mozilla/5.0 (X11; Linux x86_64;
+ rv:31.0) Gecko/20100101 Thunderbird/31.3.0
+MIME-Version: 1.0
+To: Gregory Maxwell <gmaxwell@gmail.com>
+References: <54A95179.2070200@jrn.me.uk> <CAAS2fgSw=Goibe2LkXsEH5xjyftjQq4FxJh-dhaP_N5ea21ugQ@mail.gmail.com> <54A976C3.1030805@jrn.me.uk>
+ <CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com>
+In-Reply-To: <CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com>
+Content-Type: multipart/mixed; boundary="------------030605010203080806030807"
+X-Spam-Score: 0.0 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+X-Headers-End: 1Y7pEi-0000ul-35
+Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
+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: <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: Sun, 04 Jan 2015 17:45:10 -0000
+
+This is a multi-part message in MIME format.
+--------------030605010203080806030807
+Content-Type: text/plain; charset=utf-8
+Content-Transfer-Encoding: 7bit
+
+On 04/01/15 17:35, Gregory Maxwell wrote:
+> On Sun, Jan 4, 2015 at 5:22 PM, Ross Nicoll <jrn@jrn.me.uk> 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.
+
+Attached. Sequence number for the input is set to 1, please do tell me
+if I've misunderstood how it's used.
+
+>> 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. :)
+>
+
+I'll set up a few nodes tomorrow and double check it's in fact relaying
+in the latest version. If it's simply an issue of incorrect relaying,
+that's significantly simpler at least, and the problem can be tackled
+through that instead.
+
+
+--------------030605010203080806030807
+Content-Type: text/x-hex;
+ name="f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6ac1f8.hex"
+Content-Transfer-Encoding: base64
+Content-Disposition: attachment;
+ filename*0="f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6a";
+ filename*1="c1f8.hex"
+
+MDEwMDAwMDAwMTlmYmYxZTFjNjU0MzI3ODc5NWEyNGE1MTM4Y2Q5ZWVhMTdhMjRmZjQwZjI0
+NmRlY2U2MzEyZjBjNWZjZDY4MjYwMDAwMDAwMGRhMDA0OTMwNDYwMjIxMDBlZTdkMzk1MzU1
+ZDJiNTUwNDI4OWU0ZGU4OGNkMTY5NGQ0ZmJmYjY4YzYwODNkMmIxZDk3NjY4ZjhhZWNhZDgx
+MDIyMTAwY2JiMmRlZjEyNGVhYWMzOTRkOTdhMzYxOWIxY2Y3MjMxMDE4NzgxMDVlZWZjMTc5
+MjAxYWRlNTY1MWUwZWQxZTAxNDgzMDQ1MDIyMTAwYWU2MmQ4MGMzYzM4YTUyZDI3ZWE2NDlm
+Mjc0YzE3YzBlZDQzODM1MDU3N2I3ZTIyZDRkODNhNzgwZjBjMjlhMzAyMjAwZTljMzcxYzUy
+ZDk4MTlkNmMzN2I5MDQ2NmZjZjNiN2IwNzRkOTJlMDc1YmQwNDNkNWExNmEzOTJmZGFlZDMx
+MDE1MjIxMDNhYmQ2MDM0MzQzNzE3OWQxMmFiYzQwZGE0N2MyNmFkMjYxZTJkMjJmNWM4OWQ4
+YWYyNTRkNGU1ZGRkYWUxMWEzMjEwMjBjMDc2ZjRjMTIxNTgzYjJmNGVmOTNlODE4NmQ2MWNk
+MzVjZWNjMThkMTVjNWFhOTkzYTg3NTlkNjc4YzFlYjA1MjAxMDAwMDAwMDE1ODNlMGYwMDAw
+MDAwMDAwMTk3NmE5MTQwOThmZjVkYzU4YzJjOGFmNmEzNDNhNmJlOWJlNGExNWQwNDA4ZTUy
+ODhhY2E5ZGFhOTU0
+--------------030605010203080806030807--
+
+