BTCBTC$64,216-0.43%|
ETHETH$1,795.06-0.45%|
USDTUSDT$0.99925-0.02%|
BNBBNB$588.0400-0.37%|
USDCUSDC$0.99962-0.01%|
XRPXRP$0.95796+0.78%|
SOLSOL$72.4700+1.61%|
TRXTRX$0.30543+0.87%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$68.8500+2.39%|
ZECZEC$927.3500+4.34%|
XMRXMR$507.4900+0.07%|
DOGEDOGE$0.05859+0.17%|
LEOLEO$9.2900+1.48%|
USDSUSDS$0.99994+0.01%|
WBTWBT$61.9900-0.66%|
LINKLINK$9.1400+0.03%|
ADAADA$0.15285+0.60%|
XLMXLM$0.13750-0.09%|
USDEUSDE$0.99935-0.02%|
DAIDAI$1.0000-0.00%|
NEARNEAR$3.2100+1.06%|
BCHBCH$208.8200+1.29%|
RAINRAIN$0.00585624-23.01%|
LTCLTC$44.5100+0.01%|
CCCC$0.08046-3.71%|
AVAXAVAX$7.1700+0.68%|
UNIUNI$5.2400+1.78%|
XAUTXAUT$3,839.69-0.20%|
SUISUI$0.72369+0.46%|
BTCBTC$64,216-0.43%|
ETHETH$1,795.06-0.45%|
USDTUSDT$0.99925-0.02%|
BNBBNB$588.0400-0.37%|
USDCUSDC$0.99962-0.01%|
XRPXRP$0.95796+0.78%|
SOLSOL$72.4700+1.61%|
TRXTRX$0.30543+0.87%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$68.8500+2.39%|
ZECZEC$927.3500+4.34%|
XMRXMR$507.4900+0.07%|
DOGEDOGE$0.05859+0.17%|
LEOLEO$9.2900+1.48%|
USDSUSDS$0.99994+0.01%|
WBTWBT$61.9900-0.66%|
LINKLINK$9.1400+0.03%|
ADAADA$0.15285+0.60%|
XLMXLM$0.13750-0.09%|
USDEUSDE$0.99935-0.02%|
DAIDAI$1.0000-0.00%|
NEARNEAR$3.2100+1.06%|
BCHBCH$208.8200+1.29%|
RAINRAIN$0.00585624-23.01%|
LTCLTC$44.5100+0.01%|
CCCC$0.08046-3.71%|
AVAXAVAX$7.1700+0.68%|
UNIUNI$5.2400+1.78%|
XAUTXAUT$3,839.69-0.20%|
SUISUI$0.72369+0.46%|
Augur
Prediction MarketTier-3On-chain prediction market protocol (no live app)

Augur

Ethereum's original prediction-market protocol, now in a fork-driven reboot under the Lituus Foundation — no live market app, and its first fork is complete.

Visit website

Key Facts

TypeOn-chain prediction market protocol (no live app)
Chain / RailEthereum mainnet — Augur v2 contracts deployed on Ethereum, with the post-fork token REPv2_Yes_1 an ERC-20 at 0xCf6A0A7826fa124B7705d6f3c675eAD76f1e540D. Augur Lituus is designed as a modular resolution layer whose results bridge to any EVM chain, and the Foundation is working on REP accessibility across more exchanges and L2s.
CollateralREP for disputes, a separate cash token for trading — the protocol glossary is explicit that REP “is not the currency used to trade market shares”. Current REP is REPv2_Yes_1 on Ethereum, the token the fork settled on.
JurisdictionEthereum mainnet, permissionless and unlicensed — no operator, no restricted-territory list and no terms of service are published. Because no market app is live and migration is closed, there is nothing to sign up to or trade today: augur.net is read-only project documentation.
Data ConfidenceVerify

Scale Signal

The fork is the only published scale figure: 6,547,546.66 of an 11,000,000 REP supply migrated in the Moon Fork — 59.52% — with 6,545,760.43 to the winning Yes universe, 1,786.23 to No, and the Invalid universe never created at all (observed 3 August 2026). No trading volume, open interest or user counts are published anywhere on augur.net. The Foundation's own disclosed treasury grew from about 250,000 REP in July 2025 to 1,000,000 REP by October 2025, with over $100,000 deployed into Uniswap V3 liquidity.

Overview

Augur is the oldest name on this list and the one that least resembles a venue. There is no application to open, no market to trade and no balance to deposit: the project's own FAQ answers “Can I use Augur today?” with “Not as a new Augur-native prediction-market application: one has not yet relaunched.” What augur.net offers is project documentation, an archived fork record and a monitor, and what the protocol offers is a resolution mechanism that spent 2026 proving itself in public.

That makes Augur a different kind of entry from the licensed exchanges and the live on-chain venues on this list. It is worth reading anyway, because almost every other venue's biggest unresolved problem — who decides what actually happened when real money is riding on the answer — is the only thing Augur has ever been about.

What Augur is today

The project is mid-reboot. The Lituus Foundation began rebuilding Augur from the ground up on 31 March 2025, and it now funds two parallel teams deliberately working different angles on the same problem: Lituus Labs, on oracle architecture, cryptoeconomic security and protocol design, and Dark Florist, on alternative oracle structures, user-facing applications and incentive models. The Foundation's stated endpoint is threefold: finalise a new oracle architecture with academic-style documentation, widen REP access across more exchanges and L2s, and relaunch an Augur-native market protocol once oracle security and fee-routing are settled.

So the honest status is neither “dormant” nor “live”. The legacy v2 protocol is deployed on Ethereum mainnet and its dispute machinery ran a real fork this year; the application layer that would let you use it is still being designed.

A protocol from Ethereum's early days

Augur ran one of Ethereum's first crowdsales in 2015 and launched on mainnet in 2018, which makes it a genuinely different artefact from everything else here: it predates the licensed event exchanges by years and the on-chain venues by a decade of tooling. Its founding position, stated in its own account of the reboot, was radical then and is still rare — “no company or committee should hold the final word on who won”, with disputed outcomes settled through an open economic process in which participants stake value on competing answers and lose it when they back the wrong one.

Stewardship has changed hands more than once since. The work is currently funded and coordinated by the Lituus Foundation, which writes the project's updates in the first person. That matters for anyone judging the token: the same organisation holds treasury REP and is the primary source for what the project is doing.

REP is a dispute token, not money

The single most misunderstood thing about Augur is the role of REP. It is the reputation token used in reporting and disputes, and the protocol glossary is explicit that it “is not the currency used to trade market shares”. Holding REP is a claim on the obligation to resolve markets correctly, not a share in trading activity, and the project treats it that way: “REP is not a passive asset and every REP holder has a duty to show up when called.”

Protocol thresholds are measured against theoretical REP, the supply basis the contracts use for percentage tests. The genesis-universe reference is 11,000,000 REP, which makes 2.5% equal to 275,000 REP — but the site is careful to say that a live deployment's own configured value is the authoritative one, not the widely quoted genesis number.

How a v2 market resolves, and when it escalates to a fork

Resolution starts quietly. After an event ends, a designated reporter has an initial reporting window; a report makes that outcome tentative. Any REP holder can then challenge it by staking REP on a different outcome. The first dispute round can run up to 24 hours, and later rounds up to seven days.

The amount required to dispute is not a fixed multiple of the last bond, which is a detail worth understanding before assuming a dispute is cheap or expensive. For dispute round n and outcome w the bond is:

B(w, n) = 2An − 3S(w, n)

where A is the total stake across all outcomes at the start of the round and S is the stake already on the proposed outcome. Bonds are crowdsourced, so several participants can fill one together, and the target is engineered to pay successful disputers about a 40% return drawn from the losing side.

Filled dispute bondWhat the protocol does next
Under 0.02% of theoretical REPThe new tentative outcome enters another dispute round immediately.
0.02% up to 2.5%The new tentative outcome waits out a window before another dispute round.
2.5% or moreThe market enters the fork state. This is the backstop.

Most disagreements never get that far. When a market finalises without a fork, stake on the incorrect outcome is forfeited: the protocol burns 20% of it and redistributes the rest to the REP staked on the final outcome.

The fork: one universe per outcome, one way

A fork is Augur's last resort, and it behaves like an election in which only people with money at risk can vote. The protocol splits into a child universe for each possible outcome of the disputed market — including Invalid — and every REP holder must migrate their tokens into the universe they believe reflects reality. A child universe is created lazily, only when migration first targets that outcome, so an outcome nobody backed may never have a contract at all.

While the fork runs, the parent universe is locked: no new markets, no new REP staking, and disputes in other unfinalised markets are put on hold, though those markets can keep trading and simply cannot finalise. Migration is one-way — a holder's choice cannot be reversed or moved to a sibling universe — and the reference mechanics allow a forking period of up to 60 days. The child that receives the most migrated REP when the period ends becomes the winning universe, and its outcome becomes the forking market's final answer. That result cannot be disputed through the ordinary process.

The Moon Fork, in numbers

All of this was theory until 2026. A community member, Micah Zoltu, raised a crowdsourcer specifically to drive a dispute over the market “Will the Artemis II Mission successfully liftoff in the first week of April?” all the way to the fork backstop, with existing REP holders contributing roughly 200,000 REP they knew would be spent, so that the mechanism could be watched end to end. The mission did launch; what was being tested was the machinery, not the answer.

Moon Fork recordValue
Escalation began8 April 2026
Escalation gameApril to early June 2026 — stakes double each round; threshold 2.5% of REP supply; roughly 40% paid to winning stakers
Migration windowEarly June to 3 August 2026, 01:00 UTC — closed permanently
Eligible supply11,000,000 REP
Total migrated6,547,546.66 REP — 59.52% of supply
To the Yes universe6,545,760.43 REP (winning universe, 0x2811…2A9f)
To the No universe1,786.23 REP
Invalid universeNever created — no REP migrated to it
Independently observedEthereum block 25,677,103, read 3 August 2026 at 21:36:23 UTC by two separate RPC providers with the same result
Current REPREPv2_Yes_1 at 0xCf6A0A7826fa124B7705d6f3c675eAD76f1e540D

What the fork was really testing

Augur's own account of the result is worth taking seriously because it is unusually unsentimental. The mechanism worked — a system that had only ever existed as a threat carried a real dispute to a settled outcome, and there was no switch anyone could pull to force the result. But the more interesting claim is about why the fork helps security at all.

Augur's argument is that a protocol's defence depends on holders actually showing up to dispute bad outcomes, and that part of any supply never does — tokens sit in lost wallets or with people who stopped watching. That REP counts toward the security budget while contributing nothing to it, so the oracle looks better defended than it is. The fork forces every holder to act or be left behind, and around 40% of supply never moved. What came through is a smaller pool, but all of it belongs to holders who showed up.

The mechanics cut the other way too: an attacker who pushes a dispute to a fork ends up holding tokens in the universe that does not reflect reality, and as honest holders migrate away from it, the economic value of the system moves with them. That is the whole design — truth enforced by capital, not by an authority.

Why the project says resolution is the weak point

The reboot's central argument is that this problem is now demonstrated rather than hypothetical, and Augur makes the case using three episodes at the largest venue, chosen precisely because volume concentrates there. In July 2025 a market on whether Ukraine's president would wear a suit, carrying over $150 million in volume, flipped from Yes to No on an oracle token-holder vote. In May 2026 a Wall Street Journal review of that venue's disputes found that in nearly one case in five, accounts helping decide an outcome were tied to bets in the market they were ruling on. In June 2026 a market worth $14 million fought over whether a sale date or a disclosure date controlled the payout, and the ruling has since been challenged in court by traders on the losing side. Different markets, same weak point.

It is fair to read all three as Augur's own framing, and it is also fair to note that Augur is not neutral about the answer: its conclusion is that a platform should not have to act as judge every time a contentious outcome lands on an edge case.

Augur Lituus: the next design

The reboot's technical output is Augur Lituus, published as a whitepaper on 29 January 2026 and now in development with ChainSafe engineering the implementation. The design separates the oracle from prediction markets entirely: a decentralised resolution layer that markets, DeFi protocols and any application can call when a real-world outcome is disputed, with results bridgeable to any EVM chain. Augur's own framing is that it is meant to sit underneath platforms rather than compete with them — an admission, in effect, that the venue and the judge should be different things.

The whitepaper's headline claim is quantitative: under its stated assumptions, forcing a fraudulent outcome through Lituus would cost about 134% of the oracle's fully diluted valuation, against roughly 92% under Augur v2's mechanism — meaning an attacker would have to buy up and destroy more than half the token supply, then buy into the replacement supply a second time. The assumptions are published alongside the result so they can be challenged. Separately, the Foundation funds Dark Florist's own line of work on a deliberately non-finalising oracle, which is best read as a parallel project rather than a component of Lituus.

Who it suits today

Nobody looking for somewhere to trade. The honest version: Augur suits researchers and protocol historians who want to study what a completed algorithmic fork actually looks like, and any REP holder who was affected by the Moon Fork and needs to establish what they now hold — which is REPv2_Yes_1 if they migrated, or a position in the parent universe expected to be worthless if they did not. For anyone comparing prediction markets to put money to work, the live on-chain venues such as Zeitgeist and the licensed exchanges are the ones with something to log into; Augur's next market app is gated on an oracle architecture that is still being engineered.

Two practical warnings come straight from the site. Migration is permanently closed and cannot be reopened or extended — nobody can migrate on your behalf, and anyone offering to migrate, recover or unlock REP is running a scam. And the post-fork token is new enough that wallets and exchanges label it inconsistently, so before acting on anything presented as REP, match the contract address: Kraken lists REPv2_Yes_1 under the ticker AUGUR, while its on-chain symbol is unchanged.

Regulatory Status

No licence, no regulator and no company running a market: Augur v2 is a deployed set of Ethereum contracts, and stewardship sits with the Lituus Foundation, which describes itself as a funder and coordinator of independent teams rather than a market operator. The project's stated position, held since 2015, is that no committee should hold the final word on who won — disputes are settled by REP holders staking against each other through escalating bond rounds until either the disagreement resolves or the protocol forks into one universe per outcome and every holder chooses a side. There is no US-regulated entity to license or sue, and no venue to supervise; the constraints are the contracts themselves, which means a closed migration window, a fungible post-fork token, and an explicit scam warning for anyone offering to recover unmigrated REP.

Features & Market Details

Augur is the only entry on this list that publishes no fee schedule at all — not because it is hiding one, but because there is nothing charging fees yet. The site says the relaunch of an Augur-native market protocol is deliberately gated on “oracle security and fee-routing mechanisms” being finalised, so the fee model for the next version is still open. What follows is what the primary sources do quantify: bonds, burns, migration totals and token identity.

What you can and cannot do on augur.net today

ActionStatus
Trade a prediction marketNot available — no Augur-native market application has relaunched
Create a marketNot available
Migrate REPPermanently closed — the window shut on 3 August 2026 at 01:00 UTC
Read protocol documentationAvailable — the Learn catalogue covers forks, disputes and migration
Inspect the fork recordAvailable — ForkWatch preserves the Moon Fork evidence at v3.augur.net

Dispute bonds and the escalation economics

Dispute bonds are the only per-action cost the protocol documents, and they are calculated rather than posted: for round n and outcome w, the bond is 2An − 3S(w, n), where A is total stake across outcomes at the round's start and S is stake on the proposed outcome. Because it depends on the market's stake distribution, there is no fixed figure to quote.

What is fixed is what happens to the money. Crowdsourced bonds can be filled by several participants, stake sits in escrow during a round, and unsuccessful dispute stake is returned when the round ends. When a market finalises without a fork, stake on the incorrect outcome is forfeited — the protocol burns 20% and redistributes the remainder to REP staked on the final outcome. The target return for a successful disputer is about 40%, and the Moon Fork's escalation game paid roughly that to the winners, which is why every bond in the sequence filled without anyone needing to be persuaded.

Migration mechanics and the one-way commitment

Migration is the part to understand before ever holding REP through a fork, and the site stresses that the commitment cannot be undone.

RuleMechanic
When it appliesOnly after a filled dispute bond reaches 2.5% of theoretical REP
Child universesOne per possible outcome, including Invalid — each created only when migration first targets it
DirectionOne-way. REP cannot move to a sibling universe afterwards
Parent universeLocked for new markets and new REP staking; other disputes paused
PeriodUp to 60 days under the reference mechanics; the deployed fork-end value is authoritative
WinnerThe child with the most migrated REP at the end; its outcome finalises the forking market and cannot be disputed
Early-win markerThe fork reputation goal is half of theoretical REP

The Moon Fork record

These are the completed event's own figures, not projections. The migration counter is the child token's dedicated getTotalMigrated() value rather than ERC-20 totalSupply, a distinction the project corrected after an early snapshot overstated migration by 147,679.02 REP.

MeasureRecorded value
Forking market0x963EED85778CC23E2D4636Cd4f29eECDF9827E9e — Artemis II launch question
Parent universe0x49244BD018Ca9fd1f06ecC07B9E9De773246e5AA
Winning outcomeIndex 1, Yes
Winning universe0x281171519Fb41540528398d8ED3EA257f0F32A9f
Current REP tokenREPv2_Yes_1 — 0xCf6A0A7826fa124B7705d6f3c675eAD76f1e540D
Fork reputation goal5,497,186.882986651334933313 REP
Migrated to Yes6,398,081.4136814946108694 REP by child counter — 6,545,760.43 in the project's aggregate total

REP identity after the fork

Four different names now refer to four different things, and the project treats getting this wrong as a safety issue rather than a labelling one. REPv1 is the original token; pre-fork REPv2 is the version that existed before April 2026; REPv2_Yes_1 is the post-fork token the project builds on; and AUGUR is Kraken's ticker for that same token. The site's own rule is to pair any token name with its chain, contract address and current-or-legacy status before acting on it. Wallets frequently do not detect the forked token automatically and have to be given the contract address manually; balances can be confirmed independently on Etherscan.

Funding, custody and access

There is no fiat rail and no custodial service of Augur's own: REP and the forked token are self-custodied ERC-20s on Ethereum, and the migration was a single on-chain transaction surrounded by four months of coordination because most of the ecosystem assumed a token could never split. Exchange handling varied and still does. Kraken, OKX and Bitpanda supported the fork and migrated customer balances themselves — Kraken lists the result as AUGUR — while other venues did not, and holders who left REP on a non-supporting exchange may have been left with a worthless version. The project's stated answer for anyone in that position is to contact the exchange, and its stated answer to anyone offering to fix it for them is that migration is closed forever and any such offer is a scam. Nobody from Augur or the Foundation will message first, and no legitimate process asks for a seed phrase or a signature to “verify” holdings.

Roadmap, and limitations worth knowing

  • There is currently nothing to trade. The honest headline: no Augur-native prediction-market application is live, and the FAQ says so in as many words.
  • Fees are not finalised. The relaunch is explicitly gated on fee-routing mechanisms being settled, so no fee schedule can be quoted for the next version.
  • The fork is a one-shot commitment. Migration was one-way and is now closed; REP left in the parent universe is expected to be worthless, and the project says there is nothing anyone can do about it.
  • The token does not appear where you expect. New token, inconsistent labels, no automatic wallet detection — verify by contract address.
  • Lituus is a design, not a product. The whitepaper's 134%-of-valuation attack cost is a modelled figure under stated assumptions, and the implementation is at the engineering stage with ChainSafe.
  • Stewardship is concentrated. The same Foundation that funds development holds a treasury position in REP and is the primary source for project updates — worth knowing when reading those updates.
  • Parts of the site are deliberately historical. The project labels old announcements, screenshots and migration instructions as dated evidence, and warns that a persistent on-chain flag can be misread as an open window. Use deployed contract values, not prose dates.

The short version: Augur is not a venue right now and does not pretend to be one. What it has is a resolution mechanism that was theory for eight years and then ran for real, and a public, evidence-backed record of what happened when it did — which is more than most platforms on this list can show for their oracle.

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.