Augur announced that v1 version stop time, v2 transition is subject to bifurcation and migration risk

Augur v1 will be discontinued on September 15, 2019 to facilitate the transition to Augur v2. The holder of its token REP is not directly affected by this, but traders, order creators, and participants on the platform may be at risk of resolving errors or bifurcating after the stop date.

As explained by Augur, the Augur v2 release is the first major upgrade to the Augur protocol, the Augur v2 contract code has been completed, is now under review, and will be released later this year. After v2 is deployed, Augur v1 will remain on the main Ethernet network because it cannot be shut down or changed. Augur v1 and Augur v2 will exist independently of each other, each with a separate REP version.

Augur  The market order of v1 will expire on September 15, and the market order that expires before the deadline will not be affected. If the v2 version has not been released after the deadline, the predicted market order may not be able to solve the problem, and there is a higher risk of solving errors or bifurcation. According to DappRadar, there are currently 154 active users of Augur 7 days and 560 ETH of transactions.

Once v2 is launched, REP holders will be strongly encouraged to move their REP to v2, as it is expected to become a more practical and popular platform in the long run, and the Augur team will no longer actively develop v1. Therefore, the v1 market solved after the launch of v2 may have the minimum value. But oracle on v1 can also be cheaper by reporting error results and possibly triggering forks, and if there is a market fork after the deadline, then participants who stay on v1 will no longer be able to migrate their REP to v2.

Due to the high risk of market processing errors after the deadline, Augur advises traders not to enter positions in markets that expire after the deadline. If you are already open in any of these markets, consider liquidating; Cancel any outstanding orders in these markets.

Augur recommends that issuers do not create market orders that expire after the deadline. If a market has been created that expires after the deadline, the margin may not be effectively recovered.

Augur advises participants not to participate in markets that expire after the cut-off because if a fork occurs, all participants left in v1 will lose the ability to migrate their REP to v2.

Augur hopes that the v2 release will greatly improve the availability, security and reliability of Augur, but the v1 transition may not be as smooth as we would like, steps have been taken to ensure that future version changes run more smoothly, and the Augur v2 contract has been modified to make downtime clear and easy to understand. The community is currently discussing options to improve v3 with the goal of reducing or eliminating downtime.

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia