Quote from: Cryptoslave on July 19, 2016, 10:38:38 PM

Quote from: cryptoadoption15 on July 18, 2016, 01:29:22 AM

Quote from: Cryptoslave on July 07, 2016, 06:38:37 PM

Quote from: HPt on July 07, 2016, 02:49:09 PM

Did the blockchain fork after the hard fork?
My transfer of 9.9 ANC from AMXraoVxaBvkiwWHbYRkQW7nmo6vHNHBrQ to ASoVC4BfzXKvuCp96ckq41QsxnWLh3gxnx has a lot of confirmations, but it doesn't show up in the explorer http://abe.darkgamex.ch:2751/chain/Anoncoin

Hi,

Yes, the hardfork worked correctly.

http://abe.darkgamex.ch:2751/chain/Anoncoin is still on the old chain but is being updated at the moment.

Your transaction was done on the correct chain.

Sadly, I am not very happy with the tuning of the retarget algo with 90% of our hashrate being multipools it retarget too strongly both upward and downward and consequently the remaining faithful miners (around 400 MH/s) have to mine very difficult blocks (even up to 100 times more difficult than some of the quick blocks mined by multipools). The chain is thus for the moment about 30% too slow with very broad block time.

So I will check how to tune the moving averages differently to not have so much variation with this particular 90%+ intermittent multipool hashrate as well as the proportional term of the PID to have a smoother ride with retargetting less aggressively in those worse mining conditions. In a couple of weeks a new hardfork (0.9.6.12, same codebase) will be proposed with the new settings for the PID after we testnet it and will be announced here as well as with the alert key.

CS

How is the difficulty re-targeting looking now after you have had a few more weeks to evaluate it post fork?

Hi,

I did a post with the current data from mainet on the wiki: https://wiki.anoncoin.net/GroundRod_PID_main_ver1

I hope it answer your questions!

As stated above I am still tuning the PID to limit the dispersion in block time.

Thank you for your question!

CS

I cannot read your answer because https://wiki.anoncoin.net/GroundRod_PID_main_ver1 has a security certificate error. I know the problem is not unique to me because I attempted to access it fro multiple devices, browsers and IP addresses.

Can you cut and past your response here until you are able to fix the ecurity certificate error?

Based on this issue and the toolchain problem described by Cryptopia perhaps these easy certificate/build errors should be fixed before more time is spent on PID.

It is hard to convince people to use privacy/security software when these basic issues are present