How to seed a Mantle pool with bridged assets

To seed a Mantle liquidity pool, bridge the pool’s two supported assets to Mantle, then approve and deposit them through the pool’s interface. A bridge moves assets between networks; a pool contract holds assets on Mantle so traders can swap between them. The two steps are separate, and the pool will only accept the token contracts it is configured for.

Start by choosing the pool you intend to fund and checking its pair, fee tier or pool type, and deposit rules. A token’s ticker alone is not enough to identify it: the network and contract address determine which asset the pool accepts. For a walkthrough of the transfer step, the mantle bridge guide covers the process in more detail. After the transfer, confirm the tokens appear in your wallet on Mantle before moving to the pool.

Which assets should you bridge to Mantle?

Bridge the exact two token contracts named by the pool, and leave some MNT in your wallet for Mantle transaction fees. A token arriving on Mantle is not automatically the same contract as a token with the same ticker on Ethereum or another network. The pool reads contract addresses, not labels.

Check the pool’s supported assets and its interface before bridging. If you bridge a different token representation, you may need a separate swap to get the required asset. That extra trade adds a transaction and can change how much of each pool token you have. Also check that your wallet is set to Mantle and that the receiving address is the one you plan to use for the deposit.

How do you add the bridged tokens to a pool?

Once both balances are on Mantle, connect your wallet to the pool interface and open its add-liquidity screen. The interface reads the pool’s rules and calculates the deposit amounts. In a two-asset pool, it usually asks for both tokens in a value ratio set by the pool’s current reserves. If the amounts you enter do not match, the interface may use only part of one balance or require you to adjust the amounts.

For ERC-20 tokens, the pool contract cannot move funds from your wallet until you approve a spending allowance. The interface may request one approval per token. Approving grants permission up to the stated amount; it does not itself deposit funds. After approvals confirm, review the proposed amounts and submit the liquidity deposit. The pool contract transfers the tokens and records your share, commonly through a receipt token or a position shown in the interface.

The sequence is easiest to track as three separate checks:

• Confirm the pool’s two token contracts and deposit rules.
• Bridge those tokens to your Mantle wallet and keep MNT for fees.
• Approve each token, then submit the pool deposit and verify the resulting position.

What does providing liquidity change?

Your deposit gives the pool reserves that traders can draw on. In return, your share may earn part of the trading fees, according to that pool’s rules. The pool’s reserves shift as trades happen, so the value and mix of your share can move relative to simply holding the same tokens in your wallet. This difference is often called impermanent loss; it can become a realized loss when you withdraw, and fees may or may not offset it.

Think of the pool as a shared stockroom: your deposit adds inventory, traders take one item and leave another, and your claim tracks a portion of what remains. The analogy stops there, because token prices and the pool’s formula determine the changing value of that claim.

Before depositing, verify the network, token addresses, amounts, and allowance in the wallet prompt. A small initial deposit can help confirm that the route and pool behave as expected. The practical rule is simple: bridge for the pool you have chosen, not for a ticker you assume is interchangeable, and treat the pool position as exposure to changing reserves rather than a fixed balance.