Stealth 1.0.4.1 beta Wallets
Source: https://github.com/StealthSend/Stealth/Windows: https://drive.google.com/file/d/0B8rWObF4xz1YWDd6Y2owRVJxRXM/edit?usp=sharingMac: https://drive.google.com/file/d/0B8rWObF4xz1YeGpyRDVmQUZKS1U/edit?usp=sharingThese
beta wallets should fix the worst sync issues. They require 3 restarts during sync, all about 1 minute apart. These restarts probably have more to do with the network than the actual client or blockchain. I am testing workarounds to restarting, but I haven't found an acceptable workaround yet. The good news is that I have tested the 1.0.4.1 clients extensively and they seem very well behaved.
If you test these
beta wallets, please report any issues you have syncing and post your debug.log file if possible, using pastebin, google drive, dropbox, mega, or some other service. Thanks to the several users who have helped in this way, including prix and BTCwriter.
Also, these beta wallets have a mint spacing adjustment proposed by prix that sleeps the minting thread for 60 seconds after the client mints a new block. The rest of the wallet functions should be unaffected, so you can still send transactions and accept new blocks from the network while you are staking coins.
How to sync a wallet.Unless you have a real problem with your wallet, you can probably just restart your client using the beta release, but if you want to sync a fresh chain, then continue on and follow all of the steps.
- First, find your "StealthCoin" application data folder (in your roaming folder on Windows and in "Library/Application Support" on Macs).
- Edit or create a plain text file called "StealthCoin.conf".
- Add the lines "rescan=1" and "stake=0" (leave out the quotes):
server=1
listen=1
rpcuser=USER
rpcpassword=PASSWORD
rescan=1
stake=0
Don't start your client yet, but your client will automatically find the network in 30 to 90 seconds, so you don't need any "addnode" lines in your "StealthCoin.conf" file. In fact, after you get a successful sync, you should remove the "rescan=1" line so you don't have to wait for a rescan every time you open your wallet. The "stake=0" option makes sure your wallet doesn't try to mint transactions during synchronization, which slows things down considerably.
- Make a copy of your wallet.dat file and put it somewhere safe.
- From the StealthCoin data directory remove the files and folders called "blkindex.dat", "db.log", "blk0001.dat", "database", "debug.log", and "peers.dat", "tor", and "onion". Removing the latter two make sure that other nodes forget they ever banned you in case you were serving them bad blocks for some reason.
- Start the client you downloaded above. Version 1.0.4.1 (beta).
- If you stick at blocks 5310, 5810, or 6310 (or thereabouts), quit your client and restart. It will take you about 5 minutes to get passed 6310. I haven't figured out a good work-around for restarting at these blocks yet. The need to restart may decrease as more nodes on the network run newer versions if the client. The sync will probably pause at other block numbers that end with 310 and 810, but these pauses do not seem to require a restart. The longest pause you can expect is about 90 seconds. Pauses get shorter as the block numbers increase.
- Compare your synchronization process to the block number for XST at https://bittrex.com/Status . Bittrex has consistently had the best chain, so they are our reference. The explorer at http://explorer.argakiig.us/ is now using the latest beta and is synchronized with Bittrex.
- When you have synced completely, stop the client, back up your wallet.dat again, and remove the lines "rescan=1" and "stake=0" from your "StealthCoin.conf" file.
- Restart your client. The whole process should take about 15 to 20 minutes. Compare that to bitcoin, which takes 2-3 weeks.
- If you are missing coins at the end of this process, type "repairwallet" in the console.
[/list]
