After importing private keys, the client shows the wrong date for past transactions by that key. They will show the import-date instead of the real date they took place.
Importing private keys results in wrong TX-dates #3140
issue kroese opened this issue on October 24, 2013-
kroese commented at 7:33 AM on October 24, 2013: none
-
Diapolo commented at 12:32 PM on October 24, 2013: none
AFAIK this is a known problem or at least "how it works".
-
laanwj commented at 12:38 PM on October 24, 2013: member
Yes, but I couldn't find a duplicate issue for it. In principle nowadays we store three dates for a transaction. The creation date, the block chain date, and a "smart date" that's sometimes the one sometimes the other. Not sure which one -qt shows actually.
-
qubez commented at 5:04 PM on December 12, 2013: none
This appears closeable, or at least not reproducible. In 0.8.6 Win32, transactions (from 2012) indicate the correct block timestamp after the address is imported.
- laanwj closed this on Dec 12, 2013
- Bushstar referenced this in commit 4112414710 on Apr 8, 2020
- MarcoFalke locked this on Sep 8, 2021
Labels