Manta Pacific RPC: An OP Stack L2 Whose Data Doesn't Live on Ethereum

Most rollups we've covered post their transaction data to Ethereum — that's what makes them rollups, and it's a big part of their cost. Manta Pacific makes a different choice: it's an OP Stack L2, EVM and familiar on the surface, but its data availability lives on Celestia, not Ethereum. That one decision is why Manta is cheap — and technically it turns the chain into a validium rather than a pure rollup. From the RPC it looks like any EVM chain (chain ID 169, standard eth_*, viem/ethers/foundry unchanged), so the interesting part is the modular-DA design and what it means for how you reason about the chain. Here's the map.

The essentials

Manta Pacific mainnet (live since September 2023) is chain ID 169, an OP Stack L2 with:

• ETH as the gas token (18 decimals) — unlike the non-ETH-gas L2s (Fraxtal, Metis), Manta uses plain ETH.
• ~2-second blocks — fast L2 soft confirmation.
• Celestia for data availability — since December 2023 Manta posts DA to Celestia, which makes it a validium and slashes data-posting costs.
• OP Stack optimistic rollup — soft confirmation is immediate; withdrawals to Ethereum follow the ~7-day challenge window.
• EVM-compatible — Solidity, ABIs, Hardhat, Foundry, ethers, and viem all apply directly.

Connecting is boringly standard EVM:

import { createPublicClient, http, defineChain } from "viem";

const manta = defineChain({
  id: 169,
  name: "Manta Pacific",
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: { default: { http: ["https://rpc.swiftnodes.io/rpc/manta?key=YOUR_API_KEY"] } },
});

const client = createPublicClient({ chain: manta, transport: http() });
await client.getBlockNumber();   // just works

The headline: rollup vs. validium, and where your data lives

Here's the distinction that matters. A standard rollup posts its transaction data to Ethereum, so anyone can reconstruct L2 state from L1 alone — data availability is inherited from Ethereum. Manta instead posts that data to Celestia, a purpose-built modular DA layer. Because the data isn't on Ethereum, Manta is a validium: it settles/proves against Ethereum but sources data availability elsewhere.

The trade is straightforward:

• The win: cost. Posting DA to Celestia is dramatically cheaper than Ethereum calldata or even blobs, which is a big reason Manta's fees are low. (For the Ethereum side of this story — calldata vs. blobs — see what are blobs.)
• The trade-off: DA trust. Your assurance that the data will remain available now depends on Celestia's security, not Ethereum's. That's a deliberate, well-understood modular-design choice — but it's a different long-range security assumption than a pure rollup, and worth knowing when you reason about worst-case data recovery.

Manta isn't alone in decoupling DA from Ethereum: Celo took the same modular turn using EigenDA. The pattern — OP Stack for execution, a separate layer for data — is what "modular" means in practice, and Manta is a clean example of it.

From the RPC, all of this is invisible: you still call eth_getLogs, eth_getTransactionReceipt, and friends against chain 169. The DA layer shapes cost and security, not your method calls.

The ZK-applications angle

Manta also positions itself for zero-knowledge applications via its Universal Circuits work — tooling meant to let developers build zkApps (on-chain identity, privacy-preserving logic) without hand-rolling custom circuits. It's more an ecosystem direction than an RPC feature: you interact with those contracts like any others (eth_call / eth_sendRawTransaction), and the ZK machinery lives in the contracts and off-chain proving, not in a special namespace. If you're building privacy or identity primitives, it's the reason to look at Manta specifically; if you're deploying ordinary EVM contracts, it doesn't change your workflow.

Finality: fast soft, ~7-day hard

As an OP Stack optimistic rollup, Manta gives fast soft confirmation (~2s) at the sequencer, but true L1 settlement — and withdrawals back to Ethereum — waits out the ~7-day optimistic challenge window. If your app moves value L2→L1, design for that delay; the model is in soft vs. hard finality, the same shape as OP-aligned chains like Unichain. And treat the L2 head like any optimistic rollup — reorg-capable at the tip until settlement, so key your indexer on block hash and reconcile (handling chain reorgs).

What carries over unchanged

Because Manta is EVM-compatible, treat it as a standard EVM chain:

• eth_call, eth_getBalance, eth_getLogs, eth_getTransactionReceipt, eth_estimateGas, eth_sendRawTransaction, eth_subscribe all behave normally.
• Solidity contracts, ABIs, and the viem/ethers/hardhat/foundry toolchain deploy and run as-is.
• ETH is the 18-decimal gas token; WebSocket subscriptions work; at ~2s blocks, stream rather than tight-poll.

The short version

Manta Pacific (chain ID 169) is an EVM OP Stack L2 whose defining choice is modular data availability: it posts DA to Celestia instead of Ethereum, which makes it a validium and makes it cheap — at the cost of anchoring data-availability trust on Celestia rather than Ethereum. It also targets zero-knowledge applications via Universal Circuits, but that's an ecosystem direction, not an RPC feature. From the endpoint it's standard EVM (ETH gas, viem/ethers/foundry unchanged), with fast ~2s soft confirmation and a ~7-day L1 withdrawal window. Build it like any OP Stack chain; just understand that "where the data lives" is the thing that makes Manta Manta.

Building low-cost DeFi or ZK applications on Manta Pacific? A flat-rate Manta Pacific RPC endpoint gives you chain 169 over HTTP and WebSocket alongside 75+ other chains under one key. Grab a free key and point your stack at:

https://rpc.swiftnodes.io/rpc/manta?key=YOUR_API_KEY