MultiversX Gives Itself 12 Hours to Explain Potential Mainnet Issue
MultiversX is investigating an unspecified issue on its mainnet after at least one major exchange independently reported delays moving EGLD on the network, adding an operational signal to what initially appeared to be an unusually cautious security notice.
The blockchain project said at approximately 10:00 UTC on Sept. 19 that it had detected a “potential issue” on the MultiversX mainnet and had begun investigating.
MultiversX said protecting users and ensuring the safe and reliable progression of the network were its highest priorities. It promised another update within 12 hours or sooner if the team reached a clear conclusion.
The initial statement was deliberately narrow.
MultiversX did not describe the issue as an exploit, consensus failure or outage. It reported no stolen funds, affected wallets or financial loss and did not instruct users to stop transacting, unstake EGLD or move assets away from the network.
However, Coinbase separately acknowledged an EGLD network problem shortly before the MultiversX announcement.
At 02:00 PDT on Sept. 19, equivalent to 09:00 UTC, Coinbase said customers could experience delayed sends and receives on MultiversX “due to a network issue.” The exchange said buying, selling and fiat deposits and withdrawals remained unaffected and told customers their funds were safe.
The timing does not establish what caused the MultiversX investigation, but the Coinbase notice provides independent evidence that at least some network-dependent activity was experiencing disruption around the same period.
MultiversX’s own status dashboard also showed partially degraded service at the latest check. Its Public API, xPortal, Explorer, Wallet, Bridge, xExchange and xLaunchpad were displaying degraded performance, while the network Gateway and Index were listed as operational.
That distinction matters. A blockchain can continue producing and finalizing blocks while applications, APIs, explorers or infrastructure sitting around the chain experience problems.
Recent crypto infrastructure incidents have similarly demonstrated how multiple consumer services can fail together even when the underlying trading or settlement system remains partly operational.
There is not yet enough evidence to determine whether MultiversX is dealing with that type of infrastructure degradation or something deeper inside the protocol.
Kraken Had Already Reported EGLD Funding Problems Before the Alert
There is another piece of the timeline that deserves attention.
Kraken had already been reporting problems with its MultiversX funding gateway beginning Sept. 16. The exchange said EGLD deposits and withdrawals could be delayed while other funding methods remained operational.
Because Kraken’s problem began roughly three days before MultiversX publicly disclosed the potential mainnet issue, the two events should not automatically be treated as the same incident.
Kraken also experienced a separate EGLD funding interruption around MultiversX’s Sept. 10 network upgrade that was resolved later that day.
Still, continued exchange-level funding friction is relevant when trying to establish the practical impact of a network investigation.
Exchange deposit and withdrawal systems depend on nodes, wallet infrastructure, transaction indexing and finality signals from the underlying blockchain. Problems in any of those layers can appear to exchange customers as delayed funding even when internal trading remains available.
That is why network-level incidents can propagate outward. The Liquid Network security incident, for example, ultimately forced exchanges supporting L-BTC to suspend network activity even though Bitcoin itself was not compromised.
Similarly, the recent Symbiosis bridge exploit required the project to isolate one component while keeping unrelated routes operational.
The MultiversX case has not been classified as an exploit and there is currently no evidence of comparable losses. Those incidents are useful only as examples of why identifying the affected technical layer matters before describing the severity of a blockchain problem.
Supernova Went Live Sept. 10, Not Sept. 15
The timing is particularly sensitive because MultiversX recently completed the largest protocol upgrade in its history.
Supernova activated on mainnet on Sept. 10. A Sept. 15 MultiversX ecosystem update referred back to the upgrade as already live rather than marking its activation date.
Supernova fundamentally changes how MultiversX processes blocks. The upgrade reduces block time from six seconds to approximately 600 milliseconds and decouples consensus from transaction execution, allowing the network to agree on blocks before execution proceeds asynchronously.
MultiversX designed the change to deliver sub-second finality while preserving its sharded architecture and existing validator hardware requirements.
Because the architecture changed so recently, any unexplained mainnet investigation will naturally raise questions about whether the two developments are connected.
There is currently no evidence that they are.
MultiversX has not mentioned Supernova in its Sept. 19 warning, identified a consensus or execution problem, or said that the network upgrade introduced the issue.
That distinction needs to remain explicit unless the project’s technical follow-up says otherwise.
Large protocol upgrades routinely produce operational adjustments across exchanges, wallets and infrastructure providers without indicating that the upgraded consensus mechanism itself is broken. The important question is which layer MultiversX eventually identifies.
The 12-Hour Update Matters More Than the Initial Alert
For now, the most interesting part of this story is how little MultiversX has said while still deciding the issue was serious enough to announce publicly.
Blockchain teams discover bugs constantly.
Most never produce a public warning.
When a project tells users that it has detected a potential mainnet issue, emphasizes user protection and puts a 12-hour deadline on its next communication, that suggests engineers saw something requiring active investigation but were not yet confident enough to classify it publicly.
That caution is sensible.
Calling something an exploit too early can create panic. Calling it harmless before understanding the root cause can be worse.
The next update should make the situation much easier to categorize.
If MultiversX confirms that validators continued producing blocks correctly, shards remained synchronized and finality was intact, the investigation may ultimately resolve into an application, API, indexing or infrastructure problem.
That would fit more closely with the degraded consumer-facing services currently visible on its status page.
If the team instead identifies abnormal state changes, inconsistent execution results, validator disagreement or finality problems, the implications become considerably more serious because those sit much closer to the guarantees the blockchain itself is supposed to provide.
The recent history of third-party infrastructure failures is a useful reminder that a security incident surrounding a crypto product does not automatically mean the underlying blockchain was compromised.
At the same time, recent bridge failures show the opposite problem: systems can appear to function normally until downstream infrastructure accepts state that should never have been considered valid.
That is why the technical post-mortem matters more than whether EGLD moved 5% or 10% during the investigation.
What to Watch Before MultiversX Explains the Root Cause
There are several observable signals that can help narrow the problem before the formal explanation arrives.
Block production is the first.
If MultiversX continues producing 600-millisecond blocks without abnormal missed-round rates, shard divergence or unusual finality delays, that would weigh against a broad consensus outage.
The second is exchange funding.
Coinbase’s delayed sends and receives provide a confirmed external symptom. If Binance, Bybit or additional major exchanges begin suspending EGLD deposits and withdrawals, that would suggest infrastructure operators are independently seeing enough uncertainty to stop accepting network transfers.
The third is the MultiversX Bridge.
Bridge systems deserve particular scrutiny during network incidents because they depend on one environment correctly recognizing what happened in another. Recent failures in cross-chain infrastructure have demonstrated how damaging an incorrect state assumption can become once genuine liquidity is released against it.
The fourth is the wallet and application layer.
MultiversX currently lists xPortal, Wallet, Explorer and several applications as degraded. If those recover while the core Gateway and Index remain operational, the eventual explanation may turn out to involve services around the blockchain rather than the blockchain’s consensus itself.
Modern networks increasingly depend on layers of wallet infrastructure, APIs, indexers and application services that users rarely see until something breaks.
That is what makes MultiversX’s carefully worded alert interesting.
There is enough evidence to say something is happening: MultiversX itself opened a mainnet investigation, Coinbase independently reported network-related EGLD transfer delays and several MultiversX services are showing degraded performance.
There is not enough evidence to say what caused it.
And the temptation to blame Supernova simply because the major upgrade activated nine days earlier should be resisted unless the technical evidence points there.
For investors and users, the next MultiversX statement is therefore the real event.
If the team closes the investigation without losses and demonstrates that consensus, execution and account state remained correct, the incident may prove to be a contained infrastructure problem during the stabilization period after a major upgrade.
If it identifies a protocol-level flaw, the conversation changes immediately.
Either way, MultiversX has created a useful benchmark for itself: it publicly promised more information within 12 hours. What it says in that update — and how precisely it explains the affected layer — will tell users far more than the initial warning did.
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.