Thanks for the update. A couple of question: - Will the restart happen at 307770
- Will you also be updating the SPV code (ExecoinJ)? I've been experimenting with it and get up to 307769, and then a bunch of non-connecting block errors.
Thanks again! The restart happened at 307769 Yes, we will update ExecoinJ within next hour, but Android wallet will be build against new ExecoinJ later. |
|
|
|
I See, six miners are was mining 5 blocks... At official "closed" pool. Current block is 307775. It's working, or just testing ?
Testing BUT if everything is fine, this restart becomes official. Source code is on the Github, Windows wallets have been updated (Mac's one will be later). http://explorer.execoin.net is actual. Please help to test and add some hashrate. Just as a precaution we removed dynamic block reward code completely and increased number of blocks considered in DGW to 60. Working nodes just in case: addnode=95.85.26.197 addnode=107.170.240.30 addnode=162.243.136.142 addnode=128.199.233.179 addnode=198.211.100.64 addnode=192.241.152.198 addnode=107.170.79.10 addnode=37.139.3.206 addnode=188.226.169.188 addnode=107.170.227.175 addnode=128.199.221.109 addnode=107.170.227.176 addnode=188.226.169.189 addnode=192.241.128.215 addnode=107.170.79.12 addnode=107.170.12.174 addnode=188.226.130.205 addnode=95.85.39.247 addnode=192.99.166.230 addnode=192.99.166.231 |
|
|
|
I think the key here, is to get everyone on the same page. If people node-ops dont respond in a set ammount of time, their node isnt coded in. Obviously more nodes can be added by the end usere @ any time as they become available.
Dev's, if you need any non-coding assistance & all.. please speak up, I don't want to speak for others.. but If theres is anything we can help with, even if trivial.. please let us know. I have already let one of the mods know @ Poloniex of the pending re-release @ block 307770, about to do same with cryptsy.
Thanks for your support, we are working on it. |
|
|
|
|
The problem is that afterfork code has a bug. At some arbitrary point of time a node fails to agree with the rest of the network on a reward amount:
ERROR: ConnectBlock() : coinbase pays too much
and the wallet gets stuck on the corresponding block. Darkcoin once had a similar problem with wallets getting stuck because of a bug in their dynamic reward code.
Because of a lot of transfers went to nowhere, the only solution is to fix the bug and restart the network from 307770 again.
|
|
|
|
Multipool updated last night, resynced and was synced to the same block as the explorer. Now we're 400 blocks behind and the client will not sync past that.
Please advise.
The solution is to delete blocks (everything in the folder except wallet.dat and execoin.conf) and resync (using list of nodes - for example or if without it will get a list from seeders). Please update ASAP Your DNS seed is obviously still advertising nodes on the wrong fork. You need to add a checkpoint to the code so that nodes will only connect to the proper fork. Will do. |
|
|
|
Have you contacted the exchanges? Cryptsy & Poloniex still have inaccessible wallets. We should get rid of nodes on wrong fork first. CORRECT now is Difficulty 0.61357189 Current Block 309647 !!!!!! Wrong !!!!!!!! Current Block 309594 !!!!!!!! Wrong !!!!!!!!! Current Difficulty 0.18550547 there is still hashrate on the wrong fork, if you know there is it, please contact and ask to update. |
|
|
|
Multipool updated last night, resynced and was synced to the same block as the explorer. Now we're 400 blocks behind and the client will not sync past that.
Please advise.
The solution is to delete blocks (everything in the folder except wallet.dat and execoin.conf) and resync (using list of nodes - for example or if without it will get a list from seeders). Please update ASAP |
|
|
|
Just double checking, is an exact list of nodes on the correct fork available? I used the one from above for the giveaway wallet and it does not synch.
Seeders and nodes are ok, you may just resync Please check http://explorer.execoin.net for current block. If your wallet stuck (or shows last block different from the block explorer), please resync by closing wallet, removing everything except wallet.dat in your profile folder and re-opening wallet. DNS node seeders are on correct fork (you may get a list of nodes by running 'nslookup dnsseed.execoin.net' from your command prompt). Here is list of correct nodes just in case: addnode=95.85.26.197 addnode=107.170.240.30 addnode=162.243.136.142 addnode=128.199.233.179 addnode=198.211.100.64 addnode=192.241.152.198 addnode=107.170.79.10 addnode=37.139.3.206 addnode=188.226.169.188 addnode=107.170.227.175 addnode=128.199.221.109 addnode=107.170.227.176 addnode=188.226.169.189 addnode=192.241.128.215 addnode=107.170.79.12 addnode=107.170.12.174 addnode=188.226.130.205 |
|
|
|
I send them email, I dont use them, but found admin email for multipool
Thank you, they resynced. Part of the network was on wrong fork. Now everything is fixed. Please check http://explorer.execoin.net for current block. http://pool.execoin.net is on correct fork too. If your wallet stuck (or shows last block different from the block explorer), please resync by closing wallet, removing everything except wallet.dat in your profile folder and re-opening wallet. DNS node seeders are on correct fork (you may get a list of nodes by running 'nslookup dnsseed.execoin.net' from your command prompt). Here is list of correct nodes just in case: addnode=95.85.26.197 addnode=107.170.240.30 addnode=162.243.136.142 addnode=128.199.233.179 addnode=198.211.100.64 addnode=192.241.152.198 addnode=107.170.79.10 addnode=37.139.3.206 addnode=188.226.169.188 addnode=107.170.227.175 addnode=128.199.221.109 addnode=107.170.227.176 addnode=188.226.169.189 addnode=192.241.128.215 addnode=107.170.79.12 addnode=107.170.12.174 addnode=188.226.130.205 |
|
|
|
|
Please let multipool.us know that they are on the wrong fork.
|
|
|
|
Part of the network is on wrong fork. Please move your hashrate out of multipools. Please check http://explorer.execoin.net for current block. http://pool.execoin.net is on correct fork too. If your wallet stuck (or shows last block different from the block explorer), please resync by closing wallet, removing everything except wallet.dat in your profile folder and re-opening wallet. DNS node seeders are on correct fork (you may get a list of nodes by running 'nslookup dnsseed.execoin.net' from your command prompt). Here is a list of correct nodes just in case: addnode=95.85.26.197 addnode=107.170.240.30 addnode=162.243.136.142 addnode=128.199.233.179 addnode=198.211.100.64 addnode=192.241.152.198 addnode=107.170.79.10 addnode=37.139.3.206 addnode=188.226.169.188 addnode=107.170.227.175 addnode=128.199.221.109 addnode=107.170.227.176 addnode=188.226.169.189 addnode=192.241.128.215 addnode=107.170.79.12 addnode=107.170.12.174 addnode=188.226.130.205 |
|
|
|
The pool i'm on appears to be operable, nothing broke. Payouts are reduced now as anticipated.
Hardfork completed successfully, major exchanges are operational. |
|
|
|
IMPORTANT REMINDER!
Hardfork in Execoin network is expected in approximately 11 hours, PLEASE UPDATE YOUR WALLETS from our website if still not updated!
Learn more about Execoin update and upcoming hardfork at http://www.execoin.net
|
|
|
|
|
New version of Execoin Wallet for Android has been released. This update features hardfork changes, some bugfixes, new checkpoints, DGW v3.
Please update your Android wallets!
|
|
|
|
Need to contact your browser support and get the Windows wallet unblocked by virus scanners; it does not like the "EXE" part of the filename and most browsers won't let you download it and/or run it.
Windows wallets are now available in the form of password-protected zip archives. |
|
|
|
|
Show Posts
