Notice of REP and REPV2 Migration to AUGUR

• Following Augur’s protocol fork, REP and REPV2 migrated into a new token listed on Kraken as AUGUR.
• Kraken handled the migration on clients’ behalf. No action was required.
• The migration was 1:1 for both REP and REPV2.
• Balances were not affected.
• Funding (deposits and withdrawals) and trading were paused for REP and REPV2 during the migration.
• REP and REPV2 were delisted. Funding and trading did not reopen for them.
• AUGUR was credited by end of day July 31, 2026, with funding and trading enabled (see the EEA and Canada exception below).
• Clients in the EEA and Canada: AUGUR was credited 1:1, but only withdrawals are enabled. Trading and deposits are not open. See below for details.

Augur underwent a protocol fork, which split the network into separate universes. Kraken migrated custodial REP and REPV2 balances into the surviving (“yes” / Artemis II) universe on behalf of clients. The resulting token is listed on Kraken as AUGUR, and the migration was 1:1 for both REP and REPV2.

Clients did not need to do anything. For REP or REPV2 held on Kraken, the migration was handled for them.

Some messaging said that REP holders had to migrate their own tokens or risk losing them. That applied to REP held in personal wallets. For REP and REPV2 held on Kraken, Kraken completed the migration, so there was no need to withdraw tokens to migrate them independently.

Here is what happened at each stage:

July 24, 2026 at 14:00 UTC: Funding (deposits and withdrawals) and trading were paused for REP and REPV2.

July 27 to July 31, 2026: Migration window. REP and REPV2 were migrated to AUGUR.

By end of day July 31, 2026: AUGUR was credited, and funding and trading were enabled for AUGUR (see the EEA and Canada exception below). REP and REPV2 remain delisted.

Clients did not need to do anything to complete this migration. Kraken updated accounts automatically during the migration window.

After the migration, REP and REPV2 balances were converted to AUGUR at a 1:1 rate. REP and REPV2 were delisted and are no longer supported on Kraken. Funding and trading for REP and REPV2 did not reopen.

Clients in the European Economic Area (EEA) or Canada are subject to a restriction on AUGUR after the migration.

AUGUR does not currently have a MiCA whitepaper on file, which Kraken requires in order to list a token in the EEA. Kraken’s Canadian trades route through the same legal entity, so Canada is included in this restriction. Clients in the EEA and Canada who held REP or REPV2 were previously grandfathered in, but the migration triggered a re-review, and without a MiCA whitepaper Kraken cannot fully list AUGUR for these clients.

For clients in the EEA and Canada:

• The migration was still performed, and AUGUR was credited 1:1.
• Only withdrawals are enabled for AUGUR. Trading and deposits are not open.
• This remains the case for the time being. Kraken may open trading and deposits for these clients later if Augur files a MiCA whitepaper.

No. Kraken handled the entire migration on clients’ behalf. Balances were updated automatically.

No. The migration was 1:1 for both REP and REPV2, so the amount carried over to AUGUR.

No. Both funding (deposits and withdrawals) and trading were paused for REP and REPV2 from July 24 at 14:00 UTC.

REP and REPV2 were delisted. Funding and trading did not reopen for them.

AUGUR was credited by end of day July 31, 2026, with funding and trading enabled.

AUGUR was credited to your account 1:1, but only withdrawals are enabled. Trading and deposits are not open. This may change if Augur files a MiCA whitepaper.