📅 Original date posted:2015-01-04 📝 Original message:On Sun, Jan 4, 2015 at ...

Gregory Maxwell [ARCHIVE] /

npub1f2n…rwet

2023-06-07 15:28:20

in reply to nevent1q…l39a

📅 Original date posted:2015-01-04
📝 Original message:On Sun, Jan 4, 2015 at 5:22 PM, Ross Nicoll <jrn at 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. :)

Author Public Key

npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet

Seen on

wss://relay.noswhere.com wss://relay.nostr.band

Show more details

Published at

2023-06-07 15:28:20

Kind type

1 Short Text Note

Event JSON

{ "id": "27f8a2a7f8f4124027526544ae9ad4b4c7cf18f5a8df7877b389d3f254dcd4ca", "pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73", "created_at": 1686151700, "kind": 1, "tags": [ [ "e", "c34c675aa013cba152c99a343668732650d019acd0488a1f1a5be9bc5fc8e1f8", "", "root" ], [ "e", "573625ede4b7c11ad5c47e614e16b6fd48796f4f8c17544fcbf5c916c97b6597", "", "reply" ], [ "p", "787ecd48da0d9610d322fb67c86ad23a5287d688559b2ff8ee546721fd990129" ] ], "content": "📅 Original date posted:2015-01-04\n📝 Original message:On Sun, Jan 4, 2015 at 5:22 PM, Ross Nicoll \u003cjrn at jrn.me.uk\u003e wrote:\n\u003e Grabbing a simple test case:\n\u003e https://chain.so/tx/BTCTEST/f903a31f2474df737d324c60abf2407e1cf7e052844da4ccffbfab81cf6ac1f8\n\u003e - that won't lock until 0028 UTC on the 5th.\n\u003e\n\u003e I've tried closing the wallet, moving the wallet.dat file out of the\n\u003e way, and then attempting the spend transaction (which can be locked\n\u003e immediately), and it either rejects it on acceptance to mempool, or it\n\u003e is never included in a block.\n\nCan you send me the actual raw transaction (that site doesn't appear\nhave a way to get it, only some cooked json output; which doesn't\ninclude the sequence number).\n\nAs I said, it's a severe bug if unlocked transactions are being\nrelayed or mempooled far in advance.\n\n\u003e They can only replace a non-final transaction with a final transaction,\n\nAh I missed that the replacement had to be final. Thats indeed a much\nmore sane thing to do than I was thinking (sorry for some reason I saw\nthe +1 and thought it was just checking the sequence number was\nhigher.)\n\n\u003e I don't think that's a major issue?\n\nIf they can relay the first one to begin with its an an issue, the\nreplacement just makes it twice an issue. :)", "sig": "778bafb0d1c7cc4f0d63a8df6c4c0d9962936653d51e00a477a096c0f4dc55e009c80f4af1e81b13fe8dae95fc779c49a6776f1d2d45111657370ac79f863ffb" }