Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Release Notes: BitShares Core 3.3.0 #1892
The BitShares Core software has been updated to the 3.3.0 Feature 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 and improvements but does not include any changes to the consensus protocol.
Documentation for users may be be found at How BitShares Works.
Documentation for BitShares developers may be now be found at the new BitShares Developer Portal.
Who Should Upgrade?
No upgrade is required by any operator of a validation node. Yet many operators will benefit by upgrading.
Operators of API nodes should upgrade to support client software that attempt to
Instructions for configuring a node to track the total amount in collateral can be found in the API section.
Operators of ElasticSearch nodes should upgrade to support Get operation by ID and serving
Block producing nodes will benefit due to enable to load block signing keys from files.
All node operators will benefit from
Users of the command line interface wallet (CLI) will benefit from the ability to sign messages on behalf of their account (1878).
Operators of public API nodes should add an entry into their configuration file per the instructions in the API section.
Please check the 3.2.0 Release Notes for more information if you are upgrading from a version prior to 3.2.0.
The changes for 3.3.0 Feature Release are summarized below.
|Track total amount in collateral||1089, 1781, 1893||1836, 1889, 1894|
|Add optional auto-subscription parameters to APIs:
|ES Plugin: Get operation by ID; support
Public API Node operators should enable the new api_helper_indexes plugin to track collateral by adding the entry
api_helper_indexes to the
plugins entry of the node's configuration file (
config.ini), typically, if the line looks like this:
# Space-separated list of plugins to activate plugins = witness account_history market_history grouped_orders
should change it to:
# Space-separated list of plugins to activate plugins = witness account_history market_history grouped_orders api_helper_indexes
|Suppress p2p logs||978||1875|
|Witness node switch to correct fork on restart if was shut down on another long fork||1703||1832|
|Remove seed node with missing DNS record||-||1879|
|Fix market ticker volume underflow issue||1883||1885, 1933|
|Witness node accepts block signing keys from file||-||1812|
Command Line Interface Wallet (CLI)
|Put seed nodes into separate file||-||1809|
|Add htlc parameters to developer genesis||-||1833|
|Refactor CLI register_account and create_account_with_private_key commands, remove duplicate code||-||1811|
|Database_api code refactory||-||1891, 1920|
|Clean up FC, support native 128-bit integers||998, 1584, 1660,1816||FC-137, FC-140, 1789, 1917, 1927, 1941|
|Fix optional API argument bug||1898||FC-145, FC-146, 1912|
|Modified CMakeLists.txt for static linking of libcurl||-||1872|
|Harden binaries through defensive compilation and linking||-||1810|
|Make Travis use multi-stage build||-||1890|
|CMake cleanup & MinGW support||1948||FC-121, FC-151, 1949|
|Upgrade to newer versions of MSVC compiler||1646||1840|
|Support building with Windows 10 / VS 2019 / Boost 1.70||1735||Websocketpp-3, FC-144, FC-147, 1912|
|Support Apple Xcode 10.1 / clang 4.0.1||1952||FC-152|
|Fix build with different genesis file||1965||1966|
|Create reproducible binary downloads with gitian||897||bitshares-gitian|
|Add protocol to libraries doc||1873||1877|
|Update api and cli docs||-||1862, 1863, 1866|
|Update private testnet doc||1861||Dev 154, Wiki|
|Improve help message of get_dev_key||-||1888|
|Generate doxygen docs for FC and other libraries||741||1851, FC-141|
|Fix chain_test: Committee and witnesses initialization in genesis||-||1835, 1928|
@abitmore You are correct that the build requirements changed in 3.2.0. My minor concern was that the usage of the word "since" could be interpreted to include or exclude the mentioned release; I was thinking exclude. My suggestion is to rephrase to "starting since" or "starting in" to convey that it includes the mentioned release.
In file included from /root/bitshares-core/libraries/fc/src/network/tcp_socket.cpp:4:0: