With the announcement, Augur v2 said that it would rename the REP token to REPv1 once a smooth migration is available. Meanwhile, a new REPv2 token will be introduced, and all users will have to migrate their REPv1 tokens to the new one.
Augur v2 has gone with the “use it or lose it” mantra, which simply means that all stakeholders will have to participate in the market fork should it occur, or risk losing their assets.
The good news is that there is plenty of time to move your assets with a 60-day grace period to migrate. Augur has already published a migration guide to help clarify any inconsistencies and offer help to stakeholders.
Forking will allow to perpetuate the main security model of Augur. However, Augur has reassured that forking is not on the cards as the thresholds of reaching a fork-triggering event is far from near being reached.
Augur has also offered help to third-parties, such as exchanges, dApps, DEXs, wallets and block explorers, as well as service providers, on how to specifically make the transition from REPv1 to REPv2 and reintegrate all services.
Augur operates as a no limit wagering platform where you can bet as much as you like on bespoke prediction markets and has seen considerable success since launching.