Metis Andromeda is an EVM-compatible Ethereum Layer 2. METIS is used for user-facing transaction fees and participates in the decentralized sequencer system.
Use this page to understand METIS gas, the sequencer path, bridge deposits and withdrawals, and which finality state a wallet or application should require.
Subject:
Metis
Market mode:
Snapshot Only
Fee asset:
METIS
Timezone:
UTC
This page does not promise a fixed withdrawal time, sequencer reward, bridge quote or investment return.
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:
Metis at a Glance
SubjectMetis Andromeda
Profiled AssetMETIS
Fee AssetMETIS
Network TypeEthereum Layer 2
OrderingDecentralized sequencer system
Market ModeSnapshot Only
Metis Andromeda is an Ethereum Layer 2, not an independent L1.
METIS pays local gas and supports sequencer participation.
How Metis Sequencers Order and Settle Transactions
Metis separates fast L2 execution from the stronger settlement path anchored to Ethereum.
Ordering and batching
Users submit signed EVM transactions to Metis RPC infrastructure. The active sequencer validates and orders them, builds L2 blocks and returns transaction receipts. The decentralized sequencer system rotates responsibility and uses consensus and multi-party signing components to coordinate batch submission.
Signed batches and state commitments are submitted to Ethereum through the protocol contracts. Ethereum provides the upstream settlement layer, while Metis provides the execution environment and fast local feedback. A local receipt is useful, but an application can require a later committed state for high-value decisions.
Not an L1 validator model
Metis sequencer nodes do not turn the page into a generic proof-of-stake Layer 1. Their duties concern L2 ordering, batch formation, rotation and submission under the documented architecture.
METIS Gas and EVM Execution
Familiar Ethereum transaction fields are applied to Metis state and fees.
From signature to receipt
A transaction carries a nonce, destination or contract data, value and gas settings. The sender signs with an Ethereum-compatible wallet and pays the resulting Layer 2 execution fee in METIS. A contract-token balance cannot automatically replace the native METIS fee balance.
Contracts use EVM-compatible tooling, but deployments, RPC endpoints, block numbers and storage are specific to Metis. Developers should test revert handling, gas estimation and finality monitoring against Metis instead of copying Ethereum Mainnet assumptions unchanged.
User implication
Keep enough METIS for the transaction after a bridge deposit, confirm the chain before signing and inspect the receipt on a Metis-aware explorer.
Deposits, Withdrawals and Finality
A bridge transfer crosses security domains and has more states than a local payment.
Bridge workflow
A deposit begins on the source chain and creates the supported representation on Metis after the bridge observes the required source state. A withdrawal begins on Metis and follows the current protocol path back to Ethereum. Token support, proof or challenge handling and completion timing depend on the selected route.
Verify the official bridge, source and destination token contracts, receiving wallet and fee balances on both chains. Do not send directly to a deposit address or exchange route unless that service explicitly supports the same network and asset representation.
Finality levels
Distinguish transaction submission, L2 inclusion, sequencer consensus, batch submission and Ethereum settlement. The receiving application should state which level it accepts.
Metis Checks Before You Move Funds
Network and bridge verification should happen before the signature.
Checklist
Confirm Metis Andromeda, verify the bridge and token representation, keep METIS for gas, review the destination, and wait for the required settlement state.
Do not treat an L2 receipt as universal Ethereum finality.
Do not assume every exchange supports Metis deposits.
Do not confuse a sequencer with an L1 validator.
Do not rely on a fixed withdrawal time.
Next action
Inspect current Metis bridge and sequencer documentation, then test the complete deposit or withdrawal path with a small amount.