• 3.1.0

released at 15/05/2019

Assets 3

Release Notes

The BitShares Core software has been updated to the 3.1.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

All node operators will benefit from performance improvements (1608,1621, 1662) including during replay.

Users of the command line interface wallet (CLI) will benefit from new getter commands for transaction signers and the ability to add signatures to partially signed transactions.

Upgrade Process

Precautions

A replay will automatically be executed after the upgrade.

How to Upgrade from Source Code

Obtain the Source Code

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

Binaries

Binaries of the command line interface (CLI) wallet, node software, and delayed node are pre-built and available for download.

Platform SHA256 Checksum
Microsoft Windows b1d1487a4a99878d3bcf33650dfb5d21462a26acf3cfc654a7646571285350d8
Apple macOS 571aeaca0a32036836febb8f9782ace93a5c1c5d0f03bd8093db3fad53b5fbae
Linux 795628456a40e1d00a22e4f92771e740741269cad17ed900baaf845b59d56427

Changes

The changes for 3.1.0 Feature Release are summarized below.

API

Description Issue Pull Request
get_full_accounts includes htlc; New HTLC APIs 1713 1742
Fix: ElasticSearch-objects plugin does not load genesis data 1652 1717
Add fail_reason to reflection meta of proposal_object 1730 1732
Fix: Inconsistent required_approval_index when loading from disk 1719 1720
Deterministic numbering of virtual operations in account history 1675 1676
Change hard-coded limitations in APIs to configurable 782 1513
Fix permessage_deflate - WebSocket-2

Node Functionality

Description Issue Pull Request
Improve performance of markets 982 1608,1621
Improve fee_schedule::calculate_fee() performance 1660 1662
Skip transaction size check during replay 1619 1716
Reduce precision of numbers in replay output 1666 1674
Bump fc - 1596

Node Plugins

Description Issue Pull Request
Add plugin section headers for auto-generated config.ini 1407 1641

Command Line Interface Wallet (CLI)

Description Issue Pull Request
Fixed saving keys in wallet - 1613
Add get_signed_transaction_signers and get_key_references commands to CLI 1210 1635
Add CLI command to add signatures to a partially signed transaction add_transaction_signature 867 1032
wallet info() change participation to int - 1666
Avoid segfault in CLI bid_collateral command - 1649

Other Wallets

Description Issue Pull Request
Improve js_serializer 1701 1702,1741
Install debug_witness headers 1727

Software Design

Description Issue Pull Request
Remove old hardfork checks 1553 1718
Removed unused header file 1219 1740
Replace smart_ref with shared_ptr 1548 1556
Make chain_parameters::current_fees const 1670 FC-115,1678
valgrind inspired fixes - 1693
Change indentation in quit command - 1684

Build Process

Description Issue Pull Request
Recent build errors on Windows platform 1593 FC-110,FC-111,1633,1704
Support Boost version 1.69 1557 1587,1648
ld: symbol(s) not found for architecture x86_64 Mac issue 1545 1556
Fix compiler warnings - 1515,1597,1721,1736,FC-116,1677

Unit Tests

Description Issue Pull Request
Prove owner->active delegation BSIP-94 1601
cli_tests memory access violation at address: no mapping at fault address 1303 1626

Documentation

Description Issue Pull Request
Update Documentation for initial_chain_id field when creating example genesis 1069 1628
Dynamically linking OpenSSL 1304 DevDocs-111
Add genesis-dev.json and move genesis jsons out of root source directory 1591 1592
Document subscribe_to_market returned values 1258 -

Release Contributors

@abitmore @btsabc @cedar-book @cifer-lee @crypto-ape @jmjatlanta @manikey123 @nathanhourt @OpenLedgerApp @oxarbitrage @pixelplex @pmconrad @xeroc @xloem @xuquan316

  • 3.0.1

released at 09/04/2019

Assets 3

Fixes

  • Added validation to the htlc_extend validation to prevent unwanted extensions
  • Added history entry for all parties involved in an htlc.

Where to Learn More

Who Should Update

  • All validation node operators are required to upgrade prior to Protocol Activation: 23 APR 2019 14:02 UTC as this is a consensus protocol impacting release
  • All API node operators are strongly encouraged to upgrade, as account history IDs could become different between nodes running newer vs older versions
  • All BTS token holders are strongly encouraged to review this release, then vote to support block producers signaling their intention to upgrade prior to protocol activation

How to Update

Precautions

  • All validation nodes must complete their upgrade prior to Protocol Activation: 23 APR 2019 14:02 UTC
  • A blockchain replay will not be necessary if the node was previously updated to 3.0.0.

Obtain the Source Code

  • git client: git clone --recursive --branch 3.0.1 https://github.com/bitshares/bitshares-core.git
  • zip archive:
  • tar.gz archive:

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.

Obtain the Docker Image

The latest Docker image may be found at BitShares Core Docker page and updated with:

docker pull bitshares/bitshares-core

Binaries

Binaries of the command line interface (CLI) wallet, node software, and delayed node are pre-built and available for download.

Platform SHA256 Checksum
Microsoft Windows f44bcf0b95470aecef826ec2e4959adb7112b8f9144bd3d02c36c0a33b1da5c5
Mac afba66fc18ffff89f2ee7b4fe5919aa1ec62c93ffc35d8c4b1332f6d688766ed
Linux 7bf688f56d0555af678bec2cd33f48851844e2b2b3238a767ec8f02764eb3c7a

Changes

A summary of the tasks contained within Protocol Upgrade Release (3.0.1) follows:

Core Functionality

Description Issue Pull Request
Insufficient htlc_extend_operation validation 1696 1699

Release Contributors

@abitmore @jmjatlanta @oxarbitrage @pmconrad @ryanRfox

  • 3.0.0

released at 27/03/2019

Assets 3

What’s New

Fixes

  • MCR Bugfix: Resolves a bug where the call price is inconsistent when the maintenance collateral ratio (MCR) was modified
  • Max Supply: Resolves a bug that could cause supply to grow beyond the intended maximum supply level.
  • Oversized Transactions: Resolves a bug that could allow transactions beyond the size limit.
  • Account Permission Bugfix: Resolves a bug that under certain circumstances a transaction signed by owner key of an account would be rejected

Where to Learn More

Who Should Update

  • All validation node operators are encouraged to upgrade prior to Protocol Activation: 23 APR 2019 14:02 UTC as this is a consensus protocol impacting release
  • All BTS token holders are encouraged to review this release, then vote to support block producers signaling their intention to upgrade prior to protocol activation

How to Update

Precautions

  • All validation nodes must complete their upgrade prior to Protocol Activation: 23 APR 2019 14:02 UTC
  • A blockchain replay will automatically be performed after the validation node software is restarted. This typically takes 90 minutes on a modern CPU

Obtain the Source Code

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.

Obtain the Docker Image

The latest Docker image may be found at BitShares Core Docker page and updated with:

docker pull bitshares/bitshares-core

Binaries

Binaries of the command line interface (CLI) wallet, node software, and delayed node are pre-built and available for download.

Platform SHA256 Checksum
Microsoft Windows 97559647e099c3768565f50cb5f43b0956afa6fd371b442aabdfb6e9acb62cb3
Mac 7c50d0a8f2eb5fdfd4c0c5d86d5bba076ec0acf1ccf256e70d2e4ef8010871eb
Linux 6f893f5bf5a08928c10d9adeaca92204ab150886dbe0da2102118e9aa5ab5a25

Changes

A summary of the tasks contained within Protocol Upgrade Release (3.0.0) follows:

Core Functionality

Description Issue Pull Request
Borrowing MPAs ignores max_supply setting 1465 1498
Call price is inconsistent when MCR changed 1270,1423 1324,1469,1493
Distribute Asset Market Fees to Referral Program (BSIP-43) 1268 1419
Hashed Time-Locked Contract (BSIP-44) BSIPS 103 1370,1475,1535,1538
Prevent oversized transactions 1573 1624
Account permission bugfix 584 1259

Build Process

Description Issue Pull Request
Build fails on macOS due to size_t 1590 1589

Release Contributors

@abitmore @jmjatlanta @oxarbitrage @pmconrad @OpenLedgerApp @ryanRfox

  • 2.0.20190319
Assets 3

The BitShares Core software has been updated to 2.0.20190319. The Core software is used to build the validation nodes that perform consensus of all transactions on the BitShares blockchain. This release includes only 1 bug fix; no new features are added.

Documentation for users may be be found at How BitShares Works.

Documentation for BitShares developers may be be found at the Developer Portal.

Who Should Upgrade?

All node operators are recommended to upgrade to fix the bug "plugins option ignored in config file" described in #1647

Upgrade Process

Precautions

No special precautions are expected to upgrade this release.

How to Upgrade from Source Code

Obtain the Source Code

The source code may be obtained by checking out:

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

Binaries

Binaries of the command line interface (CLI) wallet, node software, and delayed node are pre-built and available for download.

Platform SHA256 Checksum
Microsoft Windows e224a73e43eff1fd2940c6d32d699ccd944571dc66cf140770a22406033a0e4b
Mac 40455f3eadf28a9fe1ba7fc03cc746bc90f89ded28ab85c40dbc7d6daa2443cb
Linux 7b6d9bbaa897f71709d425ddf07a583eca0f8afdf25f5a26538d2c84d1334b3d

Changes

The changes for the release are summarized below.

Node Functionality

Description Issue Pull Request
"plugins" option in config.ini is ignored 1637 1647

Documentation

Description Issue Pull Request
Support Boost version 1.69 1557 1587, 1648

Release Contributors

@jmjatlanta @oxarbitrage

  • 2.0.190305
Assets 3

The BitShares Core software has been updated to 2.0.190305. The Core software is used to build the validation nodes that perform consensus of all transactions on the BitShares blockchain. This release includes only bug fixes; new new features are added.

Documentation for users may be be found at How BitShares Works.

Documentation for BitShares developers may be be found at the Developer Portal.

Who Should Upgrade?

All node operators are recommended to upgrade to benefit from fixes (1620, 1573).

Upgrade Process

Precautions

A replay will automatically be performed after an upgraded node is restarted.

How to Upgrade from Source Code

Obtain the Source Code

The source code may be obtained by checking out:

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

Command Line (CLI) Wallet Binaries

A binary of the command line interface (CLI) wallet and other tools for Windows is pre-built and available for download.

Platform SHA256 Checksum
Microsoft Windows 82b5887e8f5f0887b8355d0f4fd04a1aae9320f251e6d86b08ea2901156ce634
Mac ff5ad996131e57bc377b3797e455ffd2693e0f7411a09711a85fb7ad98d677e4
Linux 2852519e43d53bfde21eb551cd4637a2219c65365fdfa5d3d1543d98459f4da6

Changes

The changes for the release are summarized below.

Node Functionality

Description Issue Pull Request
Empty 'percent_change' in get_ticker API 1620 1631
Additional check of transaction size in consensus code 1573 1586
Bump the database - Commit 7e8a6b9

Release Contributors

@jmjatlanta @oxarbitrage

  • 2.0.190219
Assets 3

The BitShares Core software has been updated to the 201902 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 multple optimizations and bug fixes but does not include any changes to the consensus protocol. Numerous performance improvements have been made that will benefit all operators of validation nodes including block producers, seeds, and API nodes especially Elastic Search API nodes.

No upgrade or action is required by any users for this release.

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.

All operators will benefit from improvements to performance (1079, 1472, 1095), enhancements (1550), and fixes (1118, 1461).

Operators of API nodes will benefit from enhancements (1051, 842, 1018), and a fix (1490).

Operators of Elastic Search API nodes will benefit from improvements to performance (1541, 1455, 1429).

Upgrade Process

Precautions

A replay will automatically be performed after an upgraded node is restarted.

How to Upgrade from Source Code

Obtain the Source Code

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

CLI Binaries

A binary of the command line interface (CLI) wallet and other tools for Windows is pre-built and available for download at BitShares-Core-2.0.190219-Windows-x64-cli-tools.zip. SHA256 Checksum: 294025a640a5aba4e3f4dc221f8b5018e59757ab4976158f3bb80caa06f83151

For Mac please download BitShares-Core-2.0.190219-macOS-cli-tools.tar.gz. SHA256 Checksum: e8768df6fd36caff1c5894c5a9962557a9c735d782b586ada0fb647837879bea

For Linux please download BitShares-Core-2.0.190219-Linux-cli-tools.tar.gz. SHA256 Checksum: 8a52c3e3522df1d537c4723b3cda21fa9a7fbf675a78269cd8e7765b250b550f

Changes

The changes for 201902 Feature Release are summarized below.

Core Functionality

Description Issue Pull Request
Add last vote time in account object 1393 1449
Update all asset-related API's to support asset symbol as parameter 1051 1272
Expand get_top_markets API to return more data fields 842 1549
(Human-readable message needed for assert) 1018 1531
get_account_history_operations fails with partial_history and stop at 0 1490 1494
database_api::verify_account_authority is broken 1366 1384

Node Functionality

Description Issue Pull Request
Make better use of multi-core servers 1079 1360
Setup Private Testnet --create-genesis-json creates witness_node_data_dir 1118 1529
Review and backport EOS PR 3392 packing/unpacking array-like types 995 FC 100, 103
Get_key_references performance issue? 1472 1499
Cache a pointer to account_statistics_object in account object? 1095 1462
Fix for errors while loading object_database - 1461
Avoid calling exit from within a library 1110 1529
About skip_fork_db flag 1313 1527
Change more 32 bit data fields to 64 bit 1206 1347

Node Plugins

Description Issue Pull Request
Add startup message to all plugins 1459 1502
[Improve plugin loader] PR 1427 1437
Add es-objects-start-es-after-block option - 1541
Add start-es-inserts-after-block option to elasticsearch plugin 1455 1458
Add an adaptor to es_objects and template function to reduce code - 1429

Command Line Interface Wallet (CLI)

Description Issue Pull Request
Capture Ctrl+C in cli_wallet when not in daemon mode 1193 1232

Build Process

Description Issue Pull Request
BitShares Core uses Boost::Signal, which is deprecated 1512 1503, 1514, FC 101
(Mac) std::min requires 2 matching parameters 1560 1561
Build warnings - throw within destructor 1246 1510, 1511
(OpenSUSE) Linking failure 1504 1504, 1516
Build simplification - 1547
cli_wallet build failure on Ubuntu 18.04 1418 1539
Fix build errors and a warning - 1421, 1426
Bump fc after re-improving compile time resource usage - 1417
Bump fc and fix node - 1405
BitShares-fc compilation warnings 1383 FC 84

Unit Tests

Description Issue Pull Request
Finish / fix price_to_string_test 1186 1518

Documentation

Description Issue Pull Request
Add a readme file to programs directory 1532 1534
Add network-mapper to programs README 1558 1559
Change description of delayed_node option 1407 1410

Miscellaneous

Description Issue Pull Request
Cleanup - 1533
Rename API param operation_id to operation_type - 1544
Port Network Mapper from bitshares-1 1550 1555

Release Contributors

@abitmore @HarukaMa @cogutvalera @jmjatlanta @nathanhourt @oxarbitrage @pmconrad

  • 2.0.181221
Assets 3

This is a bugfix release. Upgrade is strongly recommended for all nodes!

Fixes

  • 1479

Binary SHA256 Checksum

f775b1f26031d6e9b21507f1e73e150082a5df31f0ec8df835527b5ea3e72def
  BitShares-Core-2.0.181221-Windows-x64-cli-tools.zip

d55953556cb41e863aad914f751913b8fa7d551880fc861c82c4a797e2077803
  BitShares-Core-2.0.181221-Linux-cli-tools.tar.gz

66910240726d3ebf94f3d0121224f3575e3c7fd09d84e3363081a09b9581619d
  BitShares-Core-2.0.181221-macOS-cli-tools.tar.gz

  • 2.0.181127
Assets 3

This is an emergency release to fix a stuck chain.

All nodes must upgrade.

Replay will happen automatically.

SHA256 Checksums: BitShares-Core-2.0.181127-Linux-cli-tools.tar.gz     c04daf2d879c65c12baf5b46fa30a444c06d677fe86d73ce7acb9cddad54c5f8

BitShares-Core-2.0.181127-macOS-cli-tools.tar.gz     ba90de34905cbc24305060214229fc768b44c0ea7f968ca61b3a1e10ed3036d2

BitShares-Core-2.0.181127-Windows-x64-cli-tools.zip     5f68e1efa32655fc428ca95c46fda5454e768e8c12f652f9a1e4f58fabdff852

  • 2.0.181120
Assets 3

The BitShares community discovered a problem in the UI introduced by a change in bitshares-core in the 2.0.181105 release. The voting page of the UI was blank, caused by the removal of the budget_object in PR 1213.

This release reverts just that change, and allows the voting page to be displayed correctly.

No upgrade is required by any operator of a validation node. Yet operators of API nodes should upgrade to this release. Users of the BitShares UI will benefit when the node they connect to has been upgraded.

SHA256 Hashes

BitShares-Core-2.0.181120-Linux-cli-tools.tar.gz 35eaa18bdd1a0943ca95a23abdbf40bc57eb502a7b1aafd71c2363681fb4a0e2

BitShares-Core-2.0.181120-Windows-x64-cli-tools.zip 58045fa7f50a3c8818790d69f29fa250d719e8535bd334cac55c576f0b54bf1c

BitShares-Core-2.0.181120-macOS-cli-tools.tar.gz 8f9f59d12eba0c519c4d5f875697abd8cbd0b1b441d6c6609e9e5c38f6824b18

  • 2.0.181105
Assets 3

The BitShares Core software has been updated to the 201810 Feature Release. The Core software is used by validation nodes which perform consensus of all transactions on the BitShares blockchain. This release includes new features, optimizations, and bug fixes but does not include any changes to the consensus protocol.

No action is required if you do not operate a validation node or the command line interface (CLI) wallet.

Numerous performance improvements have been made to the software that will benefit all operators of validation nodes including block producers, seed nodes, and API nodes, especially those using the Elasticsearch plugin.

Documentation for BitShares developers may be now be found at the new BitShares Developer Portal (https://dev.bitshares.works).

Who Should Upgrade?

No upgrade is required by any operator of a validation node. Yet many operators will benefit by upgrading.

All operators will benefit from performance improvements (915, 1327, 1359) and fixes (1024, 1203, 1286, 1325).

Operators of block producing nodes will benefit from performance improvements (1251), safety measures (1252), and fixes (1266, 1332, 1364).

Operators of API nodes including Elasticsearch APIs will benefit from improvements to data availability (1351, 1352) and performance (1049, 1271, 1356).

Users of the command line interface (CLI) wallet will also benefit from improvements (1195, 1248).

Upgrade Process

Precautions

Precaution 1

Operators of API nodes that service client software that expect to receive updates about all data on the blockchain by default (such as BitShares Reference Wallet before 180401), as opposed to narrowly subscribed data, should ensure that their API nodes are configured with the enable-subscribe-to-all set to true due to Pull Request 1049.

How to Upgrade from Source Code

Obtain the Source Code

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

CLI Binaries for Linux, Windows and Mac

A binary of the command line interface (CLI) wallet for Linux is pre-built and available for download here BitShares-core-2.0.181105-Linux-cli-tools.tar.gz.

Linux SHA256 Checksum (shasum): 944771487b4ce2dddeb99c3bcba5ebde7a8f19082dbfb3bf1402b319005ea3a6

A binary of the command line interface (CLI) wallet for Windows is pre-built and available for download here BitShares-Core-2.0.181105-Windows-x64-cli-tools.zip.

Windows SHA256 Checksum: c950f0b41a23500ec897e8b9e5b12a318c5b7d2d8b1b02c286833a7f9c66d1cf

For Mac please download BitShares-Core-2.0.181105-macOS-cli-tools.tar.gz.

Mac SHA256 Checksum (shasum): 19338e77d5dc87dcbb80280edd2bac833f502f1a0b1905875165d118ba174259

Changes

The changes for BitShares Core for the 201810 Feature Release are summarized below.

Core Functionality

Description Issue Pull Request
Change call_order_update_operation to return order_id 1269 1352

Node Functionality

Description Issue Pull Request
Segmentation fault when running several witness nodes on the same machine 377 1286
Performance opt pt 1 1079 1359
Log console output during replay to file 985 1355, FC-76
Change replay percentage to total block size processed 1289 1335
Improve block generation performance - 1251
Review and backport EOS patch about unsigned_int unpacking 993 1267
Check and port Steem PR 2692: missing FC typenames 1217 1248
witness_node uses two incompatible parsers for config.ini 149 1024,1325
db_block.cpp: removed unreachable code - 1312
Cleanup budget_record_object? 1139 1213
Change object_id to more than 32 bit 1088 1267
More 32 bit to 64 bit changes 1206 1347, 1374
Remove definition of unused symbol_type - 1235
Update application.cpp - 1345
application.cpp: minor optimization - 1327
Call order and bitAsset related code refactory - 1306
Re-add enable-subscribe-notify-all option after GUI issue fixed 752 1049
When signing a block that updates the signing witness's signing key, use correct signing key 125 1203
remove unused variable _consecutive_production_enabled - 1294
Check Steem issue 2658: Not producing block because node didn't wake up within 500ms of the slot time 1157 1266
remove verify_account_history_plugin_index() - 915
inconsistent error message for update_asset_issuer 944 1255
Possible to generate a block that is too large 1136 1252
remove duplicated line in network code node.cpp - 1231
Error while converting value to string 1392 1394,FC-83
Update Sahkan's seed nodes - 1404

Node Plugins

Description Issue Pull Request
Terminate block production loop when shutting down witness plugin 1314 1332, 1364
add dascoin adaptor - 1356,1396
[ES plugin] Wrong value of additional_data.fill_data.fill_order 1295 1351
refine es_objects plugin 1271

Command Line Interface (CLI)

Description Issue Pull Request
CLI wallet: avoid directly overwriting wallet file on exit 1109 1195
cli_wallet crashes when doing import_key on Mac 1244 1248
get to_id from to_account instead of get_account_id() - 1242
wallet compatibility issue 1307 1323

Build Process

Description Issue Pull Request
Integrating cURL into cmake - 1329, 1336
cli_test doesn't compile on Windows due to using 'sys/socket.h' 1292 1305
clean old style codes - 1250

Unit Tests

Description Issue Pull Request
Not able to perform testing [100,000 transactions per second] 1298 1337
Refactor cli_test 1192 1243
Test case failed on chain_test 1326 1346

Documentation

Description Issue Pull Request
API documentation 780 1174
Launch BitShares Developer Portal 1031 How-19, Dev-41
add new doc portals to readme 953 1358,1363
add readme to plugins - 1319
LaTeX project for documentation like C++ ISO/IEC 1288 -
Probably wrong comment 1301 1349
Create plugin script - 1302
add new doc portals to readme 1363
Add disk space requirements to readme - 1376,1379
Update get_trade_history API docs and coding style - 1397

Release Contributors

@abitmore @botanegg @cogutvalera @cwyyprog Damir from Dascoin @HarukaMa @jmjatlanta @ihla @liondani @OpenLedgerDev @oxarbitrage @pmconrad @RichardWeiYang @ryanRfox @tsugimoto @zhuliting