creamynebula
|
|
July 24, 2014, 01:43:57 AM |
|
This and https://bitcointalk.org/index.php?topic=681725.msg7947679#msg7947679 puts me at ease that you are reasonably committed. I do think its really important that everyone holding send transactions to a few different addresses in his wallet and keep staking 24/7, it would help a lot, even if everyone only do so with a part of their coins. I am hoping that the wallet issues get corrected. Now it is out of sync again, I have never had issues like this with any other wallet.
Just deleted everything to start over.
Can you post a log file to pastebin? Another user posted his. It was helpful, but I need a few problematic case studies to figure out what is going on. I'm back on the grid now. If I can find a pattern with the wallets that are not syncing, then I can get this fixed.
|
|
|
|
TrekRider
Newbie
Offline
Activity: 56
Merit: 0
|
|
July 24, 2014, 02:04:54 AM |
|
This and https://bitcointalk.org/index.php?topic=681725.msg7947679#msg7947679 puts me at ease that you are reasonably committed. I do think its really important that everyone holding send transactions to a few different addresses in his wallet and keep staking 24/7, it would help a lot, even if everyone only do so with a part of their coins. As has been stated many times in this thread, staking is important to the health of the coin. Everyone should take a few minutes to create some transactions in their wallets over the course of a few days and we'll never have any issues.
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 03:42:34 AM |
|
Here is one of my log file. http://www.short.cc/debug.logIt is out of sync and never sync again. I would just delete and reinstall everything but this could help the dev. I do see many ERROR: Proxy error: host unreachable. Probably this the case but I did changed dns to 8.8.8.8 with no help.
|
|
|
|
ProGamer
|
|
July 24, 2014, 03:45:49 AM |
|
This and https://bitcointalk.org/index.php?topic=681725.msg7947679#msg7947679 puts me at ease that you are reasonably committed. I do think its really important that everyone holding send transactions to a few different addresses in his wallet and keep staking 24/7, it would help a lot, even if everyone only do so with a part of their coins. As has been stated many times in this thread, staking is important to the health of the coin. Everyone should take a few minutes to create some transactions in their wallets over the course of a few days and we'll never have any issues. But this require trusting people. I was thinking automated wallets using staking to generate coins could be used.
|
|
|
|
prix
|
|
July 24, 2014, 04:50:25 AM Last edit: July 24, 2014, 05:31:39 AM by prix |
|
I have created the script file for Windows for those who want to help with stacking. It's small and very simple js-file for creating a transaction at a specified interval. I tested this file on Windows 7 x64. Instruction: 1. Run the wallet with proper .conf file. 2. Create file "coin_sender.js" and copy content from pastebin. 3. Change: iterations, user, password, url, fromAccount, toAddress, amount, interval if you need (in ms). 4. Run the script. 5. If you want to stop the script run the Task Manager and kill wscript.exe. You can see results in the log file "coin_sender.log". Over the past 3 days I created 3928 transactions and more than 1000 POS-blocks. Edit: Here is one of my log file. http://www.short.cc/debug.logIt is out of sync and never sync again. I would just delete and reinstall everything but this could help the dev. I do see many ERROR: Proxy error: host unreachable. Probably this the case but I did changed dns to 8.8.8.8 with no help. What is your block height and hash? Difficulty is low again and anybody can generate too much blocks per minute (for example: 15103 - 15106 in 3 sec). Maybe your out of sync related to this problem. Edit2: I know the dev working on the problem now. And I due to the large number of transactions can now constantly generate blocks, hope it can help the network. Edit3: I have changed the script (added fromAccount) for those who use same wallet for sending and receiving transaction.
|
|
|
|
ChrisLandin
|
|
July 24, 2014, 06:58:49 AM |
|
Hi guys. Has something major happened with the wallet?? Mine has stopped in sync for the last 48 hrs which is the best its ran. I even sent all my coins to bittrex then sent them back in 2000 batches every 5 mins or so to try and help get a more even spread on my staking to help the network. Im thinking more and more people must be staking now
|
|
|
|
StealthDevs (OP)
|
|
July 24, 2014, 08:16:06 AM Last edit: July 24, 2014, 08:33:34 AM by StealthDevs |
|
Hi guys. Has something major happened with the wallet?? Mine has stopped in sync for the last 48 hrs which is the best its ran. I even sent all my coins to bittrex then sent them back in 2000 batches every 5 mins or so to try and help get a more even spread on my staking to help the network. Im thinking more and more people must be staking now Hondo here: I'm back in civilization. The retreat didn't work out as planned, but I'm here to debug and move forward. It looks like there are real issues, but I haven't been able to investigate them, much less build the fixes. With the help of prix and two others I have tracked down a couple of syncing issues. I'm working on a beta client (1.0.4.0) that should address the two issues I have found. The beta client should be available in an hour or so. The team generally is unaffected by these issues for reasons I haven't determined yet, so I need some beta testers. I'll post windows and mac beta wallets here informally and anyone who has syncing issues can give them a try. The best thing to do is just delete your block chain and try the new clients. The source will be posted to github at the same time. I'm building the mac client right now with windows to follow. Hopefully I can get out these beta builds in less than an hour (so I can go to sleep!). I'm back and we are going to rock on Stealth. So hold tight, this baby is going to move. edit: My test has just moved passed a first sticking point at block 5310. So the beta wallet should fix most of the syncing issues. I still need testers, though, because it is almost impossible for me to replicate an error that affects a small minority of users. edit: The initial download will stall at 5310, 5810, 6310, 6810, 7310, 7810, etc., for 30 seconds to 1 minute each. But it looks like it will not be necessary to restart the client at these points. These stalls will probably get shorter as people adopt the new builds.
|
STEALTH | XST | stealth.org
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 08:53:57 AM |
|
Hi guys. Has something major happened with the wallet?? Mine has stopped in sync for the last 48 hrs which is the best its ran. I even sent all my coins to bittrex then sent them back in 2000 batches every 5 mins or so to try and help get a more even spread on my staking to help the network. Im thinking more and more people must be staking now Hondo here: I'm back in civilization. The retreat didn't work out as planned, but I'm here to debug and move forward. It looks like there are real issues, but I haven't been able to investigate them, much less build the fixes. With the help of prix and two others I have tracked down a couple of syncing issues. I'm working on a beta client (1.0.4.0) that should address the two issues I have found. The beta client should be available in an hour or so. The team generally is unaffected by these issues for reasons I haven't determined yet, so I need some beta testers. I'll post windows and mac beta wallets here informally and anyone who has syncing issues can give them a try. The best thing to do is just delete your block chain and try the new clients. The source will be posted to github at the same time. I'm building the mac client right now with windows to follow. Hopefully I can get out these beta builds in less than an hour (so I can go to sleep!). I'm back and we are going to rock on Stealth. So hold tight, this baby is going to move. edit: My test has just moved passed a first sticking point at block 5310. So the beta wallet should fix most of the syncing issues. I still need testers, though, because it is almost impossible for me to replicate an error that affects a small minority of users. edit: The initial download will stall at 5310, 5810, 6310, 6810, 7310, 7810, etc., for 30 seconds to 1 minute each. But it looks like it will not be necessary to restart the client at these points. These stalls will probably get shorter as people adopt the new builds. Stealth rock! Yes, I'm waiting to test this new beta client.
|
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 09:47:40 AM |
|
Request has been sent to download the files.
|
|
|
|
StealthDevs (OP)
|
|
July 24, 2014, 10:06:27 AM |
|
Request has been sent to download the files. Sorry! I forgot to enable the Windows download. It's ready now.
|
STEALTH | XST | stealth.org
|
|
|
StealthDevs (OP)
|
|
July 24, 2014, 10:07:22 AM |
|
Also note that the block explorer got stuck tonight. It is still on 1.0.3.1. It will be updated to the 1.0.4.0 beta release in a few hours. The maintainer is asleep.
|
STEALTH | XST | stealth.org
|
|
|
iram3130
Legendary
Offline
Activity: 1512
Merit: 1010
ITSMYNE 🚀 Talk NFTs, Trade NFTs 🚀
|
|
July 24, 2014, 10:29:58 AM |
|
This and https://bitcointalk.org/index.php?topic=681725.msg7947679#msg7947679 puts me at ease that you are reasonably committed. I do think its really important that everyone holding send transactions to a few different addresses in his wallet and keep staking 24/7, it would help a lot, even if everyone only do so with a part of their coins. As has been stated many times in this thread, staking is important to the health of the coin. Everyone should take a few minutes to create some transactions in their wallets over the course of a few days and we'll never have any issues. But this require trusting people. I was thinking automated wallets using staking to generate coins could be used. Just generate new address in your wallet and send yourself coins. It will resolve the issue.
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 10:52:49 AM |
|
Request has been sent to download the files. Sorry! I forgot to enable the Windows download. It's ready now. My wallet stuck at block 15329, the syncing is pretty fast up to this point. Much improved. edit: both wallets can't get pass block 15329
|
|
|
|
foxy
|
|
July 24, 2014, 11:29:57 AM |
|
Request has been sent to download the files. Sorry! I forgot to enable the Windows download. It's ready now. My wallet stuck at block 15329, the syncing is pretty fast up to this point. Much improved. edit: both wallets can't get pass block 15329 confirm stuck at same block.
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 11:47:08 AM |
|
|
|
|
|
prix
|
|
July 24, 2014, 01:52:11 PM |
|
I tested the beta version. Stucked on 15329. Logs (-debug -debugnet -logtimestamps): https://www.dropbox.com/s/vc9lvt8vknl9eda/new_logs.7zTwo files exists in archive. debug_15329.log - sync from 0 to 15329, then stuck debug_after_15329_restart.log - after the wallet restart, sync still stuck I found somethings interesting in the second file. The wallet tried sync after 15329 block, and as I understand can't pass 15330: 07/24/14 13:13:44 received: block (456 bytes) 07/24/14 13:13:44 received block 939f825d487fe9f9d93f 07/24/14 13:13:44 >>> CheckStakeKernelHash: passed GetKernelStakeModifier 07/24/14 13:13:44 CheckStakeKernelHash() : using modifier 0x9fff1a95cffcdf43 at height=11508 timestamp=2014-07-21 12:40:59 UTC for block from height=11393 timestamp=2014-07-21 09:44:03 UTC 07/24/14 13:13:44 CheckStakeKernelHash() : check protocol=0.3 modifier=0x9fff1a95cffcdf43 nTimeBlockFrom=1405935843 nTxPrevOffset=158 nTimeTxPrev=1405935843 nPrevout=1 nTimeTx=1406195215 hashProof=fab4dbfab0ff32c88798e6a082c24b46bef3efb1dcec3161f779eabe01d19ab5 07/24/14 13:13:44 >>> bnCoinDayWeight = 1, bnTargetPerCoinDay=5647574804144476117109686896495768941282598351965528251131500646898935529472 07/24/14 13:13:44 >>> CheckStakeKernelHash - hashProofOfStake too much 07/24/14 13:13:44 ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake e70124086e21bd03430fd6a3943ce8e5567cd2c1a73ec960d5cd8445d73522f9, hashProof=fab4dbfab0ff32c88798e6a082c24b46bef3efb1dcec3161f779eabe01d19ab5 07/24/14 13:13:44 WARNING: ProcessBlock(): check proof-of-stake failed for block 939f825d487fe9f9d93fba3ea73be0a72808f08013f262d351ca12e107136c73
15330 has hash: 939f825d487fe9f9d93fba3ea73be0a72808f08013f262d351ca12e107136c73 This is correct block, I have fully synced 1.0.3.1 and 1.0.4.0 (I synced this wallet manually copied the blockchain) with this block (both on 15525 now). I don't know why 1.0.4.0 can't pass this block when downloading it over the network, and why pass when loads from blockchain.
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 02:30:52 PM |
|
In another good new StealthCoin Forum is ready; http://www.stealthtalk.orglet me know what ya'll think
|
|
|
|
deadliftbrah
|
|
July 24, 2014, 02:45:21 PM |
|
Great effort, just not sure if the "all black everything" look is as inviting to non stealthers...btw, I'm attempting to make "stealthers" a thing....
|
|
|
|
BTCwriter
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
July 24, 2014, 03:03:14 PM |
|
Great effort, just not sure if the "all black everything" look is as inviting to non stealthers...btw, I'm attempting to make "stealthers" a thing.... We tried to make the theme according to StealthCoin logo. It can easily change when StealthCoin have new logo and color etc.
|
|
|
|
|