From: Ross Nicoll <jrn@jrn•me.uk>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Re-enabling simple tx replacement
Date: Sun, 04 Jan 2015 17:45:01 +0000 [thread overview]
Message-ID: <54A97C1D.1080604@jrn.me.uk> (raw)
In-Reply-To: <CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6ac1f8.hex --]
[-- Type: text/x-hex; name="f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6ac1f8.hex", Size: 606 bytes --]
01000000019fbf1e1c6543278795a24a5138cd9eea17a24ff40f246dece6312f0c5fcd682600000000da00493046022100ee7d395355d2b5504289e4de88cd1694d4fbfb68c6083d2b1d97668f8aecad81022100cbb2def124eaac394d97a3619b1cf723101878105eefc179201ade5651e0ed1e01483045022100ae62d80c3c38a52d27ea649f274c17c0ed438350577b7e22d4d83a780f0c29a302200e9c371c52d9819d6c37b90466fcf3b7b074d92e075bd043d5a16a392fdaed3101522103abd60343437179d12abc40da47c26ad261e2d22f5c89d8af254d4e5dddae11a321020c076f4c121583b2f4ef93e8186d61cd35cecc18d15c5aa993a8759d678c1eb0520100000001583e0f00000000001976a914098ff5dc58c2c8af6a343a6be9be4a15d0408e5288aca9daa954
prev parent reply other threads:[~2015-01-04 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 14:43 Ross Nicoll
2015-01-04 17:04 ` Gregory Maxwell
2015-01-04 17:22 ` Ross Nicoll
2015-01-04 17:35 ` Gregory Maxwell
2015-01-04 17:44 ` Gregory Maxwell
2015-01-04 17:47 ` Peter Todd
2015-01-04 18:11 ` Ross Nicoll
2015-01-04 18:31 ` Gregory Maxwell
2015-01-04 23:06 ` Jorge Timón
2015-01-04 17:45 ` Ross Nicoll [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54A97C1D.1080604@jrn.me.uk \
--to=jrn@jrn$(echo .)me.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox