I think it’s the same problem if you rehash the block chain completely without wallet.dat. Transaction time stamps are stored in the wallet.dat.
Using priv key (and not wallet.dat) won’t give you correct time stamps.[/quote]
Thanks.
I probably was not clear in my original post. What I meant was - If you do a clean install of 0.24.2 w/o backup and restore of wallet.dat, you end up with a fresh, empty, wallet.dat. Then if you “load” your coins into it via importprivkey, I think the coin-days will be dated from whenever the blockchain syncs up. Just like what happened to me with Peerunity. I’m only bringing this up because I seem to fail at the backup/restore with 0.24.1. I discussed this at length in the ‘sticky’ Peerbox thread, about page 13.
[quote=“willywithcoinnode, post:22, topic:3077”]Alright.Coin age is not necessarily determined by your client.
Search for your address in a good blockexplorer (http://peerchain.co/ e. g.) and you’ll see that your coin age is unaffected by your priv key import.[/quote]
Well, again, though. Why is it that coins that were transferred to my address nearly a week ago show with 1 day of age in Peerunity? The transaction shows in the blockexplorer back then, but the age didn’t start until Peerunity synced.
Edit: A quick little cut-n-paste of the dates: Blockexplorer shows the transaction on 14 Dec 2014 19:18:36, Peerunity claims 12/18/14 10:02 as the date and time. And Peerunity is using that date for eligibility for minting - or so it says!
Edit2: Also, over on the “Minting” tab where the transactions are highlighted in different colors depending upon their age/eligibility, it is blue with an age of 1.
[quote=“badgolfer, post:16, topic:3077”]I’d like to update, but am unsure how to back up my wallet. As I’ve mentioned before, with my current version (0.24.1??), writing to the USB doesn’t seem to work. I follow the instructions to the letter, but when I inspect the USB in Windows, the wallet.dat file is not there. But in a directory on raspi instead.
Ideas? Or should I just go ahead and flash 0.24.2 and redo importprivkey, and then do ppcoind encrypt (how I ended up doing it previously)?
Edit: Going the importprivkey route seems to reset coin-days, as it appears that that info is contained in wallet.dat. I found this out when I had some PPC sent to a Peerunity address while Peerunity was not running. Upon restarting Peerunity a week or so later, the new transaction finally showed after the blockchain re-sync’d, but with an age of “0”.[/quote]
It should be very easy. I have never used it but seeing screen-shots of the app it looks about the same.
Just try it, enter google-authenticator setup and try importing keys.
