-
Notifications
You must be signed in to change notification settings - Fork 648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft Release Notes: BitShares Core 6.0.0 "Mekong" #2508
Comments
This page summarizing what is new in the 6.0 release is looking good, nice to see all the activity summarized in one place. |
@kjbtsmg the links will be updated and will work when the release is out. Thank you anyway.
|
Ok, cool, i thought that may be the case. |
Released: https://github.com/bitshares/bitshares-core/releases/tag/6.0.0 . Closing this issue. |
Note: the final release page is https://github.com/bitshares/bitshares-core/releases/tag/6.0.0 . This issue is kept for reference.
Release Notes
The BitShares Core software has been updated to the 6.0.0 Protocol Release. The codename of the 6.x releases is "Mekong". The Core software is used to build the validation nodes that perform consensus of all transactions on the BitShares blockchain. This release includes additions, improvements and changes to the consensus protocol.
The scheduled protocol upgrade time is
Tuesday, January 11, 2022 14:00:00 UTC
(2022-01-11T14:00:00Z
).Documentation for users may be be found at How BitShares Works.
Documentation for BitShares developers may be found at the BitShares Developer Portal.
All nodes need to be upgraded to handle the protocol upgrade.
Note: some API changes may break existing client applications, as described in API changes section.
Precautions
How to Upgrade with Docker
The pre-built Docker image can be found on the BitShares Core Docker page and can be downloaded with the following command.
Note:
Obtain the Source Code
The source code may be obtained by checking out the 6.0.0 tag. Download the source at:
Build the Binaries
The binaries may be built by using your pre-existing process, or by following the standard instructions that can be found in the wiki:
Deploy the Binaries
Your standard process for deploying the node software may be used. No additional requirements or precautions will be required to deploy the new release.
Binaries of the command line interface (CLI) wallet and the node software are pre-built and available for download.
Note:
6.0.0
, pre-built Linux binaries will not run on Ubuntu 16.04 LTS (Xenial).b721383133d56fd2a6469a2aac73c92f7fe518f48a2d6a2484d1dd9dcf6c5527
c5c2ee313233aa06c42ea08f9dd747261dec61399ff1011b9f93b3553a84b868
042740d4e816b80d909d8c82acbefb3ddd20e5b833cace2cfd1816be090eaac1
The changes for 6.0.0 Protocol Release are summarized below.
witness_fed_asset
) can be configured on UIA viaasset_update_operation
Please check the linked pull requests for more info and documentation.
get_block
API will return an emptyoperation_results
field for blocks produced by nodes with version6.0.0
or higher. The operation results can still be retrieved viaget_account_history
and related APIs.extensions
field is removed fromasset_settle_cancel_operation
asset_settle_operation
is now a new typeextendable_operation_result
Software Design
Build Process and Continuous Integration (CI)
Documentation
@abitmore (https://github.com/abitmore)
@xiao93 (https://github.com/xiao93)
The text was updated successfully, but these errors were encountered: