Mantanetwork separates execution, data availability, settlement, and proof checks across distinct network paths

Functions split across Pacific and Atlantic

The two networks have served different purposes, so they produce different records. Pacific runs EVM-compatible applications and connects its state to Ethereum. Atlantic focused on Polkadot-based identity, credential, staking, and governance functions. Its announced closure now turns Atlantic activity into an asset-review and migration task.

Pacific handles EVM application activity

Manta Pacific accepts Solidity smart contracts and familiar EVM transaction calls. A wallet submits a signed call, the Layer 2 executes it, and a receipt records whether execution succeeded or reverted. Contract logs and the resulting account or application state show what that call changed. Those records answer the immediate execution question, not every later settlement question.

Its modular design assigns separate jobs to different systems. Pacific handles execution, Celestia provides data availability, and Ethereum receives state commitments. This split supports lower-cost execution, but it also means that a single status label cannot describe every layer at once.

Atlantic has moved toward exit

Manta Atlantic was the Polkadot Layer 1 path for native MANTA, staking, governance, and zero-knowledge credential functions. The active migration interface says that the mainnet will cease operations. Holders therefore need to inspect assets and staking status, then follow an available migration bridge to a destination state.

The umbrella still explains both network designs, yet the paths are no longer equivalent entry choices. Pacific remains the application path described by current network information. Atlantic requires migration evidence and a clear exit record.

Four actions leave different evidence

Compare the action first, then identify which record establishes completion. The same wallet notification can mean very different things across these paths.

Open full-size image

How does a Pacific transaction become final?

Pacific first executes a transaction, then includes it in a batch whose data and state commitment move through separate layers. Each stage answers a different question, while the required evidence depends on whether the task stays on Pacific or crosses to Ethereum.

Execution creates the first receipt

The earliest useful record contains the transaction hash, block inclusion, sender, destination contract, status, and emitted logs. A successful status means the EVM call did not revert. The logs or resulting state must still match the intended operation, because a contract can execute successfully without producing the outcome that a user expected.

Data and state commitments connect the layers

Manta Pacific executes transactions on Layer 2, makes batch data available through Celestia, and publishes state roots to Ethereum. Data availability supports reconstruction of the batch, while the state root commits to the resulting Layer 2 state. Neither record is interchangeable with a destination-chain balance.

Settlement adds a challenge boundary

The current Pacific architecture uses an optimistic settlement model. State commitments can face a challenge process before they reach the stronger finality needed for a native withdrawal. Fast-finality mechanisms address that delay at the protocol level, but a route must expose the resulting state before it is reasonable to treat a transfer as complete.

A fast-finality design and a native bridge challenge flow can describe different stages. Do not assume that one eliminates the other. The operational signal is the actual state that the chosen route exposes for that transaction.

A receipt and a completed outcome are different states

A receipt proves that one chain processed a transaction. Completion proves that the intended state exists where it is supposed to exist. For an application call, that may be a changed contract value or emitted event. For a transfer, it is the corresponding asset representation in the destination account.

This distinction prevents a common reconciliation error. A source transaction can succeed while a relayed message remains pending, a destination action still needs completion, or the wallet displays a different chain. The expected state and the observed state must refer to the same account, asset, and network.

Native deposits and withdrawals diverge

The native bridge is bidirectional, but its two directions do not have matching timelines or evidence. Deposits begin on Ethereum and finish on Pacific. Withdrawals begin on Pacific, pass through verification and a challenge period, and finish through an Ethereum transaction.

Deposits end with Pacific state

A native deposit starts when the user signs an Ethereum transaction for a supported asset. The source record shows that the deposit entered the bridge. Completion arrives when Pacific records the credit and the intended account can see the correct asset representation. A bridge history entry can help track progress, but it does not replace the destination state.

Withdrawals require a later completion action

A native withdrawal reaches Ethereum completion after verification, the waiting period shown by the route, and a finalization transaction. Initiation on Pacific is therefore an intermediate state. Verification on Ethereum is another intermediate state. The final Ethereum transaction establishes access to the withdrawn asset.

Third-party bridges follow their own contracts, liquidity paths, and status models. They are independently operated, so their completion evidence cannot be borrowed from the native route. A shorter route still needs a matching destination record.

Zero-knowledge verification has a narrower scope

A zero-knowledge proof lets a verifier test a statement without learning the private witness used to construct that proof. Mantanetwork has used this mechanism for application features and credentials. The proof only covers the statement encoded by its circuit and public inputs.

That scope matters when reading a transaction record. A zero-knowledge feature does not make every Pacific transaction private, and it does not turn every Layer 2 receipt into an Ethereum settlement proof. Application proof verification, rollup state publication, and bridge completion remain separate claims with separate evidence.

Chain identity anchors account and asset checks

Account verification begins by matching the wallet type, selected network, account, and asset representation. Pacific uses an EVM account and EVM transaction record. Atlantic uses its Polkadot-oriented account path and migration interface. A familiar token symbol cannot resolve the difference, because the same economic asset may have a native representation on one chain and a contract representation on another. The record must identify the chain and representation that the action actually used.

Open full-size image

Atlantic verification now centers on migration

The Atlantic migration flow asks a holder to connect a compatible Polkadot wallet, inspect assets, review staking status, and use an available migration bridge. Those checks establish the starting state. They do not by themselves show that a migration has finished.

Completion requires a destination-side record for the selected route. An Atlantic debit, approval, or submitted migration transaction is only the source half of that evidence. If staking affects transferability, the visible staking state must be reconciled before the transferable balance can be treated as the full account position.

Reconciliation begins at the last confirmed state

A missing result is easier to diagnose when the last confirmed record is identified first. The transaction may have reverted, succeeded only on the source chain, entered a relay queue, reached a verification stage, or completed while the wallet still displays stale data. These states require different responses.

For a reverted transaction, the state did not advance as intended, so the revert reason and transaction inputs matter before another submission. When the source succeeded but the destination remains absent, route history and destination-chain records should show whether the message is pending or needs a separate action. Repeating the source transfer can create a second transfer without resolving the first.

Open full-size image

A wallet display is useful, yet it is not the only state view. A public transaction explorer can separate a delayed interface from a missing on-chain event. If the event exists but the balance does not, check the selected network, account, and asset contract before treating the operation as lost.