Quote from: arteleis on December 24, 2014, 09:45:50 PM

Quote from: Thistleblower on December 24, 2014, 05:26:34 PM

The curious incident of the coins in the night-time.

I sent some coins to an empty wallet using the previous version of the software.
They failed to arrive, although the send was confirmed many times.
Cutting a long story (and many hours of frustration) short...

The destination wallet.dat was created using the previous software, but running in the new software with a fresh download of the blockchain. It was empty before the upgrade.

As a final resort I copied the destination wallet.dat to the machine running the previous software, and placed it in the silk data folder.
When it eventually synchronised the coins appeared. They were still not showing in the same wallet.dat running with the latest version.
So I copied the destination wallet from the machine with the previous version to the machine running the current version.
Having registered with the wallet.dat under the previous version... the coins were now present and correct under the new version.
So I have Two Copies of the same wallet.dat (created with the previous version and containing the same addresses).
One copy was empty when I upgraded to the latest software and refuses to see coins sent to addresses in that wallet.
The other copy was empty until I ran it using the previous software, when it registere receipt of the coins.
The sending wallet was running under the old software.

The coins sent to this wallet.dat will not register under the latest software until they have registered with the software version that created it.

I have not conducted any more tests, but it would seem that the addresses in a wallet created by the previous software need to be initialised by receiving coins under that version before they will function correctly with the new version. The copy that has not been running under the previous version (since the coins were sent) is still reporting that it is empty under the new version.

This could cause compatibility issues with upgrades, so I'm hoping that the team will investigate. Sorry about the longwinded account.

hmm why did you use an empty wallet.DAT from old in new then send old coins to old wallet in new client? lol that's some kind of riddle..

As explained in a previous post, I used to clean up my wallets by sending coins to a fresh wallet. I had one set up when the upgrade was issued so I used it with the new software and a fresh copy of the blockchain rather than setting up a new wallet from scratch. No orphans, redundant receiving addresses, or fragmented staking.

personally I just kept my old wallet while running the new beta exe.

have you checked wallet for any mismatched coins?
kinda sounds like using 2 different wallet.dats with different balances on 2 different versions might cause issues lol

The same Wallet.dat on two different versions. When the coins didn't arrive I tried numerous remedies before I thought of copying the wallet back into the old software which generated it. The coins arrived when I opened the wallet with the old software, and when I switched That copy to the new software they were fine. But I still have a copy of the same wallet that has not been used with the old software since the coins were transferred. This copy will not register the coins.

Try it for yourself.
Have a sending wallet running with the old software. Generate a new receiving wallet using the old software, and then run it using the new software. Send some coins to the receiving wallet and wait for them to arrive. If they don't, then copy the receiving wallet.dat to the machine running the old software and see them arrive. Then copy the receiving wallet back to the machine running the new software having first made a backup copy of of the wallet.dat that refused to see the coins. The copy that's been run through the old software should contain the coins from the sending wallet... but the copy that hasn't been run through the old software will refuse to do so.

The addresses in Both copies are identical. So why won't the copy that hasn't

It's an obscure but interesting scenario that only cane to light by accident. It 'might' have an impact on upgrades if an old wallet.dat is used (as frequently happens) with upgraded software. It only seems to affect wallets that have not been used at all before an upgrade, but I haven't investigated in greater depth. If it affects receiving addresses that haven't been used prior to the upgrade then there could be more serious ramifications... particularly after a hard fork, when 'fixing' the wallet by running the software that generated it is no longer an option.

It may well be an issue that affects other coins. I'll look around for some with recently upgraded wallets and give it a try. I now have both versions of silkcoin set up on one machine, each with it's own copy of the blockchain (not using default locations). You can't run them together because of a conflict accessing ports, but they run quite normally using either/or.

unless you talking about two different computers then this might make more sense.

you in silkchat? welcome to pm me and we can talk more.
sooo is there missing coins? I'm sorry couldn't really find for sure if that was the case in the post, lol but its christmas eve and Santa has rum haha

Thistleblower

Posts

Merits