How to Check a Pending Mantle Token Migration

Check a pending Mantle token migration in the MigratorV2 account view and compare its status with the transaction records; a migration request is not the same as a bridge transfer. The older BIT-to-MNT process began on Ethereum, where users submitted a request to exchange BIT for MNT, while the Mantle bridge moves assets between networks. The distinction matters: a confirmed request can still be under review, and a bridge deposit can be waiting for a separate cross-chain step. For more on that second process, the mantle bridge guide explains how assets move between Ethereum and Mantle.

What does “pending” mean for a Mantle migration?

“Pending” means the migration request has been submitted but has not yet reached a completed or cancelled state in the migrator’s records. In the BIT-to-MNT MigratorV2 flow, the request was reviewed before MNT was sent to the user’s wallet; the interface guide described processing as potentially taking up to 24 hours. Treat that as a stated processing window, not a guarantee that every request will finish within it, especially if you are checking an older request or an interface whose current availability you have not confirmed.

This is different from a transaction that is merely awaiting Ethereum confirmation. A wallet can report that a request transaction was sent, while the migrator’s own record still shows it pending review. Conversely, a transaction can fail before creating a valid request. The useful question is therefore not just “Did I click confirm?” but “Did the request reach the contract, and what does the migration record show now?”

The BIT-to-MNT migration was a token conversion on Ethereum. Bridging is a separate action that transfers an asset between Ethereum and Mantle after it is available on the relevant network. A swap is different again: it trades one token for another at a quoted rate, with fees and possible price impact. These routes can lead to different balances and records, so identify which operation you actually initiated before troubleshooting.

Where can you check the request and its transactions?

Open the migration interface you used, connect the wallet that submitted the request, and look for the account’s MigratorV2 section. Check the request amount, status and transaction identifiers together. The request transaction is evidence that the on-chain submission was recorded; a second transaction identifier, if shown, is the record to inspect for the completed migration. A pending label without a completion transaction means the interface has not recorded the final transfer.

Use the transaction hash to check the Ethereum explorer, making sure the wallet address and network match the original request. Confirm whether the transaction succeeded, failed or remains unconfirmed. If it succeeded, that only establishes that the request transaction was included; it does not by itself prove that MNT has already arrived. Then compare the wallet address in the migration account view with the address whose balance you are checking. A different connected wallet can make a completed transfer look missing.

For a quick review, gather these details before deciding what to do:

• The wallet address that submitted the request.
• The requested BIT amount and the status shown in the migrator.
• The request transaction hash and its Ethereum result.
• Any completion transaction hash and the MNT balance for the same wallet.

If the completion record is present but the balance is not obvious, inspect the wallet’s Ethereum token balance and verify that you are viewing the same address. Token display and token custody are separate: a wallet interface may not show an asset automatically, even when an explorer records the transfer. Do not infer completion from an approval transaction; approving a token gives a contract permission to use it, but approval alone does not submit or finish a migration.

Should you wait, cancel or submit another request?

Wait while the migrator shows pending and the request transaction succeeded, particularly if the stated processing period has not passed. The former MigratorV2 guidance said users retained control of their BIT while a request was pending and could cancel or modify it. But check the current interface and its terms before acting: changing a request may create a new record, and the old record may then show a user cancellation rather than a migration.

Do not submit a second request simply because the first is slow. First check whether the original request remains active and whether the displayed amount reflects any change. Duplicate requests can complicate the record you are trying to follow, while moving the relevant BIT during review can affect whether the original request remains eligible under the process rules. If the interface no longer provides a clear status, use the request transaction and verified contract records to establish what happened before taking another action.

Keep safety checks proportionate but firm: use the migration address obtained from Mantle’s official channels, verify the wallet prompt and contract spender, and never disclose a seed phrase or private key. A pending status is not a reason to approve a new, unrelated transaction from a message or support account.

What should you watch for next?

Watch for a change from pending to a completed or cancelled status, a completion transaction hash, and the expected MNT balance in the same wallet. If the request transaction failed or no request record appears for its hash, investigate that submission rather than waiting for a migration that was never registered. If it remains pending beyond the interface’s stated window, preserve both transaction hashes and the displayed status, then consult current official support channels with those specifics.

The practical takeaway is to treat migration status, Ethereum transaction confirmation and the resulting token balance as three separate checks. That gives a clearer answer than repeatedly refreshing a wallet or assuming that a bridge transfer is involved. The next signal that matters is a verified completion record; until then, the word “pending” describes a request in process, not MNT already delivered.