> For the complete documentation index, see [llms.txt](https://mantabridge.gitbook.io/manta-bridge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mantabridge.gitbook.io/manta-bridge-docs/what-is-manta-pacific.md).

# what is manta pacific

Manta Pacific is a modular Ethereum Layer 2 network used by Manta Bridge for moving assets between Ethereum and Manta Pacific. It uses ETH for gas and combines OP Stack execution with Celestia data availability.

## Overview

Manta Pacific is designed as an Ethereum L2: transactions execute away from Ethereum mainnet, while the network still follows a rollup-style model for bridging, settlement, and exits. For bridge users, the important point is that Manta Pacific is a separate network in your wallet, but it uses familiar Ethereum-style accounts, transactions, and token standards.

To learn how the bridge fits into this flow, see [What Is Manta Bridge?](file:///2078213/getting-started/what-is-manta-bridge.md). For the fee components users see while transacting, see [Gas Fees](file:///2078213/reference/gas-fees.md).

## Core Components

| Component                  | What it means for users                                                                                                                                 |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ethereum L2                | Manta Pacific is a Layer 2 network connected to Ethereum, so deposits and withdrawals interact with bridge contracts across L1 and L2.                  |
| OP Stack execution         | The execution environment follows the OP Stack architecture, which is used to build optimistic rollup-style chains.                                     |
| Celestia data availability | Transaction data can be published to a dedicated data availability layer instead of treating Ethereum L1 as the only data publication venue.            |
| ETH gas token              | Transactions on Manta Pacific require ETH for gas. Keep a small ETH balance on Manta Pacific before sending tokens, swapping, or interacting with apps. |

## Modular L2 Architecture

Traditional blockchains often bundle execution, settlement, consensus, and data availability into one system. Modular networks separate some of these responsibilities so each layer can specialize.

For Manta Pacific, the key split is:

1. **Execution:** user transactions and smart contract interactions run on Manta Pacific.
2. **Settlement and bridging:** deposits and withdrawals connect back to Ethereum through bridge contracts and the rollup exit model.
3. **Data availability:** transaction data is made available through Celestia, which is built specifically for data availability.

The OP Stack provides the framework for L2 execution and rollup operations. Celestia provides a data availability layer, which helps nodes and verifiers access the transaction data needed to reconstruct or verify chain state. For background, see the [OP Stack documentation](https://docs.optimism.io/op-stack/protocol/getting-started) and Celestia's guide to [data availability](https://docs.celestia.org/learn/celestia-101/data-availability/).

## Why Data Availability Matters

Data availability means that the data behind L2 transactions can be accessed by the parties that need to verify the chain. If transaction data is unavailable, it becomes harder for independent participants to reconstruct state or challenge invalid behavior.

Modular data availability matters because it separates the job of publishing transaction data from the job of executing transactions. Conceptually, this can help an L2 scale by using a layer designed for data publication while keeping Ethereum-compatible execution for users and applications.

{% hint style="warning" %}
Modular data availability changes how the network is built; it does not remove normal bridge or smart contract risks. Always review the transaction, network, token, and fee details before confirming.
{% endhint %}

## ETH as the Gas Token

ETH is the gas token on Manta Pacific. You need ETH on Manta Pacific to pay for L2 transactions, including token transfers and contract interactions.

This is separate from the asset you are bridging. For example, bridging USDC gives you USDC on Manta Pacific, but you still need ETH on Manta Pacific to send that USDC or use it in an app. Gas prices can change with network activity and transaction complexity, so check the live wallet estimate before confirming. Ethereum's [gas documentation](https://ethereum.org/developers/docs/gas/) explains the general gas model.

## What This Means for Bridging

When you deposit, assets move from Ethereum L1 to Manta Pacific L2. When you withdraw, the transfer follows the rollup's exit path back to L1. ERC-20 deposits and withdrawals may also require token approvals before the bridge can move the selected token.

Before bridging, confirm:

1. Your wallet is connected to the intended network.
2. You have ETH for gas on the network where the transaction starts.
3. You understand whether the action is a deposit or withdrawal.
4. Any live fee, gas, and confirmation details shown by the official bridge interface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mantabridge.gitbook.io/manta-bridge-docs/what-is-manta-pacific.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
