Re: [ANN] Diamond (DMD) Evolution v 2.0 | NEW wallet, 50% POS Active
So i've resynced using my old wallet and it's now showing the minted transaction i did at the end of it. However it's missing the transaction i sent to my address a few hours before the minting.
If i dump my priv key and reload the chain do i place my wallet back in the roaming folder before i sync or do i let it fully sync with fresh wallet then import my privkey afterwards?
The txid i have from cryptsy does not exist on the blockexplorer.
Is there a way of checking to see if it has been sent to the forked version?
If i dump my priv key and reload the chain do i place my wallet back in the roaming folder before i sync or do i let it fully sync with fresh wallet then import my privkey afterwards?
The txid i have from cryptsy does not exist on the blockexplorer.
Is there a way of checking to see if it has been sent to the forked version?
first of all make sure ur wallet version is at least 2.0.3.0 (soon 2.0.3.1 release can be expected)
u can sync with ur old wallet.dat
all mining minting and incomming/outgoing transactions that where orphan or done in a wrong for will after sync be visible as unconfirmed
coins stuck in such a unconfirmed transaction u can claim back by repairwallet command in console
a bit more complicated would be the methode mullick suggests (2nd level cryptsy support)
i just post it here but never tryed it myself follow his guide at own risc.
regarding TX ID thats are not visible at blockexplorer they didnt happen on main chain
if cryptsy wallet was sometime on wrong fork chain only cryptsy support answer and also the way how they plan to fix that
(resync on right chain and repeat transaction i guess...)
Quote
First try running the RPC command repairwallet. This can be done via the console in your wallet. Navigate to Help/ Debug Window / Console.
This command will look for any bad transactions but may not work as your wallet likely still sees the transactions as good
If that doesn't work a redownload of the blockchain may correct this
Lastly a fail safe method
First your going to want to dump the private key of your wallet run the command dumpprivkey followed by your address
You will want to save a copy of the key and a backup of your wallet.
Then close your client and leave it closed for some time. At least a few hours. This will give any bans you may have received from being on the bad fork time to expire
If you have a backup of your wallet.dat then go ahead and delete everything in your appdata/roaming/CoinName folder
Then restart the wallet and let it download the chain until synced
Once synced run the command importprivkey followed by your private key
This is a method I found myself. It removes all the transactions from the wallet and when its imported it can only find whats in the blockchain. So the coins you sent are no longer sent and should be in your wallet.
Let me know if this helps
Mullick
Lead Support Moderator
This command will look for any bad transactions but may not work as your wallet likely still sees the transactions as good
If that doesn't work a redownload of the blockchain may correct this
Lastly a fail safe method
First your going to want to dump the private key of your wallet run the command dumpprivkey followed by your address
You will want to save a copy of the key and a backup of your wallet.
Then close your client and leave it closed for some time. At least a few hours. This will give any bans you may have received from being on the bad fork time to expire
If you have a backup of your wallet.dat then go ahead and delete everything in your appdata/roaming/CoinName folder
Then restart the wallet and let it download the chain until synced
Once synced run the command importprivkey followed by your private key
This is a method I found myself. It removes all the transactions from the wallet and when its imported it can only find whats in the blockchain. So the coins you sent are no longer sent and should be in your wallet.
Let me know if this helps
Mullick
Lead Support Moderator
Please note you may have more than one address in your wallet!
Some addresses are created automatically by the wallet when sending and there is change remaining.
The safest way to find all of the addresses is to use the 'listaddressgroupings' RPC/console command.
You need to save the private key for each and every one of the addresses that have non-zero balance! Otherwise, you will lose those coins for good.
This is a nasty feature of the bitcoin protocol. An upcoming wallet release will have additional tools to deal with it. For now, you could use Coin Control to send the change amount to one and the same address -- but that is too much manual work and will only affect new transactions.