Manta BridgeDoes Manta Pacific still use Celestia for data availability?
Yes. Current verification sources used for this page still identify Celestia as part of Manta Pacific's data availability design.
The L2BEAT Manta Pacific profile shows Manta Pacific with Celestia and Built on OP Stack badges, while the Manta fact sheet identifies Celestia as the network's data availability layer. For a deeper bridge-specific explanation, read how Celestia data availability supports Manta Pacific deposits.
| Attribute | Current value | Source |
|---|---|---|
| Chain ID | 169 | L2BEAT Manta Pacific profile and Manta Network Information docs |
| Gas token | ETH | L2BEAT profile and Manta Network Information docs |
| OP Stack basis | Listed with Built on OP Stack context | L2BEAT Manta Pacific badges and Manta fact sheet |
| Data availability | Celestia | L2BEAT Celestia badge and Manta Celestia documentation |
| Bridge route relevance | Ethereum Mainnet to Manta Pacific native route | Manta Bridge route fact sheet |
Has Manta Pacific's chain ID changed?
No current source checked for this page shows a chain ID change. Manta Pacific remains Chain ID 169 with ETH as the gas token.
This matters when adding the network to a wallet, checking an explorer, or signing a bridge transaction. If you are manually configuring MetaMask, use the Manta Pacific MetaMask setup guide and verify the same Chain ID 169 value.
Why does this verification matter before bridging?
Architecture verification keeps the wallet, explorer, and bridge route aligned. A wrong chain ID or stale network summary can lead to confusing balances or bad transaction assumptions.
The same habit applies to ecosystem status pages such as Manta Atlantic status checks and deeper technical questions like Manta Pacific sequencer trust assumptions. For current architecture, prefer a live profile over copied snippets.
Recheck the current L2BEAT risk profile when a route decision depends on architecture or risk assumptions.
Verify before signing: confirm Chain ID 169, ETH gas, OP Stack context, and Celestia DA from live sources before treating a prompt from Manta Bridge as expected.
Open BridgeIs Manta Pacific still built on the OP Stack in 2026?
Yes, the current verification sources used for this page still identify Manta Pacific with OP Stack context. L2BEAT shows a Built on OP Stack badge for Manta Pacific, and the site fact sheet treats Manta Pacific as Manta Network's OP-Stack Ethereum L2.
Does Manta Pacific still use Celestia for data availability?
Yes. L2BEAT's current Manta Pacific profile shows a Celestia badge, and Manta's own docs describe Manta Pacific as using Celestia as the data availability layer. Treat this as an architecture fact to verify from live sources before relying on stale summaries.
Has Manta Pacific's chain ID changed?
No current source checked for this page shows a chain ID change. Manta's Network Information doc and L2BEAT both list Manta Pacific Chain ID 169, and Manta Pacific uses ETH as the gas token.
Where can I verify Manta Pacific's current architecture?
Use L2BEAT's Manta Pacific profile for an independent risk and architecture view, then compare it with Manta Network's own documentation. For wallet setup, verify the Network Information page as well because it lists Chain ID, RPC, gas token, and explorer values.
Why does this verification matter before bridging?
Bridge users sign transactions against a specific chain and route. Confirming Chain ID 169, ETH gas, the Manta Pacific explorer, and the current architecture reduces the chance of using the wrong network, stale wallet settings, or a misleading third-party page.