This version cancels the recent BKS grant by rejecting the current block 1183900, so it basically makes the node forget all the blocks made during the last week. It will fork the network between 5.x and 6.0 nodes. All nodes will stay connected to each other but on different chains, until the 6.0 chain eventually becomes the best chain for all nodes (it will take some time even if all the shareholders switch now).
If the grant is actually wanted by the majority shareholders they must just keep running version 5.x. This version exists to allow them to revert it if they want to. If there’s no consensus the two chains will coexist.
The 6.0 chain starts when the grant had 43% of the votes. Shareholders must upgrade quickly and mint if they don’t want the grant to still pass on the new chain. And they must make sure they mint continuously in the future to prevent this kind of problem.
After the upgrade shareholders who minted during last week must run this RPC command to clear all their orphaned transactions, otherwise most of their shares won’t be available to mint:
The 6.0.0 fork is proceeding well overall. Difficulty is very low at 0.00002865 due to the time gap created the release, so blocks are being found quickly. About 260 blocks have been produced on the 6.0 fork, and there is not a single vote for the malicious grants among those 260 blocks.
Most peers haven’t updated yet, though, so please do that if you haven’t already. The malicious minter or minters appear to have not joined the 6.0.0 fork at this point, though that could change at any time. We need maximum minting power on the 6.0.0 fork to ensure they won’t succeed in passing the grants if they join.
Support for the malicious grants on the 6.0.0 fork stands at 42.6% in the last 10,000 blocks, which is the interval used by the protocol. Let’s push that down!
More than 900 blocks have been minted on the 6.0.0 fork in the last three hours, without a single vote for the malicious grants. This reflects very low difficulty and very high support of the fork from active minters.
Approximately 43% of network nodes are running on 6.0.0.
We still need everyone to upgrade, but the fork is certainly on track for success, with a high degree of consensus.
When the 6.0.0 fork began, support for the malicious grants were at 42.6%. At the moment, support in the 10,000 block protocol interval has been pushed down to 28.6%. However, there has not been a single vote for the malicious grants since the 6.0.0 fork. This means that if voting continues in the same pattern, support for the malicious grants for the 10,000 block protocol interval will fall to 0% within a couple days.
The fork has been a success. The malicious grants have been defeated. BlockShare holders are united on the 6.0.0 fork. Difficulty is rising quickly, which suggests the chain is much more secure than a week ago.
Try adding the following to the file bcexchange.conf and restart B&C Exchange Wallet. Please ask if you don’t know where to find the configuration file.
Currently, in the 10,000 block protocol interval, support for the malicious grants that made the fork necessary currently stands at exactly 0%. That is what we want!
If I replace my old walletC.dat file in this new release I get a crash on startup (tried both windows and macos) . used to work fine with older version of the client.
