0.8 clients upgrade to 0.9.3.2 , the sooner the better
-
Hi , if your feathercoin wallet is running 0.8.X version , I strongly recommend that you upgrade it. If it is working for your pool and exchage, upgrade to 0.9.3.2 , others upgrade to 0.9.3.2 or 0.11.2.3.
0.9.3.2 version is very important. All clients should be upgraded. Please don’t hesitate, main pool has been installed.
http://www.ftc-c.com/pack4/feathercoin-0.9.3.2-setup.exe -
We will make 0.9.3.2 a release version soon. It needs some cleanup before this can happen.
Until then it is not recommended for mining and trading applications.
-
Please don’t hesitate, main pool has been installed. So I strongly recommend that you upgrade it. Old client will go to a wrong fork when blockchain v4.0 been minerd .
-
@Lizhi - I have already had to deal with a number of support issue because you are trying to release software too early!!!
There are a number of people helping test and fix the BUGs in 0.9.3.2 Development version. If a pool mine v4, that is NOT the official FTC Fork!!!
0.9.3.2 - Has not been released - It is still in development and testing.
PLEASE HELP US TEST< FIX the problems with 0.9.3.2 , and for CONSENSUS to decide when it is safe to release the new version and STAFF have time to PACKAGE and RELEASE it to SOME PROFESSIONAL STANDARD.THE CONSENSUS IS, It is NOT SAFE TO release yet. There should be no v4 blocks on the Network, so don’t start mining them !!!
-
After I mine and broadcast a version 4 at height 1338075, It is Orphaned , I deeply regret that.
BlockHash=97b330bc1be8263efe7ff5504510121e796ad6eb02c86024114da4123f7c5066Some solo miners still working with old version. block.nVersion be locked at version 2 and voting for hashrate is breaken .
If I replace CURRENT_VERSION with ACTIVE_VERSION in class CBlockHeader, old miners will be incomplete verification for latest protocol.
-
v2 blocks will be the only accepted until the next hard fork. It doesn’t prevent production of v3 or v4 or whatever blocks. They just need to be labelled v2 in order to prevent abuse of nVersion. There is a reason behind it.
-
@Lizhi
Having studied this problem and had to deal with the “accidental problems” these bridge version are causing I am now completely against 0.9.3.2 being released in it current form. I believe it is open wide to attack by malicious agents.There is no point in a bridge version, I have asked and asked why?? with no sensible answer. Please remove the bridge version code so we can release 0.9.6.
-
Revert hash vote, Jump version to 0.11.2.4
https://github.com/FeatherCoin/Feathercoin/commit/482c3d9db5660010c85509a7c7b37b883de1f68bfeathercoin-cli getblock bc294889c2691d9d4ed57f8c372b3195a7b657983cfcda21d36e987ecb8c3c71
-
@ Does 0.11 “at least” compile all the automatic tests?