Ask questionsStrange state (Timestamps wrong) after importing a priv key.

Describe the issue

After importing a private key from an old wallet, the rescan tool a long time, but after completion all Timestams belonging to transactions related to the newly imported key are wrong.

What behavior did you expect?

Show the correct timestamps of all trasactions, corresponding to the block the transaction took place.

What was the actual behavior (provide screenshots if the issue is GUI-related)?

see screenshots. The newly imported key has the label "ehemals", The big number for confirmations (in the tooltip) seems to be correct, but the timestamps all show the time of the latest transaction (lieferando) which was there at the time of import.

How reliably can you reproduce the issue, what are the steps to do so?

Have not reproduced this issue yet (because it takes sooo long). But I have observed other strange things before (data curruption, see: Issue

What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?

Bitcoin core from the ppa used on Ubuntu 17.4 (most recent, I think) Bitcoin core version: v0.15.0.0-g3751912e8e (64-Bit)

What type of machine are you observing the error on (OS/CPU and disk type)?

Ubuntu 17.04 64 bit, Quadcore CPU, 2GB RAM, HDD and SSD (for chainstate).

Any extra information that might be useful in the debugging process.

Everything else seems normal. The blockchain was freshly reindexed the 3 days before the import.(to cure the data corruption). The former issue "data corruption" was observed on a different computer, I then used a desktop computer. But I use the same (extermal) HDD.


Answer questions jb55


I think I'm hitting this issue? or is this something else? I just did a rescan on latest master as of yesterday and the dates seem wrong at a certain point (after the 2017 one). this is a descriptor wallet.

Perhaps I should try applying #12024 ?

Github User Rank List