Skip to content
ac1cfc0
Compare
Choose a tag to compare

The BitShares Core software has been updated to the 6.0.1 Bugfix 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 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 found at the BitShares Developer Portal.

Who Should Upgrade

Nodes with the ElasticSearch Operations plugin enabled need to be upgraded to the 6.0.1 version before the BitShares Mekong (6.x) protocol is activated. Note: the scheduled protocol upgrade time is Tuesday, January 11, 2022 14:00:00 UTC (2022-01-11T14:00:00Z).

Other nodes can be kept at 6.0.0 or upgraded to 6.0.1.

Please check the release notes of the 6.0.0 version for more info about the BitShares Mekong update.

How To Upgrade

Precautions

  • For nodes running versions earlier than 6.0.0, a blockchain replay will automatically be performed after the validation node software is restarted. This typically takes a few hours on a modern CPU.

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.

docker pull bitshares/bitshares-core:6.0.1

How to Upgrade from Source Code

Note:

  • The code base requires a compiler that supports the C++ 14 standard
  • The minimum supported boost version is 1.58, the maximum is 1.74
  • The minimum supported CMake version is 3.2
  • For Ubuntu users, it is recommended to build in Ubuntu 20.04 LTS (Focal Fossa). Ubuntu 16.04 LTS (Xenial Xerus) is no longer supported.

Obtain the Source Code

The source code may be obtained by checking out the 6.0.1 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 for download

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 built using Gitian. Please check the README of Gitian if you want to verify and/or contribute.
  • Starting from version 6.0.1, pre-built Linux binaries will not run on Ubuntu 16.04 LTS (Xenial).
Platform SHA256 Checksum
Linux 675135708df9a23eef4261d0fe1b6023e74bcff476b81cedf9370975f1ee029f
macOS 4364347ac8555cab730f0d6ef802a1429eebf5526a70440afc4605d6edc658c1
Windows 756f4eb6d12c614790b2152cf8c82c3325faa0f81f86965887877d3b8c0ffbee

Changes

The changes for 6.0.1 Bugfix Release are summarized below.

Node Plugins

Description Plugins Issue Pull Request
Fix ElasticSearch plugin for credit offers ElasticSearch Operations 2549 2553

Release Contributors

@abitmore (https://github.com/abitmore)

e9da444
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the BitShares Public Test Network (Testnet) but NOT the BitShares Mainnet.

Testnet nodes with the ElasticSearch Operations plugin enabled need to be upgraded. No need to upgrade other nodes.

Change list:

Please check the draft release notes of BitShares Mekong 6.0.1 for more info.

Docker image: docker pull bitshares/bitshares-core:test-6.0.3.

Linux, Windows and macOS binary files pre-built with BitShares-Gitian version test-6.0.3 are available for download.

Platform SHA256 Checksum
Linux 988d0b7d0dc5fa974458c8790a75b7d7c719dd659fe58d1b8fba9b2c2514a78e
macOS 87115fe31af65a9f9518c40a96a79f38de4e9bfd246c66b5c0950c735b29132e
Microsoft Windows 57261ab817d6821dcc7b250906a0100ee92f2f0c54e8d69e9a05359fa43e1b29
e52b9ff
Compare
Choose a tag to compare

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.

Who Should Upgrade

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.

How To Upgrade

Precautions

  • All validation nodes must complete their upgrade prior to Protocol Activation.
  • A blockchain replay will automatically be performed after the validation node software is restarted. This typically takes a few hours on a modern CPU.

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.

docker pull bitshares/bitshares-core:6.0.0

How to Upgrade from Source Code

Note:

  • The code base requires a compiler that supports the C++ 14 standard
  • The minimum supported boost version is 1.58, the maximum is 1.74
  • The minimum supported CMake version is 3.2
  • For Ubuntu users, it is recommended to build in Ubuntu 20.04 LTS (Focal Fossa). Ubuntu 16.04 LTS (Xenial Xerus) is no longer supported.

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 for download

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 built using Gitian. Please check the README of Gitian if you want to verify and/or contribute.
  • Starting from version 6.0.0, pre-built Linux binaries will not run on Ubuntu 16.04 LTS (Xenial).
Platform SHA256 Checksum
Microsoft Windows b721383133d56fd2a6469a2aac73c92f7fe518f48a2d6a2484d1dd9dcf6c5527
Mac c5c2ee313233aa06c42ea08f9dd747261dec61399ff1011b9f93b3553a84b868
Linux 042740d4e816b80d909d8c82acbefb3ddd20e5b833cace2cfd1816be090eaac1

Changes

The changes for 6.0.0 Protocol Release are summarized below.

Protocol

Description Issue Pull Request
Add no-collateral funding feature (SameT Funds) 2351 2469, 2474, 2476, 2523
Add simple collateralized P2P funding feature (Credit Offers and Credit Deals) 2362 2479, 2502, 2511
Add 3 new black swan response methods 2467 2499, 2510
Add missing asset authorization checks for certain operations 972, 973 2468
Add option for MPA owners to disable collateral bidding 2281 2504, 2536
Allow bitasset options to be updated after GS 2282 2506
Match force-settlements with margin calls at normal margin call fill price 2481 2489
Revive GSed bitassets based on ICR rather than MCR 2290 2505
Skip asset authorization checks for from_account for override_transfer 2295 2465
Update liquidity pool exchange operations to comply with whitelist and blacklist market settings 2350 2462, 2507
Fix a bug that some non-UIA asset issuer permission bits (e.g. witness_fed_asset) can be configured on UIA via asset_update_operation - 2499
Allow borrowers to close debt positions even when there is no sufficient price feeds - 2499
Allow updating an existing debt position or creating a new debt position if to trigger a margin call and the debt position is not fully filled but the remaining debt position's CR is higher than ICR - 2499
Debt positions with CR not greater than MCR will pay margin call fees at the time of global settlement - 2489

Node Functionality

Description Issue Pull Request
Delete unneeded directories when writing object database to disk - 2485

Node Performance and Stability

Description Issue Pull Request
Clear operation_results when generating block 2527 2475, 2528
Remove BSIP-40 support for unused operations - 2482

Node Plugins

Description Plugins Issue Pull Request
Fix liquidity pool deposit statistics Market History - 2471
Notify all related accounts on account creation Account History 265 2480
Fix a crash when starting the ElasticSearch plugin ElasticSearch Operations 2490 2495

API

Please check the linked pull requests for more info and documentation.

Description Issue Pull Request
The get_block API will return an empty operation_results field for blocks produced by nodes with version 6.0.0 or higher. The operation results can still be retrieved via get_account_history and related APIs. - 2475
The unused extensions field is removed from asset_settle_cancel_operation - 2489
The return value of asset_settle_operation is now a new type extendable_operation_result - 2499
New APIs for querying SameT Funds - 2469
New APIs for querying Credit Offers and Credit Deals - 2479
Fix liquidity pool deposit statistics - 2471
Fix liquidity pool history APIs - 2517

Software Design

Description Issue Pull Request
Add defensive check to mute SonarScanner warning - 2540

Build Process and Continuous Integration (CI)

Description Issue Pull Request
Build Docker images with Github Actions 2472 2514
Upgrade the Docker base image to Ubuntu 20.04 LTS (Focal Fossa) - 2473
Fix Gitian Windows build string table overflow issue by using Ubuntu 20.04. LTS (Focal Fossa) 2520 Gitian-50
Phase out Ubuntu 16.04 2217, Gitian-49 Gitian-51
Add dependabot.yml for GitHub Actions - 2512
Add OS version to cache key in sonar-scan workflow - 2486, 2487
Update Sonar Scanner configuration - 2437, 2458, 2518

Documentation

Description Issue Pull Request
Fix an error in README.md - 2529, 2533, 2534

Release Contributors

@abitmore (https://github.com/abitmore)
@xiao93 (https://github.com/xiao93)

08e62a2
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the BitShares public test network (Testnet) but NOT the BitShares Mainnet.

It is recommended to upgrade Testnet API nodes. It is not required to upgrade other nodes.

Change list:

Please check the draft release notes of BitShares-Core version 6.0.0 "Mekong" for more info.

Docker image: docker pull bitshares/bitshares-core:test-6.0.2.

Linux, Windows and macOS binary files pre-built with BitShares-Gitian version test-6.0.2 are available for download.

a7884c6
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the BitShares public test network (Testnet) but NOT the BitShares Mainnet.

This pre-release contains a bugfix. It is a soft fork.

All Testnet nodes need to be upgraded as soon as possible.

Change:

Please check the draft release notes of BitShares-Core version 6.0.0 "Mekong" for more info.

Docker image: docker pull bitshares/bitshares-core:test-6.0.1.

Linux, Windows and macOS binary files pre-built with BitShares-Gitian version test-6.0.1 are available for download.

5869dc5
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the BitShares public test network (Testnet) but NOT the BitShares Mainnet.

The activation time of the 6.0 protocol on the BitShares Public Testnet is set to Tuesday, November 2, 2021 14:02:00 UTC, or the ISO-8601 format 2021-11-02T14:02:02Z.

All Testnet nodes need to be upgraded before the planned activation time.

Please check the draft release notes of version 6.0.0 for more info.

Docker image: docker pull bitshares/bitshares-core:test-6.0.0.

Pre-built Linux binaries, Windows binaries and macOS binaries are available for download (built with BitShares-Gitian (version test-6.0.0)).

c06d09c
Compare
Choose a tag to compare

Release Notes

The BitShares Core software has been updated to the 5.2.1 Bugfix Release. The codename of the 5.x releases is "Splash". The BitShares Core software is used to build the validation nodes that perform consensus of all transactions on the BitShares blockchain. This release includes fixes about node stability and documentations 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 found at the BitShares Developer Portal.

Who Should Upgrade

It is recommended that all nodes be upgraded to benefit from the stability improvements introduced in this release and the benefits introduced in the 5.2.0 Feature Release, although it is not required.

How To Upgrade

Precautions

  • For nodes running versions earlier than 5.2.0, a blockchain replay will automatically be performed after the validation node software is restarted. This typically takes a few hours on a modern CPU.

How to Upgrade from Source Code

Note:

  • The code base requires a compiler that supports the C++ 14 standard
  • The minimum supported boost version is 1.58, the maximum is 1.74
  • The minimum supported CMake version is 3.2
  • For Ubuntu users, it is now supported and recommended to build in Ubuntu 20.04 LTS

Obtain the Source Code

The source code may be obtained by checking out the 5.2.1 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

docker pull bitshares/bitshares-core:5.2.1

Binaries for download

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.

Platform SHA256 Checksum
Microsoft Windows 4e800939886adfad8b5404f6f754d1c90f777a7135f0d7aac0ce43c5d5d9c7a6
Mac 8af13a35e75f7646b4006ea4ca420b6cf16badeee3d0150c1263cb918d7daacc
Linux c48e28498f7b062df7e616f402b1ad5526b344f2a26eaf0c9b75b6269eca1bbf

Changes

The changes for 5.2.1 Bugfix Release are summarized below.

Node Performance and Stability

Description Issue Pull Request
Fix a node synchronization issue 2428, 2434, 2438 2445
Fix P2P log messages appear in console and default.log 2435 2436
Add seed nodes - 2444, 2450

Documentation

Description Issue Pull Request
Fix Doxygen warnings 2433 2443
Update links and wording in README - 2439, 2441
Update version - 2446
Update contributors - 2452

Release Contributors

@abitmore (https://github.com/abitmore)
@technologiespro (https://github.com/technologiespro)
@xiao93 (https://github.com/xiao93)

8a5995d
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the public test network (testnet) but NOT the BitShares Mainnet.

Please check the draft release notes of version 5.2.1 for more info.

Docker image: docker pull bitshares/bitshares-core:test-5.2.1.

1f3e2e9
Compare
Choose a tag to compare

Release Notes

The BitShares Core software has been updated to the 5.2.0 Feature Release. The codename of the 5.x releases is "Splash". 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 bug fixes 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 found at the BitShares Developer Portal.

Who Should Upgrade

It is recommended that all nodes be upgraded, although it is not required.

API nodes will benefit from the new API, performance and stability improvements, and functionality improvements.

Block producers and other nodes will benefit from the stability improvements.

Command-line interface (CLI) wallet users will benefit from the CLI improvements.

How To Upgrade

Precautions

  • A blockchain replay will automatically be performed after the validation node software is restarted. This typically takes a few hours on a modern CPU.

How to Upgrade from Source Code

Note:

  • The code base requires a compiler that supports the C++ 14 standard
  • The minimum supported boost version is 1.58, the maximum is 1.74
  • The minimum supported CMake version is 3.2
  • For Ubuntu users, it is now supported and recommended to build in Ubuntu 20.04 LTS

Obtain the Source Code

The source code may be obtained by checking out the 5.2.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

docker pull bitshares/bitshares-core:5.2.0

Binaries for download

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.

Platform SHA256 Checksum
Microsoft Windows e235de2b70ff12fea5a75621b83fc5050d45b755156bc3ab0ddf6ab18ee421ab
Mac b2c85bff171fdd908ea2e001944cb51d5d73f1df4b5133f8712642bc682c7add
Linux 68dfc7afc2a3a32c8f5a4491e8956173bd9d4e0151736476bf698670b1ad03a9

Changes

The changes for 5.2.0 Feature Release are summarized below.

Node Functionality

Description Issue Pull Request
Disable p2p network when delayed_node plugin is enabled 104 2040, 2393
Fix data error in (virtual) execute_bid_operation - 2363
Fix transaction loss after broadcast 2376 2383

Node Performance and Stability

Description Issue Pull Request
Reduce the allowable range of negative latency - 2370
Improve market ticker read performance via chunks - 2358
Update seed nodes - 2353, 2422, 2423

API

Please check the linked pull requests for more info and documentation.

Description Issue Pull Request
Add database API get_liquidity_pools_by_one_asset to query for liquidity pools by any one asset in the pool 2356 2365

Command-Line Interface (CLI) Wallet

Description Issue Pull Request
Fix brain-key compatibility between bitshares-core and bitshares-ui 2354 2355
Fix CLI get_account_history_by_operations ordering - 2359
Print more info in account history in CLI 2296 2360, 2384
Add CLI commands get_account_name, get_asset_id, get_asset_symbol and get_asset_name - 2364
Fix sign_memo command for signing with public keys - 2386

Software Design

Description Issue Pull Request
Support building with Boost 1.74 - FC-226, 2406
Support building in Ubuntu 20.04 LTS 2216 FC-234, FC-236, 2347, 2349
Fix assigning instead of comparing - FC-232
Define related functions only when have editline - FC-233
Force TLSv1.2 or above when using libcurl - 2368
Set program options with a template function in tests - 2402
Fix code smells 2101 2372, 2390, 2392
Remove unnecessary include of boost/test/auto_unit_test.hpp 2414 2415
Remove unused code - 2424

Build Process and Continuous Integration (CI)

Description Issue Pull Request
Fix cache for matrix in Github Actions - FC-239, 2366
Integrate SonarScanner in Github Actions workflow 2314 FC-240, FC-241, 2367, 2391, 2401
Fix MinGW build in Github Actions 2427 2426

Documentation

Description Issue Pull Request
Fix typo in docs of serializable _types - FC-235
Fix description for the FC namespace in doxygen 2342 FC-237
Update copyright notices about static_variant - FC-238
Update comment about liquidity_pool_exchange_operation market fee sharing - 2382
Fix doxygen docs in node_impl.hxx 2375 2403, 2405, 2418
Document fees returned by liquidity_pool_exchange_operation 2346 2404
Fix broken link in README of performance_test - 2416
Update mail map and contributors - FC-242, 2426, 2429

Unit Tests

Description Issue Pull Request
Randomize index prefixes in ES tests, fix random failures 2283 2371, 2373
Fix two_node_network connection failure in app_test 39 2374
Fix two_node_network test case failure after transaction broadcast 2378 2377
Fix random HTLC test failures 2219 2381
Add uia_tests in cli_test - 2385, 2389
Add test cases for liquidity pool APIs - 2387
Fix random cli_test failure due to conflict on listening ports 2409 2411

Release Contributors

@abitmore (https://github.com/abitmore)
@pmconrad (https://github.com/pmconrad)
@sinetek (https://github.com/sinetek)
@xloem (https://github.com/xloem)
@hammadsherwani (https://github.com/hammadsherwani)

85d86a9
Compare
Choose a tag to compare
Pre-release

Note: this pre-release is for the public test network (testnet) but NOT the BitShares Mainnet.

Please check the draft release notes of version 5.2.0 for more info.

Docker image is available: docker pull bitshares/bitshares-core:test-5.2.0 .