Author Topic: BitShares-Core Release 2.0.180612  (Read 366 times)

0 Members and 1 Guest are viewing this topic.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3140
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
BitShares-Core Release 2.0.180612
« on: June 13, 2018, 10:12:16 am »
This is a protocol upgrade release. All nodes should upgrade before `2018-07-19 14:00:00 UTC`.

Detailed info and binaries for download: https://github.com/bitshares/bitshares-core/releases/tag/2.0.180612

Note: in the previous release ([`2.0.180425`](https://github.com/bitshares/bitshares-core/releases/tag/2.0.180425)) we fixed a serious bug.
* If you're upgrading from `2.0.180425` to `2.0.180612`, you don't need to do anything special;
* if you're upgrading from a release earlier than `2.0.180425` to `2.0.180612`, please check [release notes of 2.0.180425](https://github.com/bitshares/bitshares-core/releases/tag/2.0.180425) to see if you need to perform additional steps.

## Consensus changes

* [BSIP26: Refund Order Creation Fee in Originally Paid Asset when order is cancelled](https://github.com/bitshares/bsips/blob/master/bsip-0026.md)
* [BSIP27: Asset Issuer Reclaim Fee Pool Funds](https://github.com/bitshares/bsips/blob/master/bsip-0027.md)
* [BSIP29: Require owner authority to change asset issuer](https://github.com/bitshares/bsips/blob/master/bsip-0029.md)
* [BSIP30: Always Allow Increasing Collateral Ratio If Debt Not Increased](https://github.com/bitshares/bsips/blob/master/bsip-0030.md)
* [BSIP31: Update Short Position's Margin Call Price After Partially Called Or Settled](https://github.com/bitshares/bsips/blob/master/bsip-0031.md)
* [BSIP32: Always Match Orders At Maker Price](https://github.com/bitshares/bsips/blob/master/bsip-0032.md)
* [BSIP33: Maker Orders With Better Prices Take Precedence](https://github.com/bitshares/bsips/blob/master/bsip-0033.md)
* [BSIP34: Always Trigger Margin Call When Call Price Above Or At Price Feed](https://github.com/bitshares/bsips/blob/master/bsip-0034.md)
* [BSIP35: Mitigate Rounding Issue On Order Matching](https://github.com/bitshares/bsips/blob/master/bsip-0035.md)
* [BSIP36: Remove expired price feeds on maintenance interval](https://github.com/bitshares/bsips/blob/master/bsip-0036.md)
* [BSIP37: Allow new asset name to end with a number](https://github.com/bitshares/bsips/blob/master/bsip-0037.md)
* [BSIP38: Add target collateral ratio option to short positions](https://github.com/bitshares/bsips/blob/master/bsip-0038.md)
* [Bugfix #184: Potential something-for-nothing fill bug](https://github.com/bitshares/bitshares-core/issues/184)
* [Bugfix #214: Proposal cannot contain proposal_update_operation](https://github.com/bitshares/bitshares-core/issues/214)
* [Bugfix #453: Multiple limit order and call order matching issue](https://github.com/bitshares/bitshares-core/issues/453)
* [Bugfix #588: Virtual operations should be excluded from transactions](https://github.com/bitshares/bitshares-core/issues/588)
* [Bugfix #868: Clear price feed data after updated a bitAsset's backing asset ID](https://github.com/bitshares/bitshares-core/issues/868)
* [Bugfix #890: Update median feeds after feed_lifetime_sec changed](https://github.com/bitshares/bitshares-core/issues/890)
* [Bugfix #922 / #931 / #970] Fixed missing checks when updating a smart coin's `bitasset` options E.G. force settlement delay, backing asset ID or etc;
* [Bugfix #942] Fixed missing asset authorities check for "from" account when claiming from a withdraw permission.

## API changes

* `extensions` field of `call_order_update_operation` changed from an array to an object, which affects all related API's E.G. `get_block`, `get_account_history`, `get_relative_account_history` and etc. Due to this, old version of `cli_wallet` won't be compatible with new API nodes when that operation would occur in result.
* [Issue #862, PR #872] Improved pagination of `list_assets` node API
* [Issue #863, PR #871] Node `get_ticker` API now returns time stamp of latest block instead of server time
* [Issue #811, PR #861] Added `get_full_account` command/API to `cli_wallet`


## Other changes

* [[FC PR #36](https://github.com/bitshares/bitshares-fc/pull/36)] Support Boost 1.64-1.65

* [[FC PR #43](https://github.com/bitshares/bitshares-fc/pull/43)] Fixed a memory leak issue in TCP socket destruction

* [[FC PR #44](https://github.com/bitshares/bitshares-fc/pull/44)] Fixed Diffie-Hellman shared key computation (related to memo encryption)

* [Issue #727, PR #880] Added stack trace printing when node crashes (only for boost 1.65)

* [Issue #878, PR #927] Made number of I/O threads configurable (can be manual or auto)

* [Issue #805, PR #840 / #919 / #937] Improved logging level and messages; added logging options about log-rotation

* [Issue #837, PR #848 / #839] Added cli_wallet to Docker

* [PR #938] Fixed an issue that may cause the node to store incorrect block ID to disk when switching forks

* [Issue #582, PR #813] Fixed macOS witness node crash issue when being used as an API server

* [Issue #776, PR #816 / #955] Fixed missing notification to RPC clients when changes occurred on some types of objects

* [Issue #888, PR #954] Fixed an integer overflow issue when checking whether a price feed has expired

* [Issue #864, PR #865] Fixed a `cli_wallet` transaction signing issue when creating proposals with transaction builder

* [Issue #859, PR #801 / #817] Fixed macOS and Ninja build errors introduced in last release

* [Issue #136, PR #928] Fixed an asset supply calculation error in test case

* [Issue #943, PR #869 / #945] Improved a few assertion error messages

* [PR #850] Removed unused asset cache from `cli_wallet`

* [PR #918] Fixed in-code documentation for `set_desired_witness_and_committee_member_count` command/API in `cli_wallet`

* [PR #804] Refactored `node.cpp` and `application.cpp` for easier testing

* [PR #851 / #853 / #854 / #855] Fixed several compiler warnings

## Contributors

* [@abitmore](https://github.com/abitmore)
* [@jmjatlanta](https://github.com/jmjatlanta)
* [@oxarbitrage](https://github.com/oxarbitrage)
* [@pmconrad](https://github.com/pmconrad)
* [@xeroc](https://github.com/xeroc)
* [@cifer-lee](https://github.com/cifer-lee)
* [@ihla](https://github.com/ihla)
* [@zhuliting](https://github.com/zhuliting)
* [@Zapata](https://github.com/Zapata)

BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline armin

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: BitShares-Core Release 2.0.180612
« Reply #1 on: June 13, 2018, 12:01:50 pm »
I saw many same BSIPS implemented in older release: https://bitsharestalk.org/index.php?topic=26427.0

Is this replacing that release?

Offline pc

  • Hero Member
  • *****
  • Posts: 1365
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Re: BitShares-Core Release 2.0.180612
« Reply #2 on: June 13, 2018, 04:08:22 pm »
The "older release" was for testnet, this one contains (mostly) the same set of changes but is for mainnet.
Please vote for my BitShares witness "cyrano" and for my STEEM witness "cyrano.witness"!
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline armin

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: BitShares-Core Release 2.0.180612
« Reply #3 on: June 13, 2018, 04:25:27 pm »
Hmm that's interesting, why did you guys choose to apply a different release to the mainnet?

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3140
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: BitShares-Core Release 2.0.180612
« Reply #4 on: June 13, 2018, 10:17:33 pm »
Hmm that's interesting, why did you guys choose to apply a different release to the mainnet?
Because mainnet and testnet are different.

Please read https://github.com/bitshares/bitshares-core/wiki/Git-Flow for details.
« Last Edit: June 13, 2018, 10:19:05 pm by abit »
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline armin

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: BitShares-Core Release 2.0.180612
« Reply #5 on: June 14, 2018, 04:09:52 am »
Is it because some of the fixes are not applicable to the testnet?

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3140
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: BitShares-Core Release 2.0.180612
« Reply #6 on: June 14, 2018, 02:45:02 pm »
Is it because some of the fixes are not applicable to the testnet?
Code is almost the same except hard fork dates.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline EasyDex

Re: BitShares-Core Release 2.0.180612
« Reply #7 on: June 16, 2018, 05:05:10 am »
Is it because some of the fixes are not applicable to the testnet?
With some of the changes like the ones in this release some of which are pretty major you want to run them on testnet for a little bit to make sure no strange bugs pop up that you didn't foresee. That being said, I'm really excited about this release. This will make some of the features we have planned MUCH easier to implement and will help us bring lots of exciting features to the Bitshares ecosystem.
Check us out at www.easydex.net!