Wrapped and native tokens on Manta Pacific serve different roles

On Manta Pacific, a wrapped balance represents an asset brought from another network, while a native token was first created on Manta Pacific. They can share a ticker or track the same value, but their contracts and routes back to another chain differ.

Manta Network’s token-list repository labels tokens bridged through its canonical bridge as “canonical-bridge” and tokens first created on Pacific as “native.” The distinction matters when you trade, provide liquidity or withdraw: the label alone is not enough, so check the token’s contract address and bridge route. For the transfer mechanics between Ethereum and Pacific, see this guide to the manta bridge. The bridge page shows the selected asset and destination balance before a transaction.

What does a wrapped balance mean on Manta Pacific?

A wrapped balance is a token entry on Manta Pacific that stands for an asset issued elsewhere. When an asset crosses a bridge, the destination network must record an amount that its applications can read and transfer; a token contract supplies that record. Manta’s token list gives DAI as an example: it lists one address on Ethereum and a different address for the canonical-bridge version on Pacific.

That means a familiar symbol is not proof that two balances are the same asset. Applications use contract addresses, not just token names, to identify what is being swapped or deposited. Two tokens can display the same ticker while representing separate bridge routes, issuers or redemption paths.

How is a native token different from a wrapped token?

A native token is issued first on Manta Pacific, according to Manta Network’s token-list definition, rather than arriving as a representation of an asset on another chain. It can still be an ERC-20 token used by decentralized applications; “native” describes where it originated, not a special guarantee of safety, liquidity or value.

There is a second use of “wrapped” in EVM networks: WETH is an ERC-20 representation of ETH, while ETH itself is the network’s native currency. That distinction is about how a wallet or contract handles ETH, not necessarily about whether a token came from Ethereum or was created on Pacific. Check the asset’s contract and the application’s accepted token before making a deposit.

Which balance should you use on Manta Pacific?

Use the version accepted by the specific app and route you need. A token with the right symbol but the wrong contract may not be recognized, may have different liquidity, or may not follow the withdrawal path you expect. Manta’s token list records the token type and, for bridged assets, the original chain and address; these fields help distinguish lookalikes.

• For a transfer, confirm the source network, destination network and bridge route.
• For a swap or deposit, match the contract address shown by the application.
• For a withdrawal, verify that the destination supports that token representation.

Wrapped assets make tokens from another network usable by Pacific applications, while native tokens give projects a way to issue assets directly there. Neither label by itself decides which is better: the practical choice depends on the contract the app supports and whether you need the asset to return through a particular bridge. Before signing, compare the displayed token address and destination details with the route you intend to use.