Moonbeam set a July deadline to leave Polkadot and move GLMR to Base

Moonbeam announced on July 3, 2026 that it would migrate its GLMR token from its Polkadot parachain to Base and wind down the existing network after a short transition. The project opened a bridge, established a July 31, 2026 deadline and said its next product would focus on communication and settlement infrastructure for autonomous AI agents.

The decision was more extensive than adding support for another blockchain. Moonbeam had been built as an Ethereum-compatible parachain using the Polkadot software stack, with its own runtime, validators, staking system and GLMR-denominated execution fees. Moving GLMR to an ERC-20 contract on Base therefore separated the token and future product strategy from the network architecture around which Moonbeam had originally developed.

What Moonbeam announced

Moonbeam’s instructions said self-custody holders could exchange one existing GLMR for one Base-based GLMR through the project’s migration portal. The announced Base contract address was `0xb3846fd356c2149ee8d30b0449088dc74e265459`.

The team told users to remove assets from liquidity pools, lending markets, staking contracts and other applications before bridging. It warned that assets remaining in those protocols could become inaccessible after the Moonbeam chain wound down. The bridge handled available GLMR balances, not every type of application position or governance lock.

For GLMR held at centralized exchanges, Moonbeam said users should await instructions from their exchange because participating venues would manage the conversion. That was a contemporaneous expectation from the project, not proof on July 3 that every exchange would support the migration.

Moonbeam said the existing network would continue operating through July 31. Its announcement described the migration as preserving holders’ stake on a 1:1 basis, but it did not provide a complete event-day accounting for tokens that might remain locked, unclaimed or otherwise unavailable when the transition period ended.

Why the Polkadot departure mattered

Moonbeam’s public codebase identified the network as an Ethereum-compatible parachain built with the Polkadot SDK. Its architecture combined Ethereum-style smart-contract execution with Polkadot-specific staking, parachain and cross-chain components. The July 3 plan consequently represented the retirement of an operating blockchain environment, not merely a branding exercise.

For developers, the practical issue was application continuity. A GLMR token on Base did not automatically reproduce Moonbeam’s existing contracts, liquidity, governance state or cross-chain integrations. Each application or service needed its own withdrawal, migration or shutdown plan. Users also faced execution risk from deadlines, bridge interactions and fraudulent links imitating the official portal.

The strategic rationale remained largely issuer-supplied. Moonbeam said it would build a decentralized protocol through which AI agents could discover one another, negotiate tasks and settle payments on-chain. On July 3, that description established the project’s intended direction, but not a completed protocol, demonstrated demand or production usage. Calling the change an AI pivot was verifiable; treating the proposed agent economy as operational would have exceeded the available evidence.

Questions left open on July 3

The announcement did not fully explain the future treatment of unmigrated balances, long governance locks, unclaimed rewards or assets left inside decentralized applications. It also did not establish how circulating supply would be reported across the legacy and Base representations of GLMR.

Those omissions mattered because a nominally 1:1 conversion does not eliminate operational differences between two networks. The defensible event-day conclusion was narrow: Moonbeam had committed to leave its Polkadot-based architecture, opened a time-limited GLMR migration to Base and attached its future identity to an AI-agent protocol that had not yet launched.

Later confirmation

Kraken stated on July 27, 2026 that it would perform the 1:1 migration for affected clients and would no longer support Polkadot-based GLMR after completing the process. That later exchange notice confirmed implementation by one venue; it does not establish what every custodian or self-custody holder experienced.