> 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/security/is-manta-bridge-safe.md).

# is manta bridge safe

Manta Bridge is designed to move assets between Ethereum and Manta Pacific, but no bridge should be treated as risk-free. Use this page to understand the main safety model, what to verify before signing, and where bridge risk can still exist.

## Short Answer

Manta Bridge uses a native rollup bridge model for Manta Pacific. In this model, deposits and withdrawals are handled through smart contracts and rollup messaging rather than through a separate custodial exchange account.

That design can reduce some trust assumptions, but it does not remove all risk. You still need to verify the website, wallet prompts, token approvals, contract addresses, transaction direction, and live network conditions before using the [Manta Bridge](https://mantabridge.cc/).

{% hint style="warning" %}
**Important:** This page is not a guarantee of safety. Always verify live details in the official app and with reputable block explorers before signing transactions.
{% endhint %}

## What the Bridge Relies On

Manta Pacific is an Ethereum L2 built with OP Stack execution and external data availability. Deposits move assets from Ethereum L1 to Manta Pacific L2. Withdrawals follow the rollup exit model, where the withdrawal path is governed by the L2 design and the contracts connected to Ethereum.

At a high level:

| Component         | What to understand                                                                           |
| ----------------- | -------------------------------------------------------------------------------------------- |
| L1 contracts      | Bridge contracts on Ethereum coordinate deposits, messages, and exits.                       |
| L2 execution      | Transactions execute on Manta Pacific, where ETH is used as the gas token.                   |
| Rollup exit model | Withdrawals follow the rollup's settlement and exit process, not a normal L1 token transfer. |
| ERC-20 approvals  | Tokens such as USDC usually require an approval before the bridge can move them.             |

For background on the rollup security model, see the ethereum.org overview of [optimistic rollups](https://ethereum.org/developers/docs/scaling/optimistic-rollups/) and the Optimism documentation for the [OP Stack](https://docs.optimism.io/op-stack/protocol/getting-started).

## What to Verify Before Bridging

Before signing any transaction, check:

1. You are on the official bridge domain, reached from a trusted source.
2. Your wallet is connected to the intended source network.
3. The direction is correct: Ethereum to Manta Pacific for deposits, or Manta Pacific to Ethereum for withdrawals.
4. The token and amount match what you intend to move.
5. The wallet prompt shows the expected transaction type, network, and contract interaction.
6. Any ERC-20 approval uses an amount you are comfortable leaving as an allowance.
7. Live fees, estimated timing, and route details are acceptable before you sign.

For a step-by-step review flow, use the [bridge safety checklist](file:///2078213/security/safety-checklist.md).

## Token Approval Risk

ETH transfers do not use ERC-20 allowances, but ERC-20 tokens do. If you approve a bridge contract to spend USDC or another token, that approval remains available until it is used, reduced, or revoked.

The ERC-20 model includes `approve`, `allowance`, and `transferFrom`, which let one contract move tokens from a wallet up to an approved amount. For the underlying standard, see the ethereum.org [ERC-20 overview](https://ethereum.org/developers/docs/standards/tokens/erc-20/).

Prefer exact or limited approvals when practical, and review old allowances periodically. See [Token Approvals Explained](file:///2078213/guides/token-approvals.md) for approval-specific guidance.

## General Bridge Risks

Bridges can involve several categories of risk:

* **Smart contract risk:** Bridge and token contracts can contain bugs or unexpected behavior.
* **Interface risk:** Fake websites, malicious ads, DNS issues, or copied UIs can trick users into signing unsafe transactions.
* **Approval risk:** Large ERC-20 allowances can remain active after a bridge transaction.
* **Network risk:** Congestion, sequencer issues, or changing gas prices can affect transaction cost and timing.
* **Withdrawal risk:** Rollup withdrawals are different from normal transfers and may involve additional steps or waiting.

## Practical Safety Habits

Use a dedicated wallet for bridging when appropriate, start with a small test transfer for unfamiliar assets or routes, and reject any wallet prompt that does not match the action you expected. Keep enough ETH on the source network for gas, and verify final balances on the relevant network before assuming a transfer is complete.


---

# 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/security/is-manta-bridge-safe.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.