I DO REMEMBER entering ONLY one Pay to address which is output 1 below "address" : "DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4" // change address, where the hell it got from, nobody knows, you need or dev team at least to figure out what are possibilities it got here due to my computer virus, glitch, memory misplacement, other core clients running simultaneously and using wallet files without me entering it ,that is deep subject to begin, without coming from dogecoin wallet.dat private key pool. So the only way your coins got sent to that address was by either you specifying that address on the "Custom change address line" in the send window, or actually having specified it as a Pay to: address. The question is can you remember from where you got that address that you decided to use it as a watchonly address?Īlso afaik, when you are sending coins, the wallet will never use a watchonly address as a "change address" (when you don't specify one).
However this address doesn't "belong" to your wallet, it exists from another wallet (hopefully you have access to). In other words you used the command importaddress DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4 "" true from the console. Tells me that at some point you imported the DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4 address to your current wallet, that's what "iswatchonly : true" means. "address" : "DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4", validateaddress DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4 I do no have such address DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4 after I did dumpwallet and printed to find it. I did not do anything with wallet.dat except encrypted it with new passphrase since I restored it from unencrypted usb flash which I kept it as a back up. PS: I Synchronized it completely and than re-index it with no luck to show balance correct.
BACK UP DOGE WALLET TO DOGECOIN CORE WINDOWS 10
I have windows 10 (64bit) with Dogecoin Core QT 1.10 walletĪfter I made 2 transactions ( wallet was not entirely completed to sync ) 00, wallet made other 2 transactions for no reason Īmount I sent only 100000 6f11ae8637c6b4232aee40e0a0f31d605c54c393ab53007fa744a97f8e2747b3-001
0 kommentar(er)
