Augur completes its first live Moon Fork with 59.5% of REP migrated
The protocol's dispute mechanism has split an Ethereum market into outcome-specific universes, leaving a new REP contract and a public test of Augur's oracle design.
Augur's first live Moon Fork has finished on Ethereum mainnet, turning a mechanism that had existed in the protocol's design into an operating event. In an Aug. 5 announcement, the Lituus Foundation said the migration window closed on Aug. 3 at 01:00 UTC after a dispute over an Artemis II launch market. The fork created separate outcome universes and asked REP holders to move their tokens to the result they believed represented reality.
The final figures are unusually specific. Of 11 million REP in total supply, 6,547,546.66 moved during the window, equal to 59.52%. The Yes universe received 6,545,760.43 REP, while 1,786.23 REP went to No. The migration is now permanently closed: holders who did not move remain outside the post-fork universes, and both child tokens continue to exist onchain.
A resolution system under live incentives
Augur's fork is the final stage of its dispute process. Ordinary disputes escalate through rounds of staked challenges; if they remain unresolved, the protocol splits into one universe per possible outcome. REP holders choose by migrating, so the winning universe is the one that attracts the most economic weight. That design makes the oracle's security depend on participation, not only on the code that defines the procedure.
The foundation's account says the fork carried a live dispute through settlement without an administrative switch to force the result. The onchain outcome is independently visible through the new REPv2_Yes_1 contract. The experiment also exposed the cost of coordination: exchanges, wallets and data providers had to identify the new asset, while roughly 40% of total REP never migrated.
The fork is a checkpoint, not the finished redesign
The immediate result is a new token identity and a smaller set of holders who actively chose a universe. Kraken, OKX and Bitpanda supported the migration for customers, according to Augur's announcement, but the status of any REP balance still depends on the contract address and the exchange or wallet's labeling. That is a practical lesson from the fork: market infrastructure has to follow protocol state quickly when an asset splits.
Augur's next project is Lituus, a redesigned resolution layer being implemented by ChainSafe in a public GitHub repository. The repository includes Solidity contracts and unit, fuzz and invariant tests, but a working codebase is not the same as a deployed production oracle. The Moon Fork supplies the first live evidence for Augur's older mechanism; Lituus will have to earn a separate record through implementation, testing, audits and real disputes.
