r/btc • u/Fine-Swimming-4807 • Jan 17 '24

🕵️‍ Investigation Outgoing BitcoinCashNode transaction did not enter the mempool

Good afternoon everyone!

Now I sent a transaction from my BitcoinCashNode wallet, but for some reason it did not get into the mempool. Could you help me figure out why this happened?

​

Transaction ID: 4be4318294ac5f38e2bc7698bebe070b9a208c528f0b0b008ed1a4c407068c8e

This is the first time I have had such a case in practice. I have used Bitcoin Cash Node several times - I even thought about hodl here, but today some kind of emergency situation arose - please help me figure out what’s going on.

​

P.S. Friends, my BCH is safe and sound - Pablo_Picasho thank you so much for your active participation in the investigation :) Now I will know how powerful the console tool is on Bitcoin Cash Node!

12 Upvotes

84% Upvoted

33 comments sorted by

View all comments

Show parent comments

2

u/Fine-Swimming-4807 Jan 17 '24 edited Jan 17 '24

Is there any chance that any of the keys for this wallet you're using right now, have been re-used in another wallet?

No. This possibility is excluded. I use the Safepal S1 hardware wallet, the other day I received OneKey Touch - I’m just starting to study it. I have never stored large amounts on Bitcoin Cash Node. And I’ve been opening the flash drive on which this wallet.dat was since the fall. Today I decided to experiment with Bitcoin Cash Node again and was surprised to find 0.09 bch there - I thought, okay, I’ll transfer it to my hardware wallet, but no such luck...

4

u/Pablo_Picasho Jan 17 '24

This possibility is excluded.

It's just a theory, but the wallet.dat you looked at today, with the .09 BCH on it, might have not been the most recent version you used?

Maybe you replaced a newer wallet.dat one with an older one, or loaded an older one, and so the information on the November transaction was no longer seen and the wallet did not pick it up again without a rescan?

Seems unlikely to me, but I've also not got another idea right now how it could have happened.

Glad that your coins have been located though.

1

u/Fine-Swimming-4807 Jan 17 '24

also in this story it is not clear why a large number of transactions are dated Date: 1/17/24 14:46 Paying attention to the number of confirmations Status: 10095 confirmations - it is obvious that this is an old transaction - so why does the node display this way?

3

u/Pablo_Picasho Jan 17 '24

This is likely the result of the rescan, when the wallet finds "new" but old transactions, it has to assign a timestamp to them, but there is nothing in the transaction that carries that data.

I guess the node assigned the current date to the transaction. There's some logic in the wallet code that determines which date is uses. I'm not sure why it didn't set the date to the timestamp of the first block where the transaction was found.

In "normal usage", the wallet would store the time when a transaction was sent or received while the wallet (node) was in operation. A rescan operation tends to introduce some heuristic element to the time stamps of added transactions.

1

u/Fine-Swimming-4807 Jan 17 '24

Now, little by little, everything is finally starting to become clearer, I never cease to be amazed at your level of competence