![](https://images.hive.blog/p/C3TZR1g81UNaPs7vzNXHueW5ZM76DSHWEY7onmfLxcK2iPdiAa6tkfVRkpf9tvraQ9z55QS9fmMKbN32DMR4fCUEJKM2bGoquU7xeXZ7ZoKe6yrMrAtFTxA) The [BitShares](https://bitshares.org) Core software has been updated to the [6.0.0 Protocol Release](https://github.com/bitshares/bitshares-core/milestone/34?closed=1). The codename of the 6.x releases is [*"Mekong"*](https://github.com/bitshares/bitshares-core/releases/tag/6.0.0). 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](https://how.bitshares.works). Documentation for BitShares developers may be found at the [BitShares Developer Portal](https://dev.bitshares.works). * [Who should upgrade](#who-should-upgrade-6-0-0) * [How to upgrade](#how-to-upgrade-6-0-0) * [Binaries for download](#binaries-for-download-6-0-0) * [Changes](#changes-6-0-0) * [Release contributors](#release-contributors-6-0-0) ##

Who Should Upgrade **All nodes need to be upgraded** to handle the [protocol upgrade](#protocol-6-0-0). Note: some API changes may break existing client applications, as described in [API changes section](#api-6-0-0). ##

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](https://hub.docker.com/r/bitshares/bitshares-core/) 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](https://github.com/bitshares/bitshares-core/releases/tag/6.0.0). Download the source at: * [6.0.0.zip](https://github.com/bitshares/bitshares-core/archive/6.0.0.zip) * [6.0.0.tar.gz](https://github.com/bitshares/bitshares-core/archive/6.0.0.tar.gz) #### 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: * [Ubuntu](https://github.com/bitshares/bitshares-core/wiki/BUILD_UBUNTU) * [macOS](https://github.com/bitshares/bitshares-core/wiki/Building-on-macOS) * [Windows](https://github.com/bitshares/bitshares-core/wiki/BUILD_WIN32) #### 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](https://github.com/bitshares/bitshares-gitian/tree/6.0.0). Please check the [README of Gitian](https://github.com/bitshares/bitshares-gitian/blob/master/README.md) 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](https://github.com/bitshares/bitshares-core/releases/download/6.0.0/bitshares-core-6.0.0-win64-bin.zip)|`b721383133d56fd2a6469a2aac73c92f7fe518f48a2d6a2484d1dd9dcf6c5527`| |[Mac](https://github.com/bitshares/bitshares-core/releases/download/6.0.0/bitshares-core-6.0.0-macos64-bin.tar.bz2)|`c5c2ee313233aa06c42ea08f9dd747261dec61399ff1011b9f93b3553a84b868`| |[Linux](https://github.com/bitshares/bitshares-core/releases/download/6.0.0/bitshares-core-6.0.0-linux-amd64-bin.tar.bz2)|`042740d4e816b80d909d8c82acbefb3ddd20e5b833cace2cfd1816be090eaac1`| #

Changes The changes for [6.0.0 Protocol Release](https://github.com/bitshares/bitshares-core/milestone/34?closed=1) are summarized below. ##

Protocol

|Description|Issue|Pull Request| |-|-|-| |Add no-collateral funding feature (SameT Funds)|[2351](https://github.com/bitshares/bitshares-core/issues/2351)|[2469](https://github.com/bitshares/bitshares-core/pull/2469), [2474](https://github.com/bitshares/bitshares-core/pull/2474), [2476](https://github.com/bitshares/bitshares-core/pull/2476), [2523](https://github.com/bitshares/bitshares-core/pull/2523)| |Add simple collateralized P2P funding feature (Credit Offers and Credit Deals)|[2362](https://github.com/bitshares/bitshares-core/issues/2362)|[2479](https://github.com/bitshares/bitshares-core/pull/2479), [2502](https://github.com/bitshares/bitshares-core/pull/2502), [2511](https://github.com/bitshares/bitshares-core/pull/2511)| |Add 3 new black swan response methods|[2467](https://github.com/bitshares/bitshares-core/issues/2467)|[2499](https://github.com/bitshares/bitshares-core/pull/2499), [2510](https://github.com/bitshares/bitshares-core/pull/2510)| |Add missing asset authorization checks for certain operations|[972](https://github.com/bitshares/bitshares-core/issues/972), [973](https://github.com/bitshares/bitshares-core/issues/973)|[2468](https://github.com/bitshares/bitshares-core/pull/2468)| |Add option for MPA owners to disable collateral bidding|[2281](https://github.com/bitshares/bitshares-core/issues/2281)|[2504](https://github.com/bitshares/bitshares-core/pull/2504), [2536](https://github.com/bitshares/bitshares-core/pull/2536)| |Allow bitasset options to be updated after GS|[2282](https://github.com/bitshares/bitshares-core/issues/2282)|[2506](https://github.com/bitshares/bitshares-core/pull/2506)| |Match force-settlements with margin calls at normal margin call fill price|[2481](https://github.com/bitshares/bitshares-core/issues/2481)|[2489](https://github.com/bitshares/bitshares-core/pull/2489)| |Revive GSed bitassets based on ICR rather than MCR|[2290](https://github.com/bitshares/bitshares-core/issues/2290)|[2505](https://github.com/bitshares/bitshares-core/pull/2505)| |Skip asset authorization checks for from_account for override_transfer|[2295](https://github.com/bitshares/bitshares-core/issues/2295)|[2465](https://github.com/bitshares/bitshares-core/pull/2465)| |Update liquidity pool exchange operations to comply with whitelist and blacklist market settings|[2350](https://github.com/bitshares/bitshares-core/issues/2350)|[2462](https://github.com/bitshares/bitshares-core/pull/2462), [2507](https://github.com/bitshares/bitshares-core/pull/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](https://github.com/bitshares/bitshares-core/pull/2499)| |Allow borrowers to close debt positions even when there is no sufficient price feeds|-|[2499](https://github.com/bitshares/bitshares-core/pull/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](https://github.com/bitshares/bitshares-core/pull/2499)| |Debt positions with CR not greater than MCR will pay margin call fees at the time of global settlement|-|[2489](https://github.com/bitshares/bitshares-core/pull/2489)| ##

Node Functionality |Description|Issue|Pull Request| |-|-|-| |Delete unneeded directories when writing object database to disk|-|[2485](https://github.com/bitshares/bitshares-core/pull/2485)| ##

Node Performance and Stability

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