HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 27, 2014, 03:04:53 PM Last edit: July 27, 2014, 03:41:47 PM by HR |
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. Add3: installed and doing a re-sync, program not responding with 2203 blocks remaining and block explorer just went off-line at the same time. I've noticed the "program not responding" several times when syncing, always around the same place. Could there be a problem somewhere around block 11460? Has now completed sync. Block Explorer is back online. PC confirmed on the correct blockchain now. (Last install was a default install leaving everything in place and letting the installer do its job.)
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 03:34:09 PM |
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. We were once again targets of deliberate or non deliberate attack. We're not totally sure but it seems that somebody with huge hashrate is trying to mine with wrongly configured stratum. At least logs show that. We've just activated pos on our charity account to keep this fork safer.
|
|
|
|
lainarko
Newbie
Offline
Activity: 29
Merit: 0
|
|
July 27, 2014, 03:35:14 PM |
|
|
|
|
|
HR
Legendary
Offline
Activity: 1176
Merit: 1011
Transparency & Integrity
|
|
July 27, 2014, 03:47:24 PM |
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. We were once again targets of deliberate or non deliberate attack. We're not totally sure but it seems that somebody with huge hashrate is trying to mine with wrongly configured stratum. At least logs show that. We've just activated pos on our charity account to keep this fork safer. As you said, AidBit will be stronger for it. Good idea to do everything possible to keep the fork safer. BTW, the program mini-hang that always seems to happen on initial sync that I mentioned in my last post, there might be something there to take a closer look at. Weird things with the block explorer in general where sometimes it generates very low block values that make it look like the entire blockchain is being resynchronized . . .
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 03:53:30 PM |
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. We were once again targets of deliberate or non deliberate attack. We're not totally sure but it seems that somebody with huge hashrate is trying to mine with wrongly configured stratum. At least logs show that. We've just activated pos on our charity account to keep this fork safer. As you said, AidBit will be stronger for it. Good idea to do everything possible to keep the fork safer. BTW, the program mini-hang that always seems to happen on initial sync that I mentioned in my last post, there might be something there to take a closer look at. Weird things with the block explorer in general where sometimes it generates very low block values that make it look like the entire blockchain is being resynchronized . . . Actually, the BE followed the wrong fork. So I had to show him the way.
|
|
|
|
|
coke15
Member
Offline
Activity: 176
Merit: 10
|
|
July 27, 2014, 04:18:24 PM |
|
|
|
|
|
SimkoMiner
|
|
July 27, 2014, 04:21:55 PM |
|
I downloaded and installed latest wallet and another problem appeared:
Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
I'm stuck at block 13169
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 04:24:32 PM |
|
Actually, we had nothing to do with it. They added us on their own. Regards, AidBit
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 04:27:14 PM |
|
I downloaded and installed latest wallet and another problem appeared:
Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
I'm stuck at block 13169 [/quote
We were a target of another attack before. Now we've activated all the countermeasures that we know of. Hopefully it'll be enough this time.
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 04:28:36 PM |
|
POS difficutly is rising, the POW/POS blocks frequency should slowly stabilize.
|
|
|
|
SimkoMiner
|
|
July 27, 2014, 04:30:21 PM |
|
I downloaded and installed latest wallet and another problem appeared:
Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
I'm stuck at block 13169 [/quote
We were a target of another attack before. Now we've activated all the countermeasures that we know of. Hopefully it'll be enough this time.
ok so what should I do now? Resynchronize again?
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 04:32:20 PM |
|
I downloaded and installed latest wallet and another problem appeared:
Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers. (code -2)
I'm stuck at block 13169 [/quote
We were a target of another attack before. Now we've activated all the countermeasures that we know of. Hopefully it'll be enough this time.
ok so what should I do now? Resynchronize again? Unfortunatelly yes. I really hope it's the last time.
|
|
|
|
virgojeep
|
|
July 27, 2014, 05:07:08 PM |
|
cool. its syncing. People shouldn't be blaming the devs for lost hashing power that your renting. This is a new coin and there will be challenges to overcome. Never invest more than your willing to loose.
|
|
|
|
SimkoMiner
|
|
July 27, 2014, 05:15:41 PM |
|
Why the difficulty showing in SGMiner is different than in wallet? Miner shows 26, Wallet shows 16,46
|
|
|
|
AidBit (OP)
|
|
July 27, 2014, 05:34:08 PM |
|
Why the difficulty showing in SGMiner is different than in wallet? Miner shows 26, Wallet shows 16,46
We'll check it out. Thanks.
|
|
|
|
coke15
Member
Offline
Activity: 176
Merit: 10
|
|
July 27, 2014, 05:38:14 PM |
|
yep
same here
in same pool felix rig 1 diff 28.502--->24 in sgminer rig 2 diff 48.8711 --->30 in sgminer
at the same time ??
in rig 1 ,new aid from mining are coming ,still not in the rig 2
trying maya on rig 2
:/
|
|
|
|
Singman33
|
|
July 27, 2014, 06:16:56 PM |
|
Please update GIT repository with latest patch. ~$ aidbitd getinfo { "version" : "v1.0.1.1", "protocolversion" : 60015, "walletversion" : 60000, [snip] "blocks" : 13674, "timeoffset" : -1, "moneysupply" : 3663086.59729302, "connections" : 7, "proxy" : "", "ip" : "82.229.26.235", "difficulty" : { "proof-of-work" : 48.87110024, "proof-of-stake" : 0.00024414 }, "testnet" : false, "keypoololdest" : 1405716160, "keypoolsize" : 101, "paytxfee" : 0.00010000, "mininput" : 0.00000000, "errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers." }
~/wallets/aidbit# git pull Already up-to-date.
|
|
|
|
coke15
Member
Offline
Activity: 176
Merit: 10
|
|
July 27, 2014, 06:26:04 PM |
|
hi still sync problem, i don t know why,but regurlarly the sync restarts a -189 -190 block... manualy erase x time aidbit folder in roaming,syncking error still here ,may be that my problem comes from here? no POW aid come in. i stop for this time. wait and see. dev,i know you are working but i spend time/hash/electicity mouarf -203 block now
|
|
|
|
vetzdog
Newbie
Offline
Activity: 22
Merit: 0
|
|
July 27, 2014, 07:24:30 PM |
|
Downloaded wallet v1.0.1.2 and yes the sinc prob seams to be solved but all my coins are unconfirmed now.
Can u explaine me why, please???
And by the way sory about my stress yesterday and keep up the good work dev.
|
|
|
|
|