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.
mempool (npub18d4…6lt3) 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.
provoost / Sjors Provoost
npub1s6…dwk4c
2023-08-18 09:36:50
Author Public Key
npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4cPublished at
2023-08-18 09:36:50Event JSON
{
"id": "c91c65e36d1f6be16c00d76fce48f6e27d8dcc2e05fc80fd6b0fae23e2c2e9ca",
"pubkey": "8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8",
"created_at": 1692351410,
"kind": 1,
"tags": [
[
"p",
"3b6a3d3bb3358836a64d1c80292b96e7698ec35a2e5ca451defa6bd3af3eeb84",
"",
"mention"
]
],
"content": "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.\n\nnostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 did pick it up, presumably because it saw the block earlier? https://mempool.space/tx/8c235cb0eb540ed75aeebca5d3beeb0c0d968b8590b1ddf31ed87f997e2ea3b8 \n\nI wonder if it gets added later as other peers tell me about it again.",
"sig": "7a7590ea0897d851d6bdaad964be623339424e05cb9657dde09dfa7b59ce5f87dc462052bea5e116cdca9cb9651924a13764cbe842989d8928be906e9c678010"
}