Don’t invest unless you’re prepared to lose all the money you invest. This is a high-risk investment and you should not expect to be protected if something goes wrong. Take 2 minutes to learn more.

Notice of War (WAR) Migration

Last updated: 19 October 2026

The WAR token underwent a protocol migration. Kraken managed this process on behalf of all affected clients, so clients did not need to take any action. Once migration was complete, WAR balances automatically reflected the new token, and the ticker symbol stayed the same.

This article explained how the migration worked, how the new WAR allocation was calculated, and what clients could expect at each stage of the timeline.

  • Kraken handled the WAR token migration on clients’ behalf; no action was required.

  • Clients who held WAR at the protocol snapshot on March 10, 2026 received 90% of their eligible allocation, reflecting the standard on-chain migration terms.

  • Clients holding WAR at the time trading was paused on April 10 received a proportional share of the remaining 10% allocation as an additional distribution.

  • Trading and withdrawals for legacy WAR were paused on April 10 at 14:00 UTC; full trading was expected to resume the week following April 17.

  • The WAR ticker remained the same; once migration was complete, account balances automatically reflected the new WAR token.

  • Legacy WAR was delisted after migration; no further action or manual token swap was needed.

The WAR protocol set a snapshot date of March 10, 2026 at 20:11:49 UTC to determine eligibility for the migration. Kraken used two separate balance snapshots to calculate client allocations fairly.

90% of Kraken’s total WAR allocation was distributed among all clients who held WAR at the time of the March 10 snapshot (in proportion to their balance). This matched the standard on-chain migration setup: anyone who migrated directly on-chain after March 10 also received 90% of their holdings due to a 10% protocol fee, so these clients were treated exactly as they would have been had they migrated themselves.

The remaining 10% was distributed proportionally among clients who held WAR at the time trading was paused on April 10. Kraken distributed this portion voluntarily to ensure that clients with balances at that time were not left out entirely.

Here is what happened at each stage of the migration process:

March 10, 2026 at 20:11:49 UTC: Snapshot 1. This snapshot was implemented by the WAR team for the migration, and was not set by Kraken.

April 10, 14:00 UTC: Snapshot 2. Trading and withdrawals for the legacy WAR token were paused. Kraken took a real-time snapshot of WAR balances at that moment.

Week of April 13: All open WAR orders were canceled. No specific time was confirmed for this step.

April 13–April 17, 23:59 UTC: Migration period. Client WAR balances were adjusted to reflect new WAR token holdings. No action was required from clients during this time.

April 17: The WAR market moved to post-only mode while liquidity was established.

Following week: Full trading resumed.

Clients did not need to do anything to receive their new WAR tokens. Kraken handled the migration and updated accounts automatically during the migration period between April 13 and April 17.

The WAR ticker symbol remained unchanged, so once migration was complete, clients saw their updated WAR balance in their accounts as normal. The balance reflected the new migrated token; legacy WAR was delisted and was no longer supported on Kraken after migration concluded.

As part of this migration, WAR moved to a new smart contract. For reference, the contract addresses for both the legacy and new tokens are listed below.

Legacy WAR contract address:

8opvqaWysX1oYbXuTL8PHaoaTiXD69VFYAX4smPebonk

New WAR contract address:

C9dJfTGUzhuqPWxh9mcDr66JZN4uzXh2gh9EWnEdpump

After migration, any WAR held in a Kraken account was the new token. Legacy WAR was no longer supported, and no manual token swap was required.

Did I need to do anything to receive my new WAR tokens?

No. Kraken handled the entire migration process. Account balances were updated automatically.

Why was the allocation split 90/10?

The WAR protocol applied a 10% fee to all on-chain migrations that occurred after the March 10 snapshot. Kraken’s 90% distribution to snapshot-eligible clients reflected this mechanic. The additional 10% distributed to holders at the time trading was paused was a voluntary step Kraken took to ensure no client was excluded entirely.

Could I trade or withdraw WAR during the migration period?

Trading and withdrawals for legacy WAR were paused from April 10 at 14:00 UTC. Full trading was expected to resume the week after April 17.

Did my WAR balance look different after migration?

Balances reflected the new WAR allocation once the migration period concluded. The ticker symbol remained WAR.

How would I know when trading began? (After the migration)

Clients were notified by email, and this article was updated once trading resumed.