On 04/01/15 17:35, Gregory Maxwell wrote:
> On Sun, Jan 4, 2015 at 5:22 PM, Ross Nicoll <j...@jrn.me.uk> wrote:
>> Grabbing a simple test case:
>> - 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
>> 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.
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
Bitcoin-development mailing list