Three Exchanges Restrict Funding After Tokens Migrate to Base
Kraken, KuCoin and Bitget have all reported funding disruptions involving GLMR and MOVR within roughly 24 hours, raising questions over whether the simultaneous restrictions are connected to the recent migration of both tokens to Base.
The exchanges have not publicly linked their respective incidents, and there is currently no evidence of a security exploit affecting GLMR, MOVR or the underlying Base network.
However, the overlap is notable because both assets recently underwent major infrastructure changes after the Moonbeam and Moonriver networks were wound down from normal user operations.
Kraken reported an incident involving Moonbeam (GLMR) and Moonriver (MOVR) funding at 11:38 UTC on Sept. 9.
The exchange said deposits and withdrawals could be delayed while it investigated the problem, although all other funding methods remained operational.
Less than three hours later, Kraken restored withdrawals for both assets. Deposits could still be delayed, and the incident remained under investigation rather than being marked resolved.
KuCoin introduced a broader restriction on Sept. 10.
The exchange temporarily suspended both deposits and withdrawals for GLMR and MOVR, saying the action was taken at the request of the project team.
KuCoin did not identify a technical problem, security vulnerability or expected restoration time.
Bitget had already restricted services for the same assets on Sept. 9.
The exchange suspended both deposits and withdrawals for MOVR on Base, while separately suspending GLMR withdrawals on Base. Bitget attributed both actions to wallet maintenance and said reopening times would be announced later.
Taken individually, temporary wallet maintenance or funding delays are routine events at cryptocurrency exchanges.
The appearance of restrictions involving exactly the same two assets across three trading platforms within a short period is less common.
An important piece of context is that GLMR and MOVR are no longer operating under the same infrastructure they used for most of their histories.
Moonbeam announced in July that GLMR would leave its Polkadot-based network and migrate to Base as an ERC-20 token. Moonriver made a corresponding move for MOVR from its Kusama-based environment.
Both migrations took place at a one-to-one ratio.
The original Moonbeam and Moonriver parachains entered maintenance mode from Aug. 1. Block production continued, but ordinary user transactions were disabled as the projects shifted their focus toward a new protocol strategy.
Major exchanges consequently had to migrate customer balances and replace their original Moonbeam and Moonriver deposit infrastructure with Base-based versions of the tokens.
Kraken handled the MOVR migration during July and subsequently migrated GLMR.
Its customer documentation said MOVR funding would be paused beginning July 21 while balances moved to Base, with GLMR funding paused from July 30. Trading remained available throughout the process.
After migration, Kraken stopped supporting the old versions of the tokens and directed deposits and withdrawals through Base.
Binance followed a similar process, discontinuing deposit and withdrawal support for the original Moonbeam and Moonriver mainnets and replacing them with Base versions.
That history makes the latest exchange incidents different from a conventional Moonbeam or Moonriver network outage.
The affected exchange services now involve ERC-20 versions of GLMR and MOVR on Base rather than transactions running directly through the original parachains.
Bitget’s notices explicitly identify its affected services as GLMR and MOVR on Base.
The timing could therefore point toward a wallet, custody, token-contract or post-migration operational issue involving the Base versions of the assets.
But there is not yet enough information to establish that explanation.
Kraken has described only a funding problem. Bitget says it is performing wallet maintenance. KuCoin says it acted at the project team’s request.
None has disclosed an exploit, loss of funds or abnormal token issuance.
The Moonbeam team has also not publicly announced a corresponding security incident explaining the exchange restrictions.
That leaves the simultaneous disruption as an operational lead rather than a confirmed network or security event.
The strongest indication that there may be a shared upstream reason comes from KuCoin’s statement that the suspension was requested by the project team.
Whether that request is related to the same issue affecting Kraken and Bitget remains unanswered.
The Recent Base Migration Changes How This Incident Should Be Read
At first glance, three exchanges restricting the same two cryptocurrencies looks like the beginning of a network outage or security incident.
The migration history makes the situation more complicated.
GLMR and MOVR effectively went through a major infrastructure reset only weeks ago.
They moved from their original parachain environments onto Base, exchanges migrated customer balances, deposit addresses changed and the old networks stopped processing ordinary user transactions.
That creates several possible points of failure without requiring an exploit.
Exchange wallets may need maintenance. Custodians may encounter problems recognizing or processing the new token contracts. Internal accounting systems may still be adjusting to the migration. A project team may also request that exchanges pause transfers while fixing a contract, liquidity or operational problem.
This is why the KuCoin wording matters.
An exchange saying it is conducting routine wallet maintenance tells us relatively little. An exchange saying it suspended deposits and withdrawals “at the request of the project team” suggests the decision was not purely an internal KuCoin maintenance event.
It still does not tell us why.
The Kraken timeline provides another useful clue.
Kraken was able to restore withdrawals within several hours while deposits remained delayed. That asymmetry may suggest the problem involved validating or crediting incoming tokens rather than an inability to move GLMR and MOVR altogether.
Again, that is an interpretation, not a confirmed cause.
There is also no reason yet to describe this as a Base outage. If Base itself were suffering a broad problem, exchanges would be expected to report disruptions across many Base-based assets rather than restrictions concentrated on GLMR and MOVR.
The fact that these two tokens moved together is therefore more interesting than the fact that they currently live on Base.
For traders, the practical risk is straightforward.
Funding availability can differ substantially between exchanges even though trading remains active. A customer may still be able to buy or sell GLMR internally while being unable to deposit tokens from a wallet or move them elsewhere.
That can temporarily fragment liquidity and prevent arbitrage between venues.
For the project, the reputational issue is larger.
A token migration is supposed to simplify the transition from old infrastructure to new infrastructure. Repeated funding disruptions several weeks later can undermine confidence that exchange integrations have stabilized, even when customer balances remain safe.
The situation needs one piece of information that none of the parties has yet supplied: the common cause, if there is one.
Until Kraken, KuCoin, Bitget or the Moonbeam team explains that connection, the safest conclusion is narrow.
Three major exchanges have experienced nearly simultaneous funding problems involving GLMR and MOVR shortly after both tokens migrated to Base.
That is enough to justify investigation.
It is not yet enough to call it a security incident.
Shane Neagle is a financial markets analyst and digital assets journalist specializing in cryptocurrencies, memecoins, prediction markets, and blockchain-based financial systems. His work focuses on market structure, incentive design, liquidity dynamics, and how speculative behavior emerges across decentralized platforms.
He closely covers emerging crypto narratives, including memecoin ecosystems, on-chain activity, and the role of prediction markets in pricing political, economic, and technological outcomes. His analysis examines how capital flows, trader psychology, and platform design interact to create rapid market cycles across Web3 environments.
Alongside digital assets, Shane follows broader fintech and online trading developments, particularly where traditional financial infrastructure intersects with blockchain technology. His research-driven approach emphasizes understanding why markets behave the way they do, rather than short-term price movements, helping readers navigate fast-evolving crypto and speculative markets with clearer context.