Bitcoin and Litecoin wallet import timestamps 1 hour off
planned
P
Past Octopus
When I import a Bitcoin or a Litecoin wallet by public address, it imports the timestamps 1 hour off. Other wallets import the times correctly.
Status
Inaccurate data (timestamp 1h off) happens for
some
older transactions (usually before 2019) and is a fault of our API provider. Since it affects only some transactions, we cannot account for this automatically. We are in contact with the API provider but so far they didn't manage to fix the data issue.This post was marked as
planned
N
Neon carrot Anglerfish
All my assets are being stolen taken without permission
Jack
Merged in a post:
Bitcoin transaction imported with incorrect time.
V
Verdigris green Frog
Blockchain explorer shows time as 11.05 UTC. I synced using public address, the txn in koinly shows 10.05.
Jacob
Hey, thanks for reaching out!
Which wallet integration did you notice the different on? Or was it all wallets?
J
Jonquil Chipmunk
Same issue here (old transactions imported via btc blockchain api using public address) one hour earlier than expected. Have tried the usual wallet delete/full resync. If I manually change times it will break in the future - most likely when tax deadlines loom and for some reason I need to full resync to fix some other issue :). Please prioritise this - its a core function! Thanks.
V
Verdigris green Frog
This is not a one off issue Previously I changed it manually but if the issue gets fixed in the future, I'll end up with more work to revert changes so am raising as a bug.
L
Linen Raven
A good example of this are transactions from BTC block:
000000000000000000064bd1a9a7d89b1fa0a197fb529de0b4110074930520dd
Koinly imports them with time "1 Apr 2020 15:35 GMT/UTC" which is incorrect.
All block explorers show it as
1 Apr 2020 16:35 GMT/UTC
Koinly claims it's their data provider giving them incorrect data.
However, I think BTC blockchain is such a fundamental piece that Koinly should keep and maintain timestamp for each BTC block themselves and make sure it's correct.
I am deliberately not including specific transaction as this is a public forum. Please look at all transaction you have on your system for this block and you should be able to find that some (or all) are imported to Koinly with incorrect date.
P
Petur
Hi Thomas,
The Bitcoin and Litecoin APIs will import all transactions in UTC times.
Could you share a sample TxHash of a transaction that has been incorrectly imported?
Or is it possible that you imported these transaction via CSV files instead of API?
P
Past Octopus
Petur: I gave up and imported via CSV. I have really old BTC/ltc addresses that were created before bip that allowed tracing of change. It could be causing the issue with the time being off too. I don't know, but it's all correct on my end now because I am using a CSV with correct times and transaction amounts. Whether there is an issue in the BTC/LTC integration and the times will up to Koinly to investigate. I'll post my BTC address tomorrow so you can investigate.