Other system · settles to Polkadot
Moonbeam ticker GLMR
Historical network. Its profile describes the design as history. The evidence is in the system note below.
Summary
No consensus of its own on 2026-09-27. Until August 2026 Moonbeam was a Polkadot parachain: collators produced blocks, Polkadot relay-chain validators checked them, and the relay chain's GRANDPA gadget finalized them. After the 2026-07-03 relaunch announcement, user transactions have been rejected since 00:00 UTC on 2026-08-01, and Subscan reports the finalized height as 16,796,696, timestamped 2026-08-10 11:35:57 UTC. GLMR now exists as an 18-decimal ERC-20 token on Base, so ordering and settlement of GLMR transfers follow Base's sequencer and Ethereum settlement rather than any Moonbeam mechanism. 1891013142021
Design
- System
- Other systemMoonbeam no longer runs a chain. It launched as an Ethereum-compatible parachain on Polkadot (EVM chain ID 1284). After the 2026-07-03 announcement that it would relaunch on Base, the parachain rejected user transactions from 2026-08-01 and no block after 2026-08-10 was found. GLMR now circulates as an ordinary ERC-20 token on Base, and the announced Moonbeam Protocol is an application on Base marked pre-launch, not a chain or rollup. As a halted chain it uses the other class, and its cells describe the parachain as history.
- Settles to
- PolkadotUntil August 2026 the Moonbeam parachain depended on the Polkadot relay chain: relay-chain validators checked its blocks and GRANDPA finalized them. The chain has halted. GLMR now lives on Base as an ERC-20 token (contract 0xb3846fd356c2149ee8d30b0449088dc74e265459), an ordinary token rather than a Moonbeam chain or rollup, and Base posts its data to Ethereum.
- Settlement family
- Ethereum / EVM
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- While the chain ran, the top collator candidates by bonded plus delegated GLMR formed the active set, Nimbus picked block authors from that set at random regardless of stake size, and collators were not slashed. No collator has produced a block since 2026-08-10; GLMR transfers on Base are ordered by Base's sequencer.
- Fork choice
- No open fork choice: the parachain followed what the Polkadot relay chain included and GRANDPA finalized; before finality the relay chain builds on the chain with the most primary blocks. No Moonbeam fork choice remains, and GLMR on Base follows the Base chain derived from data posted to Ethereum.
Qualifications
- Live chain status · Not applicable. The Moonbeam parachain has rejected user transactions since 2026-08-01 and no block after 2026-08-10 was found, so block time, block metrics, collator counts and node requirements have no live meaning.
- Scarce resource · Partial. Recorded as stake for how the chain ran: collator candidates qualified by bonded plus delegated GLMR, although Nimbus then picked authors at random and collators were not slashed, while block validity and finality came from DOT-staked Polkadot validators. No Moonbeam block production exists now.
- Finality · Partial. While the chain ran, a Moonbeam block was final once the Polkadot relay chain's GRANDPA gadget finalized it, which Moonbeam described as deterministic; that finality was backed by Polkadot's slashable validators, not by Moonbeam's collators. The finalized height stopped at 16,796,696. GLMR transfers on Base follow Base's own staged confirmation, covered in the Base profile.
- Settlement family · Partial. Moonbeam ran the Ethereum virtual machine with Ethereum's account format, and Ethereum wallets worked with it, but it was a Polkadot parachain and never settled to Ethereum. Only the token now lives in the Ethereum family, as an ERC-20 on Base.
- Throughput · Not applicable. No throughput figure is recorded. The Moonbeam chain no longer produces blocks, and transfers of GLMR on Base are limited by Base, which is covered in its own profile.
Tradeoffs
- Emphasizes
- Security and Scalability
- Gives up
- Independence and continuity. Moonbeam relied on the Polkadot relay chain for block validity and finality and on a capped set of collators that were never slashed, and a project-led wind-down stopped the chain in August 2026, leaving funds not migrated in time reliant on discretionary late claims. GLMR itself now depends on Base's single operator-run sequencer and on Base's batches being posted to and finalized on Ethereum.The emphasis describes the parachain design while it ran: security from Polkadot's shared validator set, which checked and finalized its blocks, and scalability from running as one parachain beside others rather than sharing a single chain's block space. No throughput figure was verified. The token's current home on Base is covered by the Base profile, not by this reading.
- Full node at home
- Not applicable 81516There is no live Moonbeam network to follow: user transactions have been rejected since 2026-08-01 and no block after 2026-08-10 was found. The last published guidance asked for 8 cores, 16 GB RAM and a 3 TB SSD, and a Moonbeam node also synced the Polkadot relay chain. Following GLMR on Base means running a Base node; see the Base profile.
- Throughput claims
- No classified figure recorded
Scaling layers
No scaling layer recorded in this profile.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Not present | None: the Moonbeam parachain has rejected user transactions since 2026-08-01 and no block after 2026-08-10 was found, so no swap can settle on it. Any swap of GLMR now uses contracts on Base, which are outside this profile and were not reviewed. 8 |
| Authenticated data publication | Unknown | Not yet assessed under this row's current definition. |
| Light clients | Unknown | Not yet assessed under the current definitions; No light-client path applies to a stopped chain, and none was reviewed for the historical parachain. |
| 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 source was cited for absence, so the rule that absence needs a source makes this unknown. The earlier review found no payment or state channel layer anchored to Moonbeam, and none can operate on a stopped chain. |
| Programmable spending | None found Earlier definition | Nothing can execute on Moonbeam: the parachain has rejected user transactions since 2026-08-01. While it ran, spend conditions were EVM smart contracts. GLMR on Base is an ordinary ERC-20 token governed by Base contracts, which the Base profile covers. 1810 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Not present | None: the Moonbeam parachain has rejected user transactions since 2026-08-01 and no block after 2026-08-10 was found, so no payment on it can be reclaimed, delayed or recovered. While it ran, no protocol clawback or recovery vault was found. The Moonbeam Foundation's late-claim review for GLMR not migrated in time is a discretionary helpdesk process, not a recovery path set up in advance, and Moonbeam Protocol's planned escrow of buyer payments is an application design marked pre-launch. 468 |
| Rollups | None found Earlier definition | No rollup settles to Moonbeam. Moonbeam moved its token onto Base, which is itself a rollup on Ethereum; that makes GLMR a token on a rollup, not a rollup anchored to Moonbeam. 1 |
| 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 | None foundStellaSwap (sunset) | StellaSwap, which describes itself as Moonbeam's DEX, reports operating from 2021-12-12 to 2026-07-31 and is no longer in operation. No venue on the stopped chain is usable. Trading venues for GLMR on Base were not reviewed. 823 |
| Issuer-native stablecoins | None found | No issuer-native stablecoin lived on Moonbeam: Moonbeam's last documentation lists USDC and USDT arriving as Polkadot Asset Hub assets over XCM (xcUSDC, xcUSDT) or as tokens bridged from Ethereum through Snowbridge (USDC.e, USDT.e). Those representations sit on a chain that no longer accepts user transactions. 818 |
| Algorithmic stablecoins | Unknown | No source was cited for absence, so the rule that absence needs a source makes this unknown. No algorithmic stablecoin can operate on the stopped chain; historical algorithmic or hybrid stablecoins on Moonbeam were not reviewed. |
| Bridges | None foundMoonbeam migration portal (closed) | Moonbeam's own GLMR bridge to Base stopped processing transfers after 2026-07-31 23:59 UTC. Earlier routes, including XCM transfers with Polkadot chains and Snowbridge and Wormhole assets, end on a chain that rejects user transactions. Bridges that carry the Base version of GLMR to other networks were not reviewed. Risk: Late claims depend on discretionary review through the Moonbeam Foundation helpdesk; a staff moderator's reply on Moonbeam's forum on 2026-08-22 described a 60-day window without a stated start date and warned that missing it may mean permanent loss of access. Assets bridged in from other networks depend on each bridge's own recovery procedures, which were not reviewed. 56818 |
| Block explorers | ThinSubscan (Moonbeam history), BaseScan (GLMR on Base) | Subscan still shows Moonbeam's history under a maintenance-mode banner. Moonscan, the Etherscan-built explorer named in Moonbeam's docs, returned an access error in this review. BaseScan shows the Base GLMR token contract. Explorer data is provider-indexed, not canonical. 81017 |
| Hardware wallets | ThinLedger (Ledger Wallet; chain halted), Trezor (through MetaMask or Rabby; chain halted) | See custody rows: Ledger Wallet still enables the Moonbeam network by default and Trezor's GLMR page lists the Moonbeam network beside MetaMask and Rabby, but the chain no longer processes transactions. Trezor Suite holds GLMR only as the Base token, and whether Ledger Wallet shows Base GLMR was not checked. 825303132 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Add a Moonbeam account in Ledger Wallet: current Ledger wallet code includes the Moonbeam network with no feature switch, so it is on by default Can: Keep using the same address: Moonbeam's docs set up Ledger accounts through Ledger's Ethereum app, and the migration portal delivered Base GLMR to the same address that sent it Cannot: Move GLMR on the Moonbeam network: the chain has rejected user transactions since 2026-08-01; whether Ledger Wallet still shows Moonbeam balances or history was not checked Cannot: Rely on Ledger's GLMR page for the Base version of the token; the page names the third-party MyCrypto wallet and does not mention Base or the migrationRecorded as native under the custody evidence rule and the shared vendor baseline: Ledger's current wallet code enables Moonbeam by default, which outweighs the older coin page that points to MyCrypto. Native vendor support for a halted chain gives no ability to transact. Whether Ledger Wallet shows Base GLMR was not checked. 5819243031 |
| Trezor | Through an intermediaryMetaMask or RabbySame as native: Unknown | Can: Use a Trezor with the Moonbeam network through MetaMask or Rabby, which Trezor's GLMR page lists; Moonbeam is not a Trezor Suite network Can: Hold the Base version of GLMR in Trezor Suite, which supports Base; that is the token on Base, not the Moonbeam network Cannot: Manage the Moonbeam network in Trezor Suite: current Suite code has no Moonbeam network Cannot: Move GLMR on the Moonbeam network: the chain has rejected user transactions since 2026-08-01Trezor's GLMR page lists the Base and Moonbeam networks with Trezor Suite, MetaMask and Rabby without mapping them. Suite supports Base but has no Moonbeam network, so under the custody evidence rule the device reaches the Moonbeam network only through the third-party apps; holding Base GLMR in Suite is a token on another network and does not count. 8252632 |
Public data
iKnow Blockchain has no public-data lookups for Moonbeam 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
-
Forum staff described a 60-day late-claim process for unmigrated GLMR
Replying on Moonbeam's official forum, a staff moderator said holders who missed the deadline have 60 days to submit a late claim to the foundation helpdesk with address, amount and storage details, reviewed case by case, and warned that missing the window may mean permanent loss of access.
- Implementation:process described by staff
- Release:email-based review
- Activation:window start date not stated
Sources: Moonbeam Community Forum — Missed date for migration requirement (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site)
-
Moonbeam entered maintenance mode and later stopped producing blocks
From 00:00 UTC on 2026-08-01 the network rejected all user transactions while blocks continued for a final wind-down. The last finalized block found in this review, 16,796,696, is dated 2026-08-10 11:35:57 UTC.
- Implementation:maintenance mode active from 2026-08-01
- Release:not applicable
- Activation:block production observed to end 2026-08-10
Sources: Subscan — Moonbeam explorer (external site) · Subscan — Moonbeam block 16796696 (external site) · CryptoSlate — Moonbeam just halted all user transactions (external site)
-
Moonriver's MOVR set to migrate to Base on the same deadline
The sister network on Kusama announced a one-for-one move of MOVR to an ERC-20 token on Base by 2026-07-31, routed through Moonbeam because the bridge contract lived there.
- Implementation:migration route published
- Release:MOVR contract announced on Base
- Activation:standard migration closed 2026-07-31 23:59 UTC
Sources: Moonbeam — Moonriver Strategic Update: MOVR is Migrating to Base (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site) · Subscan — Moonbeam explorer (external site)
-
Moonbeam announced GLMR's move to Base and the end of its Polkadot parachain
Moonbeam said GLMR would migrate one-for-one to an ERC-20 token on Base, asked holders to bridge by 2026-07-31 and to withdraw funds from on-chain applications first, and said the parachain would run only through the transition. It also announced Moonbeam Protocol for AI-agent settlement on Base.
- Implementation:migration bridge opened with the announcement
- Release:GLMR contract live on Base
- Activation:standard migration closed 2026-07-31 23:59 UTC
Sources: Moonbeam — Moonbeam Strategic Update: Moonbeam Network Relaunches on Base (external site) · Moonbeam Foundation — GLMR and MOVR migration portal (external site) · BaseScan — Moonbeam (GLMR) token on Base (external site)
-
Runtime 4401 was released, approved by referendum and activated on 2026-07-13, becoming Moonbeam's last runtime
Moonbeam tagged runtime 4401 on GitHub on 2026-06-15. It set the maximum gas for one EVM transaction to 35 million, made a signed CallPermit count as used even when the call it authorizes fails, began charging EVM gas for P256 signature checks and added a limit on transactions per block. Referendum 155, which authorized the Moonbeam upgrade, is shown as executed. Subscan shows spec 4401 in force by 13:33 UTC on 2026-07-13 and still in force at the final block.
- Proposal:OpenGov Referendum 155 (Root track) opened for voting 2026-06-22 per the forum; Subscan shows it executed, with a call hash matching the release notes
- Implementation:Runtime built for Moonbase Alpha, Moonriver and Moonbeam; node client v0.52.3 named as the minimum version
- Release:Tagged on GitHub 2026-06-15; the Moonbeam upgrade was scheduled for about 13:00 UTC on 2026-07-13
- Activation:Active on Moonbeam by block 16,427,400 (2026-07-13 13:33 UTC) per Subscan, and still the runtime at final block 16,796,696
Sources: Moonbeam Foundation (GitHub) — Runtime runtime-4401 (external site) · Moonbeam Foundation (GitHub) — Moonbeam v0.52.3 (external site) · Moonbeam Community Forum — [Runtime] RT4401 Schedule (external site) · Subscan — Moonbeam referendum 155 (external site) · Subscan — Moonbeam block 16427400 (external site) · Subscan — Moonbeam block 16796696 (external site)
Topics your AI can explain
Your AI can explain these topics for Moonbeam through the connection, with sources.
Known gaps
What this profile's review did not establish:
- Moonbeam's documentation site did not resolve in this review; historical technical facts come from the documentation's GitHub source, last updated 2026-06-29, before the wind-down.
- No primary Moonbeam notice of the final block or of collators stopping was found. The last-block date comes from Subscan and a public RPC query; Moralis's notice says blocks stopped on 2026-08-01, which conflicts with Subscan's block timestamps up to 2026-08-10.
- Moonbeam's own maintenance-mode explainer returned a not-found error; the 2026-08-01 start time comes from Subscan's banner and CryptoSlate's report.
- The start date of the 60-day late-claim window was not stated in the forum staff reply, and the reply does not say whether its author works for the Moonbeam Foundation; it is marked only as forum staff and moderator.
- Subscan's page for block 16,796,696 labels it unfinalized, while Subscan's homepage and the finalized-block query on two public RPC endpoints give it as the finalized height; this review treats it as finalized.
- Moonbeam Protocol is marked pre-launch in its documentation; no contract addresses, launch date or audit were verified.
- Trading venues and liquidity for GLMR on Base, and how many GLMR tokens were not migrated, were not verified from a primary source.
- Whether Ledger Wallet displays Base GLMR was not tested; which Trezor app covers which GLMR network is inferred from Trezor Suite code, not stated on the vendor page.
- Moonscan returned an access error, so its current status is unknown.
- Polkadot's handling of the parachain's slot or coretime after the wind-down, and whether the chain could be restarted, were not reviewed.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- Moonbeam Strategic Update: Moonbeam Network Relaunches on Base (2026-07-03) (external site)
- Moonbeam news (external site)
- Moonriver Strategic Update: MOVR is Migrating to Base (2026-07-07) (external site)
- Moonbeam Protocol documentation (external site)
- GLMR and MOVR migration portal (external site)
- Missed date for migration requirement (staff moderator reply 2026-08-22) (external site)
- Multisig Maintenance & Wind-Down: Moonbeam, Moonriver, and Moonbase July 2026 (external site)
- Moonbeam explorer (maintenance-mode banner, finalized height) (external site)
- Moonbeam block 16796696 (external site)
- Moonbeam (GLMR) token on Base (external site)
- Notice of Moonbeam (GLMR) Migration to Base (2026-07-27) (external site)
- moonbeam-foundation/moonbeam (external site)
- Moonbeam Consensus & Finality (docs source, last repo update 2026-06-29) (external site)
- Staking on Moonbeam (docs source) (external site)
- Run a Node on Moonbeam (docs source) (external site)
- Moonbeam docs network variables (chain ID, block time, node specs, staking values) (external site)
- Block Explorers (docs source) (external site)
- XC-20s and cross-chain assets overview (docs source) (external site)
- Interacting with Moonbeam Using Ledger and the Ethereum App (docs source) (external site)
- Proof of Stake Consensus (BABE, GRANDPA) (external site)
- Transaction Finality (external site)
- Connect to Base (external site)
- StellaSwap sunset notice (external site)
- Moonbeam wallet (external site)
- Moonbeam (GLMR) wallet (external site)
- Base wallet (external site)
- Moonbeam just halted all user transactions (2026-08-01) (external site)
- Moralis product changelog (Moonbeam support removal notices) (external site)
- A halted chain renders as a perfectly healthy subgraph (issue 15) (external site)
- Ledger Wallet coin module loaders (ledger-live, develop branch) (external site)
- Currencies hidden behind feature switches (ledger-live, develop branch) (external site)
- Trezor Suite network configuration (trezor-suite, develop branch) (external site)
- Offenses & Slashes on Polkadot (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