From: Gregory Maxwell <gmaxwell@gmail•com>
To: Ross Nicoll <jrn@jrn•me.uk>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Re-enabling simple tx replacement
Date: Sun, 4 Jan 2015 17:35:37 +0000 [thread overview]
Message-ID: <CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com> (raw)
In-Reply-To: <54A976C3.1030805@jrn.me.uk>
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.
> 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. :)
next prev parent reply other threads:[~2015-01-04 17:35 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 [this message]
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
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='CAAS2fgTxwD2GJ-n+d=ovEYWCxpwyPO_DMBguP_ioc+_cdEhW=w@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jrn@jrn$(echo .)me.uk \
/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