-
Notifications
You must be signed in to change notification settings - Fork 649
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
Release Notes: BitShares Core 4.0.0 #2026
Milestone
Comments
Is the |
Please make sure that all pull requests listed in https://github.com/bitshares/bitshares-fc/milestone/3?closed=1 are included in the release notes. Thanks. |
Done (in anticipation of #2042) |
11 tasks
Updated with changes from test-4.0.3 |
Updated with changes from test-4.0.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release Notes
The BitShares Core software has been updated to the 4.0.0 Protocol Release. 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
Thursday, July 30, 2020 13:55:00 UTC
(2020-07-30T13:55: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 operators must upgrade to handle the protocol upgrade and to benefit from performance improvements.
Operators of API nodes will be able to configure custom limitations on their API nodes as described in the API section.
Precautions
Thursday, July 30, 2020 13:55:00 UTC
Upgrading from Any Version
Delayed Node
The
witness_node
program can be configured to serve the features that were previously provided by thedelayed_node
program. Therefore thedelayed_node
program is no longer supported. Instructions for configuring a witness node to act as delayed node can be found in the Wiki.Elastic Search Plugin
The default values for the Elastic Search Plugin have been changed. These changes are summarized under Elastic Search Plugin.
Custom Operations Plugin
A new
custom_operations
plugin is added in this release which is enabled by default for new nodes. The plugin stores account catalogs ofkey=>value
data using custom operations. The feature is expected to be utilized by several client applications including the reference UI and the BTS++ mobile App in the near future. Existing public API nodes should enable it.API Helper Indexes Plugin
The
api_helper_indexes
plugin is now required for serving several existing critical APIs. Public API nodes should enable it. Please check the API section for more info.Upgrading from 3.2.0
Operators of API nodes need to edit their configuration file per the instructions in the 3.3.0 Release Notes API section.
Upgrading from before 3.2.0
Please check the 3.2.0 Release Notes for more information if you are upgrading from a version prior to 3.2.0.
Note: the minimum build requirements have changed starting from the 3.3.0 Feature Release:
Obtain the Source Code
The source code may be obtained by checking out the 4.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.
How to Upgrade with Docker
The latest Docker image may be found at BitShares Core Docker page and updated with
Binaries of the command line interface (CLI) wallet and the node software are pre-built and available for download.
Note: These binary builds are reproducible and were signed using Gitian. Please check the README if you want to verify and/or contribute.
9482f0ef03e4df2fdd08c30e535709940925fd2ac0eccbe19c399316e57f0961
25a28802d6bd44f9d516ade2b605ea6e5c55fdbddcf801c638be11f1c92ca0a7
5d62f634633693e0a89dd86fdc0314ac0edb2fdc0d9b1437b84c62c5167270b7
The changes for 4.0.0 Protocol Release are summarized below.
Node Functionality
Node Plug-ins
Default settings for the Elastic Search Plugin have changed.
elasticsearch plugin:
_elasticsearch_operation_object
is defaulted totrue
_elasticsearch_operation_string
is defaulted tofalse
es_objects plugin:
_es_objects_limit_orders
is defaulted tofalse
General instructions for configuring Elastic Search are available here.
api_helper_indexes
plugin is now required for several critical APIs. For API node operators, please enable the plugin if these APIs are used by your clients.get_limit_orders_by_account
APIhtlc_redeemed_operation
htlc_refund_operation
get_all_workers
API to query only worker objects that have expired or not expired.get_trade_history
API andget_trade_history_by_sequence
APIget_full_accounts
APICommand Line Interface Wallet (CLI)
sign_transaction2
andsign_builder_transaction2
commands to explicitly specify keys for signing transactionsSoftware Design
exception::to_detail_string()
delayed_node
programBuild Process and Continuous Integration
cat-parts
andembed_genesis
Documentation
Unit Tests
Docker
@abitmore
@christophersanborn
@crazybits
@crypto-ape
@heifner
@ioBanker
@jmjatlanta
@manikey123
@MichelSantos
@mvandeberg
@nathanhourt
@OpenLedgerApp (Alexey Frolov and ddylko)
@oxarbitrage
@pmconrad
@ryanRfox
@spartucus
The text was updated successfully, but these errors were encountered: