BitShares Forum
Main => General Discussion => Topic started by: abit on May 10, 2018, 11:11:33 pm
-
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.
-
(https://i.imgur.com/5lK6Pcz.jpg)
@xeroc Please vote "bangzi-test" as active witness in testnet.
-
(https://i.imgur.com/5lK6Pcz.jpg)
@xeroc Please vote "bangzi-test" as active witness in testnet.
Edit: In order to avoid misunderstandings, please refer to abit's message below for instructions: https://bitsharestalk.org/index.php?topic=26426.msg318460#msg318460
-
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 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?
-
@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?
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 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?
Good point. They should be..
My bad...that's what i get for posting early in the am. :( Apologies @bangzi
That incorrect info .. please edit it.
Nodes please upgrade BEFORE the scheduled hard fork time, e.g. upgrade NOW, but not upgrade after the time. If some nodes didn't upgrade, there will be forking.
-
(https://i.imgur.com/5lK6Pcz.jpg)
@xeroc Please vote "bangzi-test" as active witness in testnet.
Voted. Are you running test-2.0.180510 for block production now? If not, please do it.
By the way, anyone who want to be voted please leave a message.
-
(https://i.imgur.com/5lK6Pcz.jpg)
@xeroc Please vote "bangzi-test" as active witness in testnet.
Voted. Are you running test-2.0.180510 for block production now? If not, please do it.
By the way, anyone who want to be voted please leave a message.
Done. Switch back to 20180510.
-
By the way, anyone who want to be voted please leave a message.
My test witness "witness.zapata" has been upgraded sucessfully to "test-2.0.180510" using Docker image.
I run also a test API node with the same version: testnet.dex.trading
Can you vote me in?
-
By the way, anyone who want to be voted please leave a message.
My test witness "witness.zapata" has been upgraded sucessfully to "test-2.0.180510" using Docker image.
I run also a test API node with the same version: testnet.dex.trading
Can you vote me in?
Voted.
-
As of writing, there are 25 active witnesses in testnet is ready for the hard fork:
abit-test, blckchnd-testnet, clockwork.witness-1, sahkan-bts-testnet, sc-bitshares-testnet, zhaomu-test, witness.zapata, bangzi-test, crazybit.witness, xeldal-test, roelandp, witness-still, witness.yao.test, thom-witness, freedom-t, sampson-test, test-hiblockchain, migicwallet-witness,fox-20180510,delegate.ihashfury,lafona-testnet,oxarbitrage-test,initX,gdex-witness,necklace-w,bhuz-testnet,rngl4b
Their witness account in mainnet are:
in.abit, blckchnd, clockwork, sahkan-bitshares, sc-ol, delegate-zhaomu, ?, bangzi, crazybit, xeldal, roelandp, witness.still, witness.yao, verbaltech2, delegate.freedom, winex.witness, witness.hiblockchain, magicwallet.witness, fox, delegate.ihashfury, delegate-1.lafona, ?, ?, gdex-witness, xn-delegate,bhuz,rnglab
Among them,
* sc-ol, bangzi have witness accounts in mainnet, but are not active (didn't get voted in);
* witness.zapata, initX(xeroc), oxarbitrage-test(oxarbitrage) don't have an witness account in mainnet.
These active mainnet witnesses don't have an active witness in testnet:
bhuz, rnglab, abc123, xman, openledger-dc, elmato, mr.agsexplorer
Update: bhuz updated.
Update: rnglab had updated earlier
-
Did the testnet hard-forked successfully?
-
Did the testnet hard-forked successfully?
Yes. And testing is still going on.
-
Edit: In order to avoid misunderstandings, please refer to abit's message below for instructions: https://bitsharestalk.org/index.php?topic=26426.msg318460#msg318460