Moonbeam halts user transactions after GLMR migration cutoff

Moonbeam stopped user-directed transactions when its GLMR migration window closed at 23:59 UTC on July 31. The network entered an operational wind-down and began rejecting transactions at 00:00 UTC on Aug. 1, while block production continued at node level.

The migration used a direct contract that locked GLMR on Moonbeam and released an equal amount from a reserve minted in advance on Base, sending tokens to the same user addresses at a 1:1 rate. At 20:20 UTC on July 31 the migration contract held about 308.183 million GLMR. Total issuance was roughly 1.241 billion GLMR, giving a direct-bridge uptake of about 24.83% at that snapshot. The remaining roughly 75% of supply included free holdings that were not bridged, exchange custody, staking, treasury and other on-chain positions.

Before the deadline, Moonbeam advised users to withdraw funds from liquidity pools, lending markets, staking, crowdloans, governance locks and other protocols where possible. Guidance from the project noted the bridge processed only free balances and warned that funds left deployed might become inaccessible once the network wound down.

For staking and crowdloan balances frozen at the cutoff, Moonbeam committed to honoring those positions on Base if holders met account-signature and snapshot requirements. The guidance did not extend the same explicit commitment to arbitrary governance locks, DeFi positions or unclaimed rewards.

After the standard bridge closed, the migration portal redirected late holders to email Moonbeam’s helpdesk for individual review and potential recovery. Moonbeam has not published a universal late-claim portal; individual reviews are handled case by case and there is no public guarantee that every balance will be recoverable.

Exchange-held GLMR followed each venue’s migration process rather than the direct migration contract. One exchange announced it would automatically convert GLMR balances held on its platform at 1:1, while another published its own migration and cutover schedule. Snapshot-covered locked balances and exchange-processing routes were handled outside the direct on-chain migration, so the migration contract’s uptake percentage does not measure stranded or at-risk supply.

Under the published wind-down schedule, Moonbeam entered maintenance mode at the start of Aug. 1 and began rejecting user transactions. Node-level block production persisted during the operational wind-down. The project directed users with unresolved balances to contact support for case-by-case assistance.