approved and published on 06/18/2018
The BitShares Blockchain Foundation is pleased to let everyone know about the upcoming protocol upgrade for the BitShares main network.
After months of development and many weeks of testing on the bitshares testnet, the finalized version
has been tagged in bitshares-core.
This is a protocol upgrade release. All nodes must upgrade before
2018-07-19 14:00:00 UTC.
2.0.180612, you don’t need to do anything special;
2.0.180612, please check release notes of 2.0.180425 to see if you need to perform additional steps.
bitassetoptions E.G. force settlement delay, backing asset ID or etc;
git fetch origin git checkout 2.0.180612 git submodule sync --recursive git submodule update --init --recursive # it follows the usual compile instructions with cmake and make
The detailed lists of updates, bug fixes and security fixes can be found in the Release Notes
The new docker container has been built by Docker Hub and is available via
docker pull bitshares/bitshares-core:2.0.180612
The new release modifies the blockchain protocol and due to this is a consensus-changing modification. While the usual terminology for this kind of upgrade in other blockchains is hard-fork, we would like to emphasis a new term for Graphene-based blockchains: protocol upgrade. The reasons we distinguish our upgrades from a hard-forks, is that our consensus mechanism - delegated proof of stake (DPOS) - does not allow for the blockchain to split into two (or even more) independent blockchains. BitShares comes with an inherent replay protection and together with BTS holder-approved block producers cannot result in a splitting of the blockchain.
We would like to remind everyone of the mailing lists operated by the BitShares Blockchain Foundation where business operators and users can engage discussions and get the most recent updates, directly. An distinct mailing list for critical operation updates exists, too.