Nostr Web Client

While briefly staring at my mempool, I noticed that some transactions got rejected because their locktime was based on a freshly mined block, which my node hadn't seen yet. Even several minutes later my mempool doesn't have it.

nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 did pick it up, presumably because it saw the block earlier? https://mempool.space/tx/8c235cb0eb540ed75aeebca5d3beeb0c0d968b8590b1ddf31ed87f997e2ea3b8

I wonder if it gets added later as other peers tell me about it again.

Reply to this note

Please Login to reply.

Discussion

fiatjaf 2y ago

Maybe blocks are too big.

fiatjaf 2y ago

Wait, but shouldn't these transactions be valid either way if you had their parents in your mempool already?

Sjors Provoost 2y ago

I think I linked to the wrong example. Though it's a similar phenomena. This one got rejected for being in a too large unconfirmed chain:

2023-08-18T09:27:32.705237Z [net] got inv: wtx 8c235cb0eb540ed75aeebca5d3beeb0c0d968b8590b1ddf31ed87f997e2ea3b8 new peer=50

2023-08-18T09:27:32.706424Z [net] Requesting wtx 8c235cb0eb540ed75aeebca5d3beeb0c0d968b8590b1ddf31ed87f997e2ea3b8 peer=50

2023-08-18T09:27:33.912485Z [mempoolrej] 8c235cb0eb540ed75aeebca5d3beeb0c0d968b8590b1ddf31ed87f997e2ea3b8 from peer=50 was not accepted: too-long-mempool-chain, too many descendants for tx cca29e4a3f560b3414e47feede6de0c2d9cb94af535780479e531f14bd003395 [limit: 25]

The chain was too long from the point of view of my node, because it hadn't seen the confirmations yet.

MrMiaggy 2y ago

I can’t wait for a time when “While briefly staring at my mempool….” replaces, “this one time at band camp…” 😌

Sjors Provoost 2y ago

Wrong example, I meant this one: https://mempool.space/tx/56a76f8a056de85bee7f46b7b05cd62972b34dd6631526ebbac99d76f587a564

From my log:

2023-08-18T09:27:31.644274Z [mempoolrej] 56a76f8a056de85bee7f46b7b05cd62972b34dd6631526ebbac99d76f587a564 from peer=40 was not accepted: non-final

Sjors Provoost 2y ago

Eventually my node got the transaction anyway, because it was mined.

2023-08-18T09:36:23.506105Z Saw new header hash=00000000000000000002aa586c441bb575a4d9d51c94fa8182f0c44758479fc9 height=803739

2023-08-18T09:36:23.506194Z [net] Requesting block 00000000000000000002aa586c441bb575a4d9d51c94fa8182f0c44758479fc9 from peer=69

2023-08-18T09:36:28.294225Z [net] received block 00000000000000000002aa586c441bb575a4d9d51c94fa8182f0c44758479fc9 peer=69

2023-08-18T09:36:29.247778Z UpdateTip: new best=00000000000000000002aa586c441bb575a4d9d51c94fa8182f0c44758479fc9 height=803739 version=0x2e648000 log2_work=94.366442 tx=880923786 date='2023-08-18T09:36:12Z' progress=1.000000 cache=112.3MiB(840196txo)

(sadly not received as a compact block)