Moonbeam halts transactions — late GLMR holders left emailing support
What happened (the TL;DR with receipts)
Moonbeam shut down its usual GLMR migration window at 23:59 UTC on July 31 as the network wound down to relaunch on Base. The official bridge mechanism worked by locking GLMR on Moonbeam and releasing the same amount from a reserve already minted on Base, sending tokens to the same user address at a 1:1 rate.
Less than four hours before the cutoff, at about 20:20 UTC on July 31, the migration contract held roughly 308.183 million GLMR. With total issuance around 1.241 billion GLMR, that put direct-bridge uptake at roughly 24.83% at that moment — meaning about 75% of the supply was still elsewhere: free balances, exchange custody, staking, treasury and other on-chain positions.
Moonbeam warned users in advance to pull funds out of liquidity pools, lending markets, staking, crowdloans, governance locks and similar places before bridging, because the bridge only handled free balances. The project also said some frozen staking and crowdloan balances that met snapshot and account-signature requirements would be honored on Base, but it didn’t promise the same for arbitrary governance locks, DeFi positions or unclaimed rewards.
At 00:00 UTC on August 1 the network entered maintenance mode and began rejecting user transactions — blocks continued to be produced during the wind-down, but user-directed transfers were effectively cut off at the deadline.
If you missed the bridge — what you can (and can’t) do
If you were one of the people who missed the scheduled migration, the official portal directed late holders to contact the helpdesk for individual review. There was no universal post-cutoff claim portal published, so recovery became a case-by-case, discretionary process with no guaranteed outcome.
Practical reality: if your GLMR was sitting as a free balance in a wallet, you were in the best position to migrate. If it was locked up in staking, a crowdloan snapshot, or on an exchange, your recovery path depended on the specific rules or the exchange’s internal process — some venues converted balances automatically at 1:1, others ran their own schedules.
If you need to try the helpdesk route, prepare a neat packet of evidence: your wallet address, transaction hashes showing the balance, any relevant snapshot info, and clear ID of the affected position. Don’t email private keys — ever. Treat helpdesk outreach like a detective case: clean, documented, and persistent.
Also watch out for scams. When migrations and deadlines happen, bright shiny phishing attempts spike. Only use official channels and double-check contact details from verified project announcements or your exchange’s support page.
Bottom line: the migration did its job for a chunk of supply, but a large portion of GLMR remained outside the direct bridge when the clock hit zero. If you’re in that group, email the support team, gather your proof, and cross your fingers — recovery is possible in some cases, but not guaranteed.
