Pages:
Author

Topic: [ANN][AID] AidBit | Digital-currency redefined | POW/POS | Groestl | Charity - page 31. (Read 101130 times)

full member
Activity: 154
Merit: 100
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.    Sad

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. Smiley
HR
legendary
Activity: 1176
Merit: 1011
Transparency & Integrity
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.    Sad

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 . . .
full member
Activity: 154
Merit: 100
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.    Sad

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.
HR
legendary
Activity: 1176
Merit: 1011
Transparency & Integrity
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.    Sad

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.)

 Tongue
hero member
Activity: 504
Merit: 500
full member
Activity: 154
Merit: 100


NEWS:

We've just released a minor update v.1.0.1.2, especially useful for non-tech people.

www.aidbit.net/download

It includes an installer option (enabled by default in this version) to delete the blockchain database.

Fix: Fixed POW Reward display in miner control.

Thank you!

AidBit
member
Activity: 98
Merit: 10


AID is listed at Coin-Swap.net

Markets
AID/BTC

Join our IRC channel
#coin-swap

Registration
Register

MFA Authentication
How to setup MFA with Google Authenticator

Support
Contact

Deposits
Confirmations are currently set to 10. You can watch the status of your deposit from your Deposit page.
member
Activity: 176
Merit: 10
yes i agree with you  but i see my wallets ans it s very not cool :/
i think i mine wind... Huh



edit:9h30 continue mining since this morning,a lot a block this morning when diff was 0---->0.0000000000000000000000000000000000000000000000000000 AID in my wallet



i m loosing faith
hero member
Activity: 1484
Merit: 535
Hashrates increasing, very nice ... and there were problems with the blockchain but  the dev(s) stayed and fixed those .. only prove that there really are dev(s) behind the product..

member
Activity: 176
Merit: 10
hi

hum can you explain to me:

-the new wallet made me loose 670 and 590 AID, "no confirm" , before mess, all was ok :/

-how many time AID are "stake" from wallet?

-receive only AID extract from POS, NO ONE FROM MINING?


?
sr. member
Activity: 386
Merit: 250
To the people attacking us. Thank you, you will only make us stronger!
yeah,sure we are.Attackigg means that AID is gaining attention. Smiley
full member
Activity: 154
Merit: 100
To the people attacking us. Thank you, you will only make us stronger!
full member
Activity: 147
Merit: 100
Why people want to download wallet from unknow people where you have an official link ?
full member
Activity: 154
Merit: 100
Yes, diff increase, good  Grin

We think we're still not in the clear. Master Checkpoint node is now keeping the network safe, and most of the nodes are on the right fork. As it's usual in software development we're most likely not facing one issue, not to mention multiple attacks.

Vger is right now coding the installer update, to delete the blockchain database for non tech users.
HR
legendary
Activity: 1176
Merit: 1011
Transparency & Integrity

Taking a look at the .csv file I saved before upgrading to the new wallets for the first time, I see that rolling share payouts from p2poolcoin.com:14715 (where I also had some miners) continued until 2014-07-26 05:55:20 GMT on what must have been a bad fork since the new block chain has those P2Pool payouts stopping at 2014-07-25 19:18:56 GMT, some 10 hours earlier.

That can certainly be addressed and reversed, and I should see those payouts come good once that pool is back up and running, correct?


BTW, on a more positive note, this from Cryptsy:

Hello XXXX,

Thank you for contacting us about this issue
I have submitted the coin request to our development team who will review it
to see if it meets our requirements for addition to the Cryptsy exchange.

If you have further issues, concerns or questions please do not hesitate to contact us again.
Thank you for choosing Cryptsy and enjoy trading!


Sincerely,

XXXX
Customer Service Manager


sr. member
Activity: 826
Merit: 250
Yes, diff increase, good  Grin
sr. member
Activity: 252
Merit: 250
Looks like the latest wallet update worked. Altmine is still on the same chain as the block explorer.
full member
Activity: 154
Merit: 100
hero member
Activity: 925
Merit: 1000
The last block in my wallet (latest version 1.0.1.1) is 13003. Block Explorer is showing now block 13097.
Pages:
Jump to: