Layer 1 blockchain
MultiversX ticker EGLD
Summary
Secure Proof of Stake over a sharded ledger. Mainnet runs three execution shards and a metachain, each with 400 eligible validators (1,600 in total); every validator node is backed by at least 2,500 EGLD, and part of each shard's set is reshuffled at the 24-hour epoch boundary. Since Andromeda (May 2025) all 400 validators of a shard sign each block, and a block is final once more than 2/3 of their BLS signatures are aggregated into a consensus proof. The metachain notarizes shard block headers so other shards can act on cross-shard output. Supernova, activated on mainnet on 10 September 2026, cut rounds from 6 seconds to 0.6 seconds and has validators vote on a block before executing it, with execution results recorded in later headers. 1245691016
Design
- System
- Layer 1 blockchainPermissionless proof-of-stake base layer that settles its own transactions. Its ledger is split into three execution shards plus a coordinating metachain, each producing its own blocks in lock-step rounds, so block-level metrics describe one shard rather than the whole network.
- Settlement family
- Its own design
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Other
- Who makes blocks
- In each shard and in the metachain, the proposer for a round is the validator whose hash of its public key and the round's randomness is lowest; the randomness chains from the previous proposer's signature. Nodes join by staking 2,500 EGLD each and, since Staking v4, enter an auction ranked by stake above that minimum.
- Fork choice
- No longest-chain or heaviest-chain rule. A block is final once a proof aggregating signatures from more than 2/3 of the shard's validators exists, and the documentation says only one valid proof can exist per block. Failures are resolved by coordinated software releases: after transactions stopped on 19 September 2026, the mainnet configuration restarted the network from a recovery checkpoint and excluded the rounds that followed it. The restarted network stalled again within about 20 minutes, and a further release excluded a second window before normal processing resumed on 24 September.
Qualifications
- Block time · Partial. Each execution shard and the metachain produce their own blocks in shared rounds of 0.6 seconds since 10 September 2026 (6 seconds before). Rounds can pass without a block, and a block-interval figure describes one shard, not the network.
- Finality · Applies. Deterministic committee finality: a block is final once more than 2/3 of its shard's 400 validators have signed, with no confirmation-depth rule. It is not classed as economic finality because the docs describe stake slashing for serious offences while noting double-signing enforcement as still to come, and routine faults are handled by rating and jailing. The September 2026 recovery also shows that a coordinated restart can replace recorded blocks.
- Adaptive sharding · Partial. The protocol can split or merge shards, but MultiversX's glossary says mainnet has run three execution shards since 2020 without triggering resharding, and the live network configuration reports adaptivity switched off.
- Cross shard atomicity · Partial. A transfer or contract call between shards executes in sequence across several blocks; a later step that fails does not automatically reverse earlier ones unless the contract handles it.
- Tps · Contested. MultiversX's own pages give several different throughput figures for mainnet, for future shard counts and for a test network. They appear only as classified claims, and no observed mainnet window was recorded.
- Settlement family · Partial. Recorded as other: MultiversX runs its own Secure Proof of Stake over a sharded ledger of execution shards and a metachain, with WebAssembly smart contracts on its own virtual machine (SpaceVM).
Tradeoffs
- Emphasizes
- Scalability and Decentralization Contested
- Gives up
- Per-shard security margin, atomic cross-shard composability and liveness margin. Each shard's safety rests on the 400 validators assigned to it for the epoch rather than on all stake; contract calls that cross shards run asynchronously and can leave partial outcomes; following the whole ledger needs one node per shard; and mainnet processed almost no user transactions for more than five days (19 to 24 September 2026), starting nine days after Supernova cut round time tenfold.Decentralization here means a large number of validator keys (1,600 eligible) on modest per-node hardware. By stake the picture is more concentrated: MultiversX's staking documentation says the top 11 staking agencies control 33%, and the public API grouping on 27 September 2026 showed the 11 largest identities holding just over one third of stake, the largest being the MultiversX identity at about 11.5%. MultiversX presents security as a primary goal, so some readers would list security instead of decentralization.
- Full node at home
- Demanding 1314One node follows one shard: MultiversX lists 4 dedicated CPU cores, 8 GB RAM, a 200 GB SSD and an always-on 100 Mbit/s link with a 4 TB monthly data allowance per node. Following the whole network needs an observing squad of four observers plus a proxy, for which the docs recommend 16 CPUs, 32 GB RAM and disk that can grow to 5 TB. Both pages were last updated before Supernova made rounds ten times shorter, and ARM processors cannot sync from genesis.
- Throughput claims
- Theoretical peak: 30,000 tx/s 15Theoretical peak; not comparable across chains or with observed load.Stated as a mainnet achievement on MultiversX's 'What is MultiversX?' documentation page (last updated February 2026); no date, window or method given.Not stated.No method, measurement window or transaction mix is given, so it cannot be treated as an observed mainnet rate. The same page says capacity scales further as shards are added; mainnet has run three execution shards since 2020 and shard splitting has not been triggered in production. Predates Supernova's round-time change and ignores state growth, cross-shard latency and propagation to full nodes; not comparable with another chain's figure.
- Lab benchmark: 120,000 tx/s 3Controlled benchmark; not observed network behavior.Final day of the Battle of Nodes public adversarial test network, 11 to 31 March 2026, as reported in MultiversX's documentation glossary.Community-run validators on a test network; hardware not stated.A test-network event run before Supernova reached mainnet, not observed mainnet load. Shard count, transaction mix and how long the rate was sustained are not stated; reported by MultiversX and not independently measured in this review. Ignores state growth and propagation to full nodes; not comparable with another chain's figure.
Scaling layers
- MultiversX Sovereign Chains · Sidechain, status unknown 326
App-specific chains built with MultiversX's software, each with its own validators, consensus and fee rules, linked to mainnet by bridge contracts that accept outgoing transfers signed by at least 67% of the sovereign chain's validator keys. Bridge security rests on those validators, not on MultiversX's consensus (the glossary also describes EGLD restaking to back them), and no validity or fraud proof is described. The docs are marked incomplete, several pages are placeholders, and no production sovereign chain on mainnet was verified.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | Not yet assessed under the current definitions; no protocol-level swap using hash or time locks was found. Contract calls between shards are asynchronous rather than atomic, so same-shard escrow contracts are the nearest pattern; none was reviewed as a maintained product. 3 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | Not yet assessed under the current definitions; no maintained light client was found. The documented read path is an observer node per shard behind a proxy, or a public API, which means trusting that server rather than light verification. 14 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel network anchored to MultiversX was found. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | WebAssembly smart contracts, written mainly in Rust, can hold and move funds; accounts can require a guardian co-signature; and relayed transactions let a second account pay the fee. Multisig wallets are contracts rather than a protocol account type. 192122 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; guardians are a protocol feature: a guarded account needs a guardian co-signature for every transaction, and replacing the guardian without its signature takes 20 epochs, which MultiversX describes as time for the owner to react if a key is stolen. A key that must co-sign is not a recovery path under this row (§1), and confirmed payments cannot be reversed. 1920 |
| Rollups | Unknown | The earlier note said absence was not exhaustively verified, so under the rule that absence needs a source this is unknown rather than not present. Earlier finding: no rollup settling to MultiversX was found; MultiversX scales through its own shards, and the sovereign-chain documentation page titled for an Ethereum layer 2 is an empty placeholder. 326 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | Established in the ecosystemxExchange (constant-product AMM), AshSwap (stable-swap AMM) | xExchange documents an x*y=k automated market maker with a 0.3% swap fee; AshSwap describes a stable-swap AMM and aggregator on MultiversX. Liquidity depth was not assessed. 272829 |
| Issuer-native stablecoins | ThinUSH (Hatom, over-collateralized) | Circle's USDC list and Tether's protocol list do not include MultiversX; USDC and USDT on MultiversX are tokens whose metadata says they are bridged from Ethereum. The only MultiversX-native dollar token found is Hatom's USH, which its metadata calls over-collateralized; its collateral and issuer controls were not reviewed. 3031323334 |
| Algorithmic stablecoins | Unknown | No algorithmic stablecoin with material usage was verified. USH is described as over-collateralized, not algorithmic. 32 |
| Bridges | First-partyMultiversX Ad-Astra Bridge (Ethereum, BNB Smart Chain), Axelar (mainnet status unclear) | The Ad-Astra Bridge moves tokens between MultiversX and Ethereum or BNB Smart Chain through safe and bridge contracts on each side operated by ten relayers. MultiversX also documents an Axelar verifier setup, but its mainnet contract entries read 'TBD'. Risk: Transfers are approved by 7 of 10 relayers, five run by the MultiversX Foundation and five by community validators, so collusion or compromise of seven relayers, or a contract bug, could mint or release unbacked tokens. Bridged USDC and USDT depend on the Ethereum-side safe and are not issued by Circle or Tether on MultiversX. 232425 |
| Block explorers | First-partyMultiversX Explorer | MultiversX's documentation links its own explorer. Third-party explorers were not verified. Explorer data is provider-indexed and is not a quality check. 35 |
| Hardware wallets | Established in the ecosystemLedger | See custody rows: Ledger lists a MultiversX device app and EGLD management and delegation in Ledger Live; Trezor states it does not support MultiversX. 3639 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Yes | Can: Install the MultiversX app on a Ledger device from Ledger Live's app catalog Can: Manage EGLD in Ledger Live Can: Delegate EGLD to the Ledger by Figment staking provider from Ledger Live Can: Sign transactions in the MultiversX Web Wallet with a Ledger device, including setting a guardianLedger's MultiversX page was last modified in September 2023, and support for individual MultiversX tokens in Ledger Live was not re-verified. 363738 |
| Trezor | None foundSame as native: No | Cannot: Manage MultiversX accounts in Trezor Suite Cannot: Treat wrapped EGLD on BNB Smart Chain or Energi as MultiversX custodyTrezor's MultiversX page says Trezor does not currently support MultiversX; its Wrapped EGLD page lists only the Energi and BNB Smart Chain networks. Third-party signing paths were not checked. 3940 |
Public data
iKnow Blockchain has no public-data lookups for MultiversX yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
Mainnet halted for more than five days and was restarted from a recovery checkpoint
Nine days after Supernova, MultiversX mainnet stopped processing transactions at about 06:38 UTC on 19 September 2026. Mainnet configuration v2.1.2.0, published on 23 September, restarted the network from a recovery checkpoint at the last round with indexed transactions and excluded the rounds up to about 16:35 UTC on 23 September. The restarted network stalled again at about 16:53 UTC after indexing 114 transactions, almost all protocol reward payouts. Configuration v2.1.5.0, published on 24 September, excluded a second window from 21:00 UTC on 23 September to 15:30 UTC on 24 September, and block production and user transactions resumed at about 15:30 UTC on 24 September.
- Implementation:recovery checkpoint and excluded rounds in mainnet configuration; node v2.1.5 keeps the state trie check but writes only missing nodes, per its commit message
- Release:configuration v2.1.2.0 (pre-release) and v2.1.3.0 published 2026-09-23; configuration v2.1.5.0 and node v2.1.5 published 2026-09-24
- Activation:brief restart at about 16:35 UTC on 23 September, stalled again by about 16:53 UTC; normal processing resumed at about 15:30 UTC on 24 September per public API data
Sources: multiversx/mx-chain-mainnet-config repository — mx-chain-mainnet-config v2.1.2.0 (external site) · multiversx/mx-chain-mainnet-config repository — Mainnet config changes v2.0.9.0 to v2.1.2.0 (external site) · multiversx/mx-chain-mainnet-config repository — Mainnet config changes v2.1.2.0 to v2.1.5.0 (external site) · multiversx/mx-chain-go repository — mx-chain-go v2.1.5 (external site) · MultiversX public API — Metachain blocks at nonce 33336398 (external site) · MultiversX public API — Transaction count, 19 September 06:38 UTC to 23 September 16:34 UTC 2026 (external site)
-
Mainnet configuration scheduled Supernova for epoch 2233; it activated on 10 September 2026, cutting rounds from 6 seconds to 0.6 seconds
The mainnet configuration release v2.0.6.0 set Supernova to activate at epoch 2233. That epoch began on 10 September 2026, and the configuration changes the round duration from 6,000 to 600 milliseconds from it, with 144,000 rounds per epoch. Supernova has validators vote on a block before executing it and records execution results in later headers. It had been approved by an on-chain vote in January 2026, according to MultiversX.
- Proposal:MIP-27 proposed August 2025; approved by on-chain vote in January 2026 according to MultiversX
- Implementation:node v2.0.x
- Release:mainnet configuration v2.0.6.0 released 2026-09-04
- Activation:active from epoch 2233 (10 September 2026) per mainnet configuration and live network data
Sources: multiversx/mx-chain-mainnet-config repository — mx-chain-mainnet-config v2.0.6.0 (external site) · multiversx/mx-chain-mainnet-config — Mainnet config.toml (v2.1.5.0) (external site) · MultiversX public gateway — Mainnet gateway network configuration (external site) · MultiversX Agora forum — MIP-27: Supernova - Sub-second Finality (external site) · MultiversX Docs — Preparing SCs for Supernova (external site) · MultiversX Docs — Terminology (external site)
-
EGLD moved from a supply cap to tail inflation
Release v1.11.1, Staking V5 and New Emissions Model Phase 1, implemented the economic change approved by governance in October 2025. From epoch 1951 (about 2 December 2025) issuance is calculated from the current total supply, starting at 8.757% a year, falling by 0.25 percentage points each economics year, with a 2% floor, and is split among staking rewards (50%), an ecosystem growth fund (20%), a growth dividend (20%) and protocol sustainability (10%).
- Proposal:approved by on-chain vote in October 2025 according to MultiversX's glossary
- Implementation:implemented in node v1.11.1
- Release:v1.11.1 released 2025-11-24
- Activation:active from epoch 1951 per the mainnet economics file
Sources: MultiversX — Release: Staking V5 and New Emissions Model - Phase 1 - v1.11.1 (external site) · multiversx/mx-chain-mainnet-config — Mainnet economics.toml (v2.1.5.0) (external site) · MultiversX Docs — Terminology (external site)
-
Relayed transactions versions 1 and 2 were switched off
MultiversX's Barnard Patch 3 release (v1.10.8) scheduled the removal of the two older relayed-transaction formats at epoch 1918, expected on 30 October 2025, leaving only version 3, in which the relayer's address and signature are fields of the transaction itself. The mainnet configuration sets the same epoch.
- Implementation:implemented in node v1.10.7 and v1.10.8
- Release:v1.10.8 released 2025-10-21
- Activation:in effect from epoch 1918 (about 30 October 2025), as set in the mainnet configuration
Sources: MultiversX — Release: Barnard Patch 3 - v1.10.8 (external site) · multiversx/mx-chain-mainnet-config — Mainnet enableEpochs.toml (v2.1.5.0) (external site) · MultiversX Docs — Relayed Transactions (external site)
Topics your AI can explain
Your AI can explain these topics for MultiversX through the connection, with sources.
Known gaps
What this profile's review did not establish:
- No official incident report for the September 2026 stoppage was reviewed; its timing comes from the mainnet configuration and public API data, and its cause is not stated here. The API shows the network restarted at about 16:35 UTC on 23 September, stalled again at about 16:53 UTC after indexing almost only protocol reward payouts, and resumed normal processing at about 15:30 UTC on 24 September.
- Whether any user transactions or finalized blocks were discarded by the September 2026 recovery checkpoint was not confirmed; the public API shows no indexed transactions in the excluded rounds.
- Whether stake slashing for double-signing is enforced on mainnet was not confirmed; the docs describe it both as reserved for serious offences and as upcoming.
- Hardware and bandwidth needs after Supernova's shorter rounds were not re-documented; the cited requirements pages predate the upgrade.
- No maintained light client, atomic swap tooling, channel network or rollup anchored to MultiversX was found.
- The mainnet status of Axelar routes to MultiversX was not confirmed; the setup page lists mainnet contracts as to be decided.
- No production sovereign chain connected to mainnet was verified.
- Hatom's site blocked access, so USH collateral, governance and issuer controls were not reviewed.
- Third-party block explorers and third-party Trezor signing paths were not checked.
- Whether any transaction fee is burned on mainnet could not be confirmed. The glossary says 10% of base fees are burned today but also that the new fee framework is not yet implemented; MultiversX's Staking V5 release note says that framework would start about one month after Supernova; and the mainnet economics file at review sets a 30% contract-owner share and a 10% block-leader share with no burn setting.
- MultiversX's own statements about uptime and staking-provider counts were not independently verified and are not repeated here.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Consensus (Secure Proof-of-Stake) (external site)
- Sharding (external site)
- Terminology (external site)
- MIP-27: Supernova - Sub-second Finality (external site)
- Mainnet enableEpochs.toml (v2.1.5.0) (external site)
- Mainnet config.toml (v2.1.5.0) (external site)
- Mainnet economics.toml (v2.1.5.0) (external site)
- Mainnet gateway network configuration (external site)
- Mainnet config changes v2.0.9.0 to v2.1.2.0 (recovery checkpoint) (external site)
- Mainnet config changes v2.1.2.0 to v2.1.5.0 (second excluded window) (external site)
- Metachain blocks at nonce 33336398 (both recorded sequences) (external site)
- Transaction count, 23 September 16:47 UTC to 24 September 15:30 UTC 2026 (returned zero) (external site)
- System Requirements (external site)
- Observing Squad (external site)
- What is MultiversX? (external site)
- Staking v4 (external site)
- Validator identities with stake share (external site)
- Validators - Overview (external site)
- Built-In Functions (external site)
- xPortal (Invisible Guardians) (external site)
- MultiversX Virtual Machine (SpaceVM) (external site)
- Relayed Transactions (external site)
- Ad-Astra Bridge architecture (external site)
- Bridge transfer flows (external site)
- Axelar Amplifier Setup (external site)
- Sovereign Chains concept (external site)
- Welcome to xExchange (external site)
- Liquidity Pools (external site)
- AshSwap (external site)
- Token USDC-c76f1f (WrappedUSDC) (external site)
- Token USDT-f8c08c (WrappedUSDT) (external site)
- Token USH-111e09 (HatomUSD) (external site)
- USDC contract addresses (external site)
- Supported protocols (external site)
- Useful Links & Tools (external site)
- MultiversX (Elrond) Wallet (external site)
- Staking EGLD (external site)
- Ledger (external site)
- MultiversX coin page (external site)
- Wrapped EGLD wallet (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding