Topic: [SSD] Sonic - 1st TOR with functional anon send - Steganography based Anon App - page 130. (Read 284913 times)
September 06, 2014, 02:50:57 AM
Uploading a patch now for anyone still having issues. Just need to extract to wherever you installed sonicscrewdriver at before.
September 06, 2014, 02:00:15 AM
Has anyone found their windows qt client keeps crashing after starting ok and being left to run? widows says it stopped working and it closes.
Haha, that's what we've been talking about for a few pages.
Solution:
For anyone reading, his solution was correct. Obviously, backup your wallet before making any changes to it.
Create a new address. Send the balance (maybe break it into smaller payments if it's a huge balance) of your wallet to that address. Go to help->debug. Go to console. dumpprivkey youraddress. Copy that into a txt file. Backup that wallet and move it out of your appdata/roaming/sonicscrewdriver folder. Start wallet with no wallet.dat. Go to help->debug->console. importprivkey yourprivkey.
That should work.
edit: If that's too complicated and you're tech unsavvy, you can just send the coins to bittrex and then create an address with your supersonic 2.0 client and then send them to your new wallet address. Send a small amount to bittrex first to test.
September 06, 2014, 01:55:37 AM
Has anyone found their windows qt client keeps crashing after starting ok and being left to run? widows says it stopped working and it closes.
September 06, 2014, 01:43:25 AM
Coin age resets whenever coins remove, sadly
I just did some more investigating. It looks like there is indeed some incompatibility between the old SSD private keys and the new wallet (unless I just didn't wait long enough). I was unable to import my old private key into my new wallet, but when I created a new address and sent coins to it like you suggested, I was able to import that key instantly.
So, are we going to try to get everyone to move their coins to an address generated by the new wallet (before 9/10 gets here) or are you going to change the source?
For anyone reading, his solution was correct. Obviously, backup your wallet before making any changes to it.
Create a new address. Send the balance (maybe break it into smaller payments if it's a huge balance) of your wallet to that address. Go to help->debug. Go to console. dumpprivkey youraddress. Copy that into a txt file. Backup that wallet and move it out of your appdata/roaming/sonicscrewdriver folder. Start wallet with no wallet.dat. Go to help->debug->console. importprivkey yourprivkey.
That should work.
edit: Another thing. We should maybe somewhat coordinate this as we have to wait 3 days before we're able to stake again. If you have a large balance, maybe send some of your balance today and the rest of 9/8 or something like that.
There is no incompatibility between the privatekeys, If anything there is a difference between the wallet formats. If you had waited for it to index all your transactions and then closed and reopened your wallet you would see that it had moved from the address book to the receive addresses.
When I first started testing I had my old wallet that I was still using. I changed cause it took forever for it to go through each transaction and see how it was related to mine.
Oh, okay. I'll try again.
September 06, 2014, 01:29:44 AM
Coin age resets whenever coins remove, sadly
I just did some more investigating. It looks like there is indeed some incompatibility between the old SSD private keys and the new wallet (unless I just didn't wait long enough). I was unable to import my old private key into my new wallet, but when I created a new address and sent coins to it like you suggested, I was able to import that key instantly.
So, are we going to try to get everyone to move their coins to an address generated by the new wallet (before 9/10 gets here) or are you going to change the source?
For anyone reading, his solution was correct. Obviously, backup your wallet before making any changes to it.
Create a new address. Send the balance (maybe break it into smaller payments if it's a huge balance) of your wallet to that address. Go to help->debug. Go to console. dumpprivkey youraddress. Copy that into a txt file. Backup that wallet and move it out of your appdata/roaming/sonicscrewdriver folder. Start wallet with no wallet.dat. Go to help->debug->console. importprivkey yourprivkey.
That should work.
edit: Another thing. We should maybe somewhat coordinate this as we have to wait 3 days before we're able to stake again. If you have a large balance, maybe send some of your balance today and the rest of 9/8 or something like that.
There is no incompatibility between the privatekeys, If anything there is a difference between the wallet formats. If you had waited for it to index all your transactions and then closed and reopened your wallet you would see that it had moved from the address book to the receive addresses.
When I first started testing I had my old wallet that I was still using. I changed cause it took forever for it to go through each transaction and see how it was related to mine.
September 06, 2014, 01:17:47 AM
i have had my coin in my wallet for 2 week now , and not once have i got any staking coin
you should also check if your wallet is locked or not for you cannot stake with a locked wallet
September 06, 2014, 01:10:17 AM
i have had my coin in my wallet for 2 week now , and not once have i got any staking coin
Weird. How many coins do you have? Difficulty is quite high so if you have considerably less than 10,000, there's a good chance you wouldn't have staked anything yet.
edit: Also, what block are you on? You should be on the most current block from here: http://explorah.net/ssd/
Do you see that small blue light near the top that means you're staking?
September 06, 2014, 01:09:48 AM
i have had my coin in my wallet for 2 week now , and not once have i got any staking coin
September 06, 2014, 12:53:00 AM
Coin age resets whenever coins remove, sadly
edit: If you were using a pre 2.0.0.1 client (current client is 2.0.1.0), the easiest way to correct the problem is to send your coins to bittrex. (Send a small amount to test first.) Then create a new wallet with the newest client. Then send the coins from bittrex to your new wallet address.
September 06, 2014, 12:05:22 AM
Coin age resets whenever coins remove, sadly
September 06, 2014, 12:03:25 AM
Ok one last thing to try,
Make new address, send everything to that address,
dumpprivkey for new address.
close qt, and move wallet.dat to new location.
open qt, import privkey.
watch it and tell me if it errors out.
Make new address, send everything to that address,
dumpprivkey for new address.
close qt, and move wallet.dat to new location.
open qt, import privkey.
watch it and tell me if it errors out.
I think you could be right that it's the old wallet with the new client. For some reason, the address where I received all my coins wasn't even listed in the receive coins tab. I'm not sure if I originally created a new one or just sent them to the old default one.
I got an address from a clean wallet and sent some coins there. I'll let it sit for a few days and see if there are any problems. If I follow your instructions and send some coins to an address my (possibly bad) wallet generates, would they maintain coin age for some reason? Is that why you suggested to do it that way?
September 05, 2014, 11:11:21 PM
i get this
Oh, hell yeah. Wallet problems!
Time to score some cheap SSD.
Take your time dev.
W00t!
September 05, 2014, 11:01:21 PM
Ok one last thing to try,
Make new address, send everything to that address,
dumpprivkey for new address.
close qt, and move wallet.dat to new location.
open qt, import privkey.
watch it and tell me if it errors out.
Make new address, send everything to that address,
dumpprivkey for new address.
close qt, and move wallet.dat to new location.
open qt, import privkey.
watch it and tell me if it errors out.
September 05, 2014, 10:24:54 PM
How long is it supposed to rescan for?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
TBH I would say both can take the same amount of time. This is due to salvagewallet going through each transaction and making sure they are valid. and dump/import is just going to take all your transactions from the blockchain and credit them as it goes
Same problem after running salvagewallet unfortunately. Windows 8.
September 05, 2014, 09:25:15 PM
How long is it supposed to rescan for?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
TBH I would say both can take the same amount of time. This is due to salvagewallet going through each transaction and making sure they are valid. and dump/import is just going to take all your transactions from the blockchain and credit them as it goes
September 05, 2014, 09:20:25 PM
How long is it supposed to rescan for?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
Do you think it would be better to dump my private keys and import them into a fresh wallet?
September 05, 2014, 08:29:34 PM
UPDATED Windows QT's
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
If we aren't having issues, do we still need to update?
Also, this is probably the most promising recent coin and it's still flying under the radar. Did everyone contact cryptsy, mintpal, and poloniex?
You do not need to but best practice says yes you should. Also if the problem persists there is one last thing to try, that would be to launch the qt via command line or shortcut with the -salvagewallet switch. This will make sure all transactions are correct in the wallet.dat itself.
Mine actually did crash a few hours ago. I just wasn't paying attention to that computer. Updated quickly and no problems so far.
edit: Spoke too soon. Started with salvagewallet. I'll see if that does anything.
September 05, 2014, 08:15:45 PM
UPDATED Windows QT's
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
If we aren't having issues, do we still need to update?
Also, this is probably the most promising recent coin and it's still flying under the radar. Did everyone contact cryptsy, mintpal, and poloniex?
You do not need to but best practice says yes you should. Also if the problem persists there is one last thing to try, that would be to launch the qt via command line or shortcut with the -salvagewallet switch. This will make sure all transactions are correct in the wallet.dat itself.
September 05, 2014, 08:12:14 PM
UPDATED Windows QT's
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
If we aren't having issues, do we still need to update?
Also, this is probably the most promising recent coin and it's still flying under the radar. Did everyone contact cryptsy, mintpal, and poloniex?
September 05, 2014, 07:56:31 PM
UPDATED Windows QT's
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
OP Has been updated with correct Links
Manual Install
Auto Install
If you are having issues with random closes this should fix it.
OP Has been updated with correct Links
Jump to: