Wallet sync stuck on block 75. Any ideas? edit: another coin with the precision/32 bit bug? if so, that's 3 now... Is the following a valid block or is there a bug. 2014-03-25 01:23:08 received block f0f3b3d222ff0d9330db22d33a0f3e963a65db7fea8286c38e3be5fc49f8c9ff
2014-03-25 01:23:08 ERROR: AcceptBlock() : incorrect proof of work
2014-03-25 01:23:08 ERROR: ProcessBlock() : AcceptBlock FAILED Did you add nodes? Yep, it wouldn't even get the first block without them. With them, got to 75 and stopped |
|
|
|
Wallet sync stuck on block 75. Any ideas? edit: another coin with the precision/32 bit bug? if so, that's 3 now... Is the following a valid block or is there a bug. 2014-03-25 01:23:08 received block f0f3b3d222ff0d9330db22d33a0f3e963a65db7fea8286c38e3be5fc49f8c9ff
2014-03-25 01:23:08 ERROR: AcceptBlock() : incorrect proof of work
2014-03-25 01:23:08 ERROR: ProcessBlock() : AcceptBlock FAILED |
|
|
|
What version number?
v1.3.2.1-unk-beta but looks like s4w3d0ff has the answer Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...
I compiled the new wallet and started a fresh sync but it won't got past block 8737.
Any hints?
try to clear out any old peers.dat files I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops If it helps, 2014-03-23 22:28:49 SetBestChain: new best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 tx=9353 date=2014-02-07 11:22:25 progress=0.058806
2014-03-23 22:28:49 nActualTimespan = 639 before bounds
2014-03-23 22:28:49 GetNextWorkRequired RETARGET
2014-03-23 22:28:49 nTargetTimespan = 80 nActualTimespan = 320
2014-03-23 22:28:49 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0) What are your machines specs? We had this problem before but don't have enough data to come to a conclusion. We think it maybe a "rounding" issue due to differences in processors. If you could let us know what OS (32 or 64bit) and possessor you are using that would help. It think that older (low powered) processors are not doing the math with enough accuracy as the others. This problem has been fixed in the latest update but trying to sync new wallets may be an issue on older machines. Well you'd be right about old/slow processors, this is on an Intel Atom N280 (slow when new, nevermind now). And it's a 32 bit linux mint 16 system. I've had 32 bit specific problems before (like with DGW now) so that could be an issue. Any chance there's a recent-ish blockchain download link somwhere in this thread? Thanks for the support |
|
|
|
Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...
I compiled the new wallet and started a fresh sync but it won't got past block 8737.
Any hints?
try to clear out any old peers.dat files I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops If it helps, 2014-03-23 22:28:49 SetBestChain: new best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 tx=9353 date=2014-02-07 11:22:25 progress=0.058806
2014-03-23 22:28:49 nActualTimespan = 639 before bounds
2014-03-23 22:28:49 GetNextWorkRequired RETARGET
2014-03-23 22:28:49 nTargetTimespan = 80 nActualTimespan = 320
2014-03-23 22:28:49 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0) |
|
|
|
Fixed the issue where no one could get past block 340. Windows Link: https://mega.co.nz/#!hsQw1b7A!CzJvWzW3zslgHg24J2zmDaB_khTT3zTc50hEtnDQim0 Will be working on linux wallet released tomorrow. And mac OSX as well! Any chance of 32 amd 64 bit wallets? or at least, github source Updated op for source. You can compile for linux. I will try and provide linux wallet as soon as possible! But there is a long list of things to be done right now Actually, I couldn't see it in the OP but I found it on your website. Thanks |
|
|
|
|
Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...
I compiled the new wallet and started a fresh sync but it won't got past block 8737.
Any hints?
|
|
|
|
|
predicatably, main pool offline
|
|
|
|
Sample blade.conf
(Place blade.conf into c:/users/**yourcomputername**/AppData/Roaming/Blade)
It's actually "Blade.conf" under linux rather than the stated "blade.conf". |
|
|
|
|
wallet says current block: 5100, total blocks: 5100 but still says out of sync
Any ideas?
|
|
|
|
I had 73.9992938 from the early days of this coin, launched wallet, wouldn't sync past around block 14xx, updated wallet, fully synced but that balance is now stuck as unconfirmed.
How to get it confirmed?
Old Appcoins (pre march 9th/relaunch) are for no use as well as the old Appcoin clients either. New Appcoin is based on a different source than the old one and they can't be combined. You must load the new Appcoin client from our website http://www.appcoin.info/downloads/ or from the OP of this topic. Pre relaunch Appcoin-folders (roaming-directory) and clients should be removed before you launch the new Appcoin client. If you have a client that's uploaded after Appcoin relaunch you should NOT delete the wallet.dat -file from the appcoin -folder but instead leave it (and appcoin.conf) there and remove the other files from the folder and after that, reload the blockchain by launching the new Appcoin 0.8.3 client (released March 21st). Hopefully this helps, and if you need more aid, please contact us. So the coins are lost and the wallet.dat is useless? I need a new one generated by the new code? |
|
|
|
|
I had 73.9992938 from the early days of this coin, launched wallet, wouldn't sync past around block 14xx, updated wallet, fully synced but that balance is now stuck as unconfirmed.
How to get it confirmed?
|
|
|
|
I've pushed a few new changes the repository and updated the binaries to -b11. Changes:
- Import clintar's fix for reconnecting if the server is rebooted to improve robustness;
- Fix too-high dev fee to jh/clintar in source (this was fixed in the -b10 binaries, but I never pushed it to the source tree)
(The bug: Instead of donating 0.25% to each of them and subtracting 0.5% to me, it subtracted 0.5% and then donated the full amount to each person)
- Remove unneeded use of atomic header file to simplify build process with older gcc
-Dave
regular make, make -f Makefile_mtune and make -f Makefile_nomarch all segfault for me. Using a first generation Core i7 920 and 32 bit linux mint 16 Can someone please get a working 32 bit linux build going, I've wanted to mine this coin since launch and still have an empty wallet  |
|
|
|
Fixed the issue where no one could get past block 340. Windows Link: https://mega.co.nz/#!hsQw1b7A!CzJvWzW3zslgHg24J2zmDaB_khTT3zTc50hEtnDQim0 Will be working on linux wallet released tomorrow. And mac OSX as well! Any chance of 32 amd 64 bit wallets? or at least, github source |
|
|
|
I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain. I can post the debug log if someone wants to help. It has completely screwed my Saturday I was hoping to have a nice smooth p2pool transition I just pushed this branch, try it and let me know if that works: https://github.com/evan82/darkcoin/tree/DGW-32bit-bugstill.. 2014-03-22 16:25:34 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:25:34 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:25:34 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:25:34 Misbehaving: 112.175.123.94:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:25:34 disconnecting node 112.175.123.94
// Check proof of work
//if (nBits != GetNextWorkRequired(pindexPrev, this))
double n1 = ConvertBitsToDouble(nBits);
double n2 = ConvertBitsToDouble(GetNextWorkRequired(pindexPrev, this));
if ((int)(n1*100) != (int)(n2*100))
return state.DoS(100, error("AcceptBlock() : incorrect proof of work"));
user@monitoring:~> darkcoind --help
DarkCoin version v0.9.0.0-g07c9905-beta
Same result here, but not only that, with userdata deleted (so complete resync) it gets stuck on block 23590. It won't accept block 23591 2014-03-22 21:55:36 received block 00000000006eeac449b08b60a2956dfdbca9a12819a961ddf8a666c31feee47d
2014-03-22 21:55:36 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 21:55:36 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 21:55:36 Misbehaving: 91.228.76.83:9999 (0 -> 100) DISCONNECTING Although it is valid http://explorer.darkcoin.io/block/00000000006eeac449b08b60a2956dfdbca9a12819a961ddf8a666c31feee47dIf you use linux, use 64bit os. 32bit bug will be fixed soon. Sadly I can't but I don't mind waiting. I just wanted to report that the proposed fix not only doesn't fix the original issue, it actually breaks sync much earlier. Has any managed to see if this also applies on 32 bit windows? I would think so if it really is 32 bit specific but if not, it might help narrow down the problem |
|
|
|
I'm having a strange issue.. one machine (ubuntu) refuses to update it's wallet. I've deleted literally everything (the darkcoin/ directory and the .darkcoin/ directory) and rebuilt it. As before, it hung on s bunch of orphan blocks from about 6 days ago. So, I deleted and rebuilt everything again, then took everything in the .darkcoin/ directory from a currently working wallet (except wallet.dat) and copied it into the new directory so it would (theoretically) have a decent blockchain to start from and only be a block behind. It found one block, and then stopped communicating with the blockchain. I can post the debug log if someone wants to help. It has completely screwed my Saturday I was hoping to have a nice smooth p2pool transition I just pushed this branch, try it and let me know if that works: https://github.com/evan82/darkcoin/tree/DGW-32bit-bugstill.. 2014-03-22 16:25:34 received block 0000000000a138da706d1e79ab9064034578404bd551482bae4840afa6673fad
2014-03-22 16:25:34 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 16:25:34 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 16:25:34 Misbehaving: 112.175.123.94:9999 (0 -> 100) DISCONNECTING
2014-03-22 16:25:34 disconnecting node 112.175.123.94
// Check proof of work
//if (nBits != GetNextWorkRequired(pindexPrev, this))
double n1 = ConvertBitsToDouble(nBits);
double n2 = ConvertBitsToDouble(GetNextWorkRequired(pindexPrev, this));
if ((int)(n1*100) != (int)(n2*100))
return state.DoS(100, error("AcceptBlock() : incorrect proof of work"));
user@monitoring:~> darkcoind --help
DarkCoin version v0.9.0.0-g07c9905-beta
Same result here, but not only that, with userdata deleted (so complete resync) it gets stuck on block 23590. It won't accept block 23591 2014-03-22 21:55:36 received block 00000000006eeac449b08b60a2956dfdbca9a12819a961ddf8a666c31feee47d
2014-03-22 21:55:36 ERROR: AcceptBlock() : incorrect proof of work
2014-03-22 21:55:36 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-22 21:55:36 Misbehaving: 91.228.76.83:9999 (0 -> 100) DISCONNECTING Although it is valid http://explorer.darkcoin.io/block/00000000006eeac449b08b60a2956dfdbca9a12819a961ddf8a666c31feee47dSo sadly the DGW-32bit-bug branch isn't the fix |
|
|
|
|
Time to compile me a wallet.
Let's see what online to offline evolves into
edit: Any MPOS pools?
|
|
|
|
There's no 32 bit linux wallet and no source...
No choice but to give this coin a miss.
Source will be available again soon. We're forking the blockchain to fix difficulty issues. And there is a linux wallet as well. The provided linux wallet is for 64 bit systems only. |
|
|
|
Vote for SHACoin on MintPal
https://www.mintpal.com/votingOnly registered users with a trade history are permitted to vote for coins. Every user is limited to 5 (five) votes per hour. You can also send some BTC to move it up in the votes fast to this address: 19F8KFvUL4MYkZMzisJ9Yp2K3nd8DpTpvm +5 (241-246) Reply & add SHACoin address in the signature = 600 SHACoins Each Is that done? |
|
|
|
|
There's no 32 bit linux wallet and no source...
No choice but to give this coin a miss.
|
|
|
|
|
Show Posts
