Moonbeam is an EVM-compatible parachain in the Polkadot ecosystem. GLMR is its native asset for gas, staking-related participation and governance.
Use this page to separate Moonbeam execution from Ethereum Mainnet, understand GLMR gas and collator roles, and prepare cross-chain actions with the correct finality and asset representation.
Subject:
Moonbeam
Market mode:
Snapshot Only
Fee asset:
GLMR
Timezone:
UTC
This page does not guarantee a cross-chain message, recommend a collator or treat EVM compatibility as shared Ethereum state.
Content ownership: BitcoinToolkit Editorial TeamTechnical references: Official protocol and developer documentation.Review approach: Technical explanations are checked against primary sources and updated when the network or asset changes.Last content review: Data integration last tested:
Moonbeam at a Glance
SubjectMoonbeam
Native AssetGLMR
Fee AssetGLMR
Network TypePolkadot parachain
ExecutionEVM compatible
Market ModeSnapshot Only
Moonbeam is an EVM-compatible Polkadot parachain, not Ethereum Mainnet.
GLMR pays gas locally; collators and relay-chain validators have different duties.
How Moonbeam Uses Polkadot Shared Security
Moonbeam combines local parachain block production with relay-chain validation and finality.
Collators and validators
Collators maintain Moonbeam state, collect EVM transactions and produce candidate parachain blocks with state-transition proofs. GLMR holders can support collator candidates under Moonbeam staking rules. Collators are not the same as Polkadot relay-chain validators.
Relay-chain validators check the parachain transition and participate in Polkadot consensus. GRANDPA finality on the relay chain gives Moonbeam deterministic finality once the relevant relay-chain state is finalized. A service should monitor that state rather than equating the first collator block with the strongest final result.
What shared security does not mean
Moonbeam has its own runtime, governance, accounts and contract deployments. Shared security does not merge Moonbeam balances or state with Polkadot, Ethereum or another parachain.
GLMR Gas and EVM Compatibility
Ethereum tools can connect to Moonbeam, but every transaction belongs to Moonbeam state.
Sending and deploying
A Moonbeam EVM transaction includes a sender nonce, recipient or contract data, value and gas fields. The sender signs through an Ethereum-compatible wallet and pays execution fees in native GLMR. Contract tokens do not automatically pay the gas balance.
Solidity bytecode and familiar JSON-RPC methods reduce migration effort, but chain ID, RPC URL, block behavior, precompiles and deployed addresses remain Moonbeam-specific. A contract on Ethereum Mainnet is not present on Moonbeam unless it was deployed there, and the two contracts can hold different state.
Developer implication
Test Moonbeam-specific precompiles, finality events and fee behavior. Indexers must understand both Ethereum-style logs and the surrounding Substrate and parachain context.
Cross-Chain Messaging and Asset Checks
Cross-chain support is a capability, not a promise that every asset or route is interchangeable.
Messages and representations
Moonbeam can interact with other ecosystems through supported messaging and bridge paths. Each route defines its own origin, destination, asset representation, fee requirements and completion state. A token symbol shown on two chains does not prove the contracts or backing path are the same.
Before sending, verify the official route, destination support, amount format and account type. Keep GLMR for the local Moonbeam action and the destination chain's fee asset for the next transaction. Cross-chain completion can lag local execution or fail for route-specific reasons.
Security boundary
Polkadot finality secures the accepted Moonbeam state, while an external bridge or application adds its own contracts, operators and failure modes.
Moonbeam Checks Before You Sign
Most errors come from assuming EVM sameness where only interface compatibility exists.
Checklist
Confirm the Moonbeam chain ID and RPC, verify the contract on Moonbeam, keep GLMR for gas, inspect the cross-chain route and wait for the finality level the receiving service requires.
Do not treat Moonbeam as Ethereum Mainnet.
Do not confuse collators with relay validators.
Do not infer token identity from a symbol.
Do not promise instant cross-chain completion.
Next action
Use current Moonbeam network details and inspect the transaction on a Moonbeam-aware explorer before a production transfer or deployment.