News about development:
Results from the various
Testnets we are doing showed a very good retargetting of the difficulty with the new PID.
However, there is a bug on
Testnet that makes peers ban each other when finding blocks while being connected through I2P. It occurs when at about the same time two blocks are found by two different peers and one of them find another block in a row, before receiving the block from the other peer. On receiving, the peer will ban the other peer thinking it is a DoS attack.
2015-12-09 06:46:28 received: headers (82 bytes) from peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:28 received: block (188 bytes) from peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:28 received block 00000ac84373f5620f095919a7ad84c939fbae4c754ffae68d08e3bc6e72f9e7 peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:31 received: headers (163 bytes) from peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:31 ERROR: ContextualCheckBlockHeader : incorrect proof of work
2015-12-09 06:46:31 Misbehaving: c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p (0 -> 100) BAN THRESHOLD EXCEEDED
2015-12-09 06:46:31 ERROR: invalid header received
2015-12-09 06:46:31 ProcessMessage(headers, 163 bytes) FAILED, from peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:31 disconnecting peer peer=2, peeraddr=c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p
2015-12-09 06:46:35 connection from c7hefsynw7wf4p7l6hadufgs5mwn6clschsrbnjlwx5dqeki4yra.b32.i2p dropped (banned)
This bug does not allow us to upgrade the coin at the moment to the 99% finished 9.6.9 codebase.
Also, and most importantly, GroundRod our Chief Developer is no more, in fact he may be actually dead... but because he is anonymous we cannot be sure although it is 4 months he disapeared.
So we are looking for a skilled C++ coder to review the GroundRod code and finally release this awesome work!Until and unless we find this new C++ coder we will not release. It would be a shame considering the amount of work GroundRod put in this new codebase (updated to bitcoin 10.99).
Pass the word around!
CS
I will ask Lizhi.
Thank you for your help Conqueror!
Also I have updated the
Development Schedule to show the current bugs discovered in Testnet and their resolution, and the
Anoncoin development team page to show the current list of active developers and inactive ones, updated every month. In this way people will not be mislead about where we currently are and what our human capacity are.
We have open sourced the 0.9.6.9 code on Github tree gr_develop! Based on Bitcoin 0.11.0! Feel free to build your new Development version and report bugs!
https://github.com/Anoncoin/anoncoin/tree/gr_develophttps://wiki.anoncoin.net/How_to_build_Anoncoin_developAlso we have updated the list of all found bugs in this version so far, waiting for review from a new skilled C++ lead developer. If you are such a developer and are interested to become the lead developer in Anoncoin Core please contact me at:
cryptoslave@mail.i2p or
cryptoslave@anoncoin.net. Furthermore you are welcome to join us in #anoncoin-dev on IRC2P.
https://wiki.anoncoin.net/Development_schedule#Release_A_-_Anoncoin_Core_0.9.6.9_-_https:.2F.2Fgithub.com.2FAnoncoin.2Fanoncoin.2Ftree.2Fgr_developAlso please we are in needs of DNS-Seeders!
https://wiki.anoncoin.net/How_to_run_a_DNS_seeder A bounty is available for DNS-Seeders
https://wiki.anoncoin.net/Bounties#Seed_nodesPlease Help us to find a new Core Lead Developer if you want this coin to be part of the Future!