Main > General Discussion
New BitShares TESTNET release: test-2.0.180510
paliboy:
@clockwork are you saying that new rules are not inside condition valid after Sat, 19 May 2018 13:58:00 UTC? Witnesses are supposed to get ready and turn the new version of client only after this time?
Bangzi:
Edit: In order to avoid misunderstandings, please refer to abit's message below for instructions: https://bitsharestalk.org/index.php?topic=26426.msg318460#msg318460
clockwork:
--- Quote from: Bangzi on May 11, 2018, 04:49:30 am ---
@xeroc Please vote "bangzi-test" as active witness in testnet.
--- End quote ---
Edit: In order to avoid misunderstandings, please refer to abit's message below for instructions: https://bitsharestalk.org/index.php?topic=26426.msg318460#msg318460
Bangzi:
@xeroc Please vote "bangzi-test" as active witness in testnet.
abit:
This is a repost of https://steemit.com/bitshares/@abit/bitshares-testnet-release-test-2-0-180510
New HARD FORK release for [BitShares](https://bitshares.org/) [Open Public TestNet](https://testnet.bitshares.eu) is out, version [test-2.0.180510](https://github.com/bitshares/bitshares-core/releases/tag/test-2.0.180510).
Hard fork time is scheduled at `Sat, 19 May 2018 13:58:00 UTC`.
Testnet nodes please upgrade, ALL PEOPLE please help test.
Mainnet release will be published after test is done, estimated date is around Tue, 12 June.
## 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.
## 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)
Non-consensus changes and other info to be updated.
NOTE:
Nodes please upgrade BEFORE the scheduled hard fork time, e.g. upgrade NOW, but not upgrade after the time. If some active witnesses didn't upgrade in time, there will be unintended forking.
Testnet witnesses who have upgraded please leave a message in this thread.
Testnet witnesses who want more votes please leave a message as well.
Navigation
[0] Message Index
[*] Previous page
Go to full version