I get an assertion failure line 436 with kernel.cpp expression pindex-> pprev||pindex-> getblockhash()==(!if testnet? hashGenesisBlock:hash GenesisBlocktestnet
Happens when I try to open the wallet., reinstall didnt seem to make a difference to a new directory.. thoughts?
so it sounds like your block index is corrupted goto the Application data directory, delete blk0001.dat, the leveldb folder, the database folder, and the blkindex.dat file |
|
|
|
Wallet Links v2.0.1.0: This includes numerous bug fixes and Security Checkpoints. |
|
|
|
Hmm... Seems I do have a problem with the latest wallet bitcointalk.org/index.php?topic=755180 That one (2.0.0.1) will start for me. But the process then disappears after a while... No error or warning either. Just disappears :/ Any suggestions for me?  I followed instructions, even started with fresh wallet! Devvie I have a beta build out with a couple more bug fixes. Though some information gathering, OS, Manual or Auto Install, and it just stops? |
|
|
|
Im curious as to why this site only has XST and SSD? Probably because they are the only two certified so far. Site just launched today |
|
|
|
       01 / DEVELOPER ID VERIFICATION
We begin with a rigorous identity verification of the lead developers. Identity verification is a multi-step process that involves written and/or verbal communication, video chat and legal proof of identity, such as notarized identity verification. We ensure that only identified developers have access to code repositories.  02 / CODE REVIEWIdentifed developers are then eligible for a complete code review wherein our cryptocurrency experts look for anomalies related to the money supply, such as obfuscated pre-mines or post-mines. Our experts also ensure that the money supply will stay within limits specified by the coin developers, and identify any potential bugs found during review.  03 / TESTING AND BUILDINGOur development team then builds the wallet code as a deployable Microsoft Windows application and tests for basic wallet operations and networking. Part of the testing process includes a blockchain analysis to verify that coin production meets specifications in terms of money supply and block times. We also provide similar services for Mac OS X and Linux deployment.  04 / ELECTRONIC CODE CERTIFICATIONAfter testing, we electronically sign the code using a digital certificate recognized by Microsoft, Apple, and other major software vendors. This signature ensures that the program does not change between its digital certification and deployment to your users.  05 / RATINGSFinally, as part of our process, we offer coin ratings based on identity verification, code review, testing, and whether certified wallets were used at launch. These ratings are:      |
|
|
|
Wallet Links v2.0.0.1: Includes various bug fixes. SourceFeel free to build from source. Questions Comments Concerns lemme know. Enjoy |
|
|
|
|
if you are using a new wallet and a new address it will only have to index a single transaction with the wallet since you wont have the previous address history. This is why it is going to take less time.
|
|
|
|
Bittrex down for wallet maint, easiest fix seems to be 1) install latest wallet onto new machine, send coins there, uninstall from old machine, remove wallet, reinstall, resend coins back to first reinstalled wallet..
good to know. As stated as well will be doing one last wallet update v 2.0.0.1 will be a required update as there are some bug fixes in it. there wont be any db re-indexing so should be a quick replacement |
|
|
|
|
Sounds good to me I will be pushing one final update out with checkpoints, some changes to clean up the code, and most importantly fix a bug in the lock code which wasn't fully locking the wallet back up. Also Bittrex wallet is back up and running again.
|
|
|
|
|
Uploading a patch now for anyone still having issues. Just need to extract to wherever you installed sonicscrewdriver at before.
|
|
|
|
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. |
|
|
|
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 |
|
|
|
|
Coin age resets whenever coins remove, sadly
|
|
|
|
|
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.
|
|
|
|
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?
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 |
|
|
|
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. |
|
|
|
UPDATED Windows QT's Manual InstallAuto InstallIf you are having issues with random closes this should fix it. OP Has been updated with correct Links |
|
|
|
did you just copy over the preexisting folder or did you make a new folder? made new folder. resync. it works for hour now. looks like its goodcrashed again. now its opened and staking did you run it with -debug? Also new Windows build incoming with no static libraries sometimes openssl is finicky ok. now its runned with -debug will waitThank you, I think the issue may be a difference between the openssl dll's and the static library its trying to run fro. so rebuilding and then we shall see. |
|
|
|
|
Show Posts
That's great news!
