19:I[65179,["/_next/static/chunks/16oq79q4m6et7.js","/_next/static/chunks/0__7pjky1~_cm.js","/_next/static/chunks/04~mj_5cp40sv.js","/_next/static/chunks/0rrzxh_-qnds7.js","/_next/static/chunks/11jbptme92m-w.js","/_next/static/chunks/0noioqaz1h59..js"],"default"] 1b:I[3697,["/_next/static/chunks/16oq79q4m6et7.js","/_next/static/chunks/0__7pjky1~_cm.js","/_next/static/chunks/04~mj_5cp40sv.js","/_next/static/chunks/0rrzxh_-qnds7.js","/_next/static/chunks/11jbptme92m-w.js","/_next/static/chunks/0noioqaz1h59..js"],"default"] 1a:T549,

Moonbeam's standard GLMR migration window closed at 23:59 UTC on July 31, ending the self-service route for moving tokens as the Polkadot-based network enters an operational wind-down ahead of a relaunch on Base.

The cutoff terminated the standard migration path for self-custodied free balances. Exchange holdings, frozen balances, and protocol positions were not covered by this deadline and remain subject to separate handling procedures.

Under the official migration process, GLMR was locked on Moonbeam while an equivalent amount was released on the new chain. Users who missed the window are now left without the standard automated route and must rely on direct support channels to recover funds, according to the report.

Wider Pattern of Rapid Network Wind-Downs

The source draws a comparison to a similar case involving Swell, which had warned users to bridge out by June 23, 2026, turning a planned Layer 2 shutdown into a test of user exit procedures. Such cases illustrate how quickly decentralized finance users can be left behind when crypto projects transition to new infrastructure or wind down operations.

Source: CryptoSlate

#Bridge