tungfa
Legendary
 Offline
Activity: 1834
Merit: 1023
|
 |
December 23, 2014, 02:48:50 PM |
|
|
|
|
|
|
|
Terzo2
|
|
December 23, 2014, 02:54:46 PM
Last edit: December 23, 2014, 03:26:12 PM by Terzo2 |
|
I'm hunting for dumping pigs ! They will be shot at sight !
|
|
|
|
|
coins101
Legendary
Offline
Activity: 1456
Merit: 1000
|
|
December 23, 2014, 03:18:09 PM |
|
knowing Kristov this is either an excellent app just for the sake of it, or a way to track users  |
|
|
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:19:54 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
|
|
|
|
Nthused
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
December 23, 2014, 04:21:56 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
Have you tried using -rescan ? It seems like it wasn't broadcasted. BTW if you deleted your wallet.dat file and didn't make a backup then it is gone for good... |
|
|
|
|
eduffield (OP)
Legendary
Offline
Activity: 1176
Merit: 1036
Dash Developer
|
|
December 23, 2014, 04:23:02 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
Have you tried using -rescan ? It seems like it wasn't broadcasted. or --zapwallettxes |
Dash - Digital Cash | dash.org | dashfoundation.io | dashgo.io
|
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:23:18 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
Have you tried using -rescan ? It seems like it wasn't broadcasted. Can you elaborate please? -rescan on the debug console on A? |
|
|
|
Nthused
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
December 23, 2014, 04:25:01 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
Have you tried using -rescan ? It seems like it wasn't broadcasted. Can you elaborate please? -rescan on the debug console on A? You can add it to the end of your .bat setup Just open CMD prompt, drag over the Darkcoin-Qt.exe and then press spacebar (so it can have 1 gap) then type -rescan "or" --zapwallettxes |
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
December 23, 2014, 04:29:04 PM |
|
Hello darkers, I think something really bad happened to me.
Had to move my 1005DRKs from A to B.
It was the first time I opened the wallet on B, so it generated the keys and dled the blockchain as well. I sent 1DRK for testing from A and it arrived to B.
Then I proceeded with the 1005 payment (used the same destionation adress) and it has been stucked @0 confirmation, so I closed and reopened the wallet on B.
The bad thing is that the wallet generated the keys and dled the blockchain again as it was the first time been opened (using the .zip download from darkcoin.io). I didn't make a backup tho, so no way I can the destination address on my wallet again, amirite?
The payment is still @0 confirmations, transaction id is d8fbedf74271cc704b8bc3fadd664a9a98afa02a165d7c878999a4057478e1b8 .
Is there any way to recover this?
So you are saying somehow the wallet.dat file disappeared? And now it made a new one? I don't know how that could happen! Do you remember anything else that might have happened? ^^^I agree with above ^^^  |
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d |
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:33:42 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
December 23, 2014, 04:35:34 PM |
|
It sometimes takes a long time for the first confirmation to come around. If you closed the first wallet before you had a confirmation, the TX may not have been broadcasted. If you zap the transactions per above (--zapwallettxes) you can start all over again. And save the wallet.dat file WITH encryption (that you wrote down!!!) before sending the funds. At that point, keep the old wallet open long enough to broadcast And don't open the original wallet until you do a zapwallettxes! bat file: ./darkcoin-qt.exe --zapwallettxes save as start.bat and make sure that notepad is set to save as (pull down menu) *all files* |
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d |
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:39:05 PM |
|
It sometimes takes a long time for the first confirmation to come around. If you closed the first wallet before you had a confirmation, the TX may not have been broadcasted. If you zap the transactions per above (--zapwallettxes) you can start all over again. And save the wallet.dat file WITH encryption (that you wrote down!!!) before sending the funds. At that point, keep the old wallet open long enough to broadcast And don't open the original wallet until you do a zapwallettxes! Now it has 1confirmation. Too bad I do not have the wallet.dat (planned to backup after the funds been received) nor the destination address, I tried both --zapwalletxes and -rescan (they are the same command, arent they?). |
|
|
|
AzzAz
Legendary
Offline
Activity: 1030
Merit: 1006
|
|
December 23, 2014, 04:40:29 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
Maybe I am a bit paranoid: could that be somebody hacked your second wallet an erased it than started instalation again and left it that way? |
|
|
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:42:17 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
Maybe I am a bit paranoid: could that be somebody hacked your second wallet an erased it than started instalation again and left it that way? Uhm the odds are close to 0 cause it is an encrypted fresh new windows install, it has less than 2hours of life. |
|
|
|
Nthused
Legendary
Offline
Activity: 1554
Merit: 1001
|
|
December 23, 2014, 04:43:48 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
Maybe I am a bit paranoid: could that be somebody hacked your second wallet an erased it than started instalation again and left it that way? Uhm the odds are close to 0 cause it is an encrypted fresh new windows install, it has less than 2hours of life. I'm pretty sure he said after the funds weren't received he deleted the Blockchain and Wallet.dat but didn't save it prior to doing so. If that is the case then the Funds on that address are gone forever  |
|
|
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:46:08 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
Maybe I am a bit paranoid: could that be somebody hacked your second wallet an erased it than started instalation again and left it that way? Uhm the odds are close to 0 cause it is an encrypted fresh new windows install, it has less than 2hours of life. I'm pretty sure he said after the funds weren't received he deleted the Blockchain and Wallet.dat but didn't save it prior to doing so. If that is the case then the Funds on that address are gone forever Lol but why on earth the wallet deleted the blockchain and wallet.dat? |
|
|
|
AzzAz
Legendary
Offline
Activity: 1030
Merit: 1006
|
|
December 23, 2014, 04:46:14 PM |
|
Thank you for the reply, the wallet did the rescan but the destination address is not listed.
Maybe I am a bit paranoid: could that be somebody hacked your second wallet an erased it than started instalation again and left it that way? Uhm the odds are close to 0 cause it is an encrypted fresh new windows install, it has less than 2hours of life. I'm pretty sure he said after the funds weren't received he deleted the Blockchain and Wallet.dat but didn't save it prior to doing so. If that is the case then the Funds on that address are gone forever right, WHO deleted the Blockchain ? |
|
|
|
|
TanteStefana2
Legendary
Offline
Activity: 1260
Merit: 1001
|
|
December 23, 2014, 04:46:38 PM |
|
No, --zapwallettxes would delete any unconfirmed payments. -rescan or -reindex (not sure if they're different) would redownload the blockchain. I can't see how you lost your original wallet.dat! Could you have deleted it (check trash) Could you have moved it? A new one wouldn't be created unless the original was renamed or removed.
Still, it's important to make everything secure before you ever send funds.
1. get the wallet address's key, print it out and keep it on a jump drive encrypted in a zip.
2. encrypt your new wallet
3. make backups of your wallet.dat, I also encrypt these in a zip. I have a standard passphrase my hubby and children know for this.
4. send 1 coin (like you did) to make sure it arrives ok.
5. send the rest of the coins.
Please look for any wallet.dat files, rename them so you can be sure you're not getting confused, then check them one at a time to see if one might be the correct one.
|
Another proud lifetime Dash Foundation member My TanteStefana account was hacked, Beware trading "You'll never reach your destination if you stop to throw stones at every dog that barks."Sir Winston Churchill BTC: 12pu5nMDPEyUGu3HTbnUB5zY5RG65EQE5d |
|
|
AzzAz
Legendary
Offline
Activity: 1030
Merit: 1006
|
|
December 23, 2014, 04:48:04 PM |
|
and, maybe antivirus deleted wallet.dat?
|
|
|
|
|
xxxgoodgirls
Legendary
Offline
Activity: 1092
Merit: 1001
|
|
December 23, 2014, 04:50:18 PM |
|
No, --zapwallettxes would delete any unconfirmed payments. -rescan or -reindex (not sure if they're different) would redownload the blockchain. I can't see how you lost your original wallet.dat! Could you have deleted it (check trash) Could you have moved it? A new one wouldn't be created unless the original was renamed or removed.
Still, it's important to make everything secure before you ever send funds.
1. get the wallet address's key, print it out and keep it on a jump drive encrypted in a zip.
2. encrypt your new wallet
3. make backups of your wallet.dat, I also encrypt these in a zip. I have a standard passphrase my hubby and children know for this.
4. send 1 coin (like you did) to make sure it arrives ok.
5. send the rest of the coins.
Please look for any wallet.dat files, rename them so you can be sure you're not getting confused, then check them one at a time to see if one might be the correct one.
No I just closed the destination wallet for a second before having the 1st confirmation and opened it again. At the open it generated all the keys and dled the blockchain again. I correctly closed the wallet, no crash or whatever. |
|
|
|
|
