Summary

• MigratorV2 is available at: https://migratebit.mantle.xyz/
• MigratorV2 features and request handling policies are authorized by MIP-27.
• It may take up to 24 hours between your request and migration ($MNT to your wallet).
• While your request is pending you retain full control of your $BIT, and you can revoke the request, modify the request, or move your $BIT at any time.

Steps for using the official UI (recommended)

Request Migration

1. Go to https://migratebit.mantle.xyz/
2. Connect your wallet holding $BIT
3. Input the quantity of $BIT you request to migrate (recommended: MAX / Available Balance)
4. Click Request
5. Confirm in your wallet.   Note: For additional security you can check the following details: (Interaction contract: 0x1A4b46696b2bB4794Eb3D4c26f1c55F9170fa4C5; Method Id: 0x095ea7b3; Spender address: (MigratorV2) 0x95cE6D5D5FD2063Fd9a10f7f8f81F9e3193Ca53F)*
6. It may take up to 24 hours to review and approve the migration request. Some requests will not be approved in line with the MIP-27 policy.

View Status of your Request

1. Click Account
2. Go to MigratorV2 tab
   1. "Amount": is the quantity of $BIT you have requested to Migrate
   2. "Transaction 1": is your Request txid
   3. "Transaction 2": is the txid of a successful Migration
   4. "Status":
      1. Will show "pending" while the request is being reviewed
      2. Will show "cancelled by user" if you cancelled or modified your request. Upon modification, a new request record will be shown.

Steps for using Etherscan (advanced users)

Request Migration Note: this is the same process as approving allowance to your $BIT

1. Go to https://etherscan.io/token/0x1a4b46696b2bb4794eb3d4c26f1c55f9170fa4c5#writeContract
2. Connect your wallet holding $BIT
3. Go to 2. Approve (0x095ea7b3)
4. Fill in:
   1. Spender address: 0x95cE6D5D5FD2063Fd9a10f7f8f81F9e3193Ca53F
   2. Amount: the amount of $BIT you request to migrate
5. Click Write
6. It may take up to 24 hours to review and approve the migration request. Some requests will not be approved in line with the MIP-27 policy.

View Status of your Request See previous section

Key Features

Two-step process

• Step 1: Users (holders of $BIT) make a Request via the [BIT.Approve()](https://etherscan.io/token/0x1a4b46696b2bb4794eb3d4c26f1c55f9170fa4c5#writeContract) function
• Step 2: Another Role reviews the requests and approves the migration - via [Migratorv2.approveMigrationRequest()](https://etherscan.io/address/0x95cE6D5D5FD2063Fd9a10f7f8f81F9e3193Ca53F#writeContract) function.
• For MigratorV1, both steps were completed by the user. For MigratorV2 there is a separation of roles to enforce the MIP-27 policy. As it will take time to review Step 2, end-to-end migration may take up to 24 hours to complete.

Users retain control of their $BIT while requests are pending

• "Step 1: Request" does not transfer $BIT. The $BIT will remain in the user's wallet under their control. Users can revoke the request, modify the amount (considered a new request) or move the $BIT at any time.
• "Step 2: Migrate" is handled by a smart contract. The MigratorV2 contract will receive $BIT from the user's wallet and the same quantity of $MNT to the user's wallet. Both legs will either execute successfully or both will fail. The reviewer / approver does not hold user $BIT at any time.

Policy against partial migration

• If the amount of $BIT in the user wallet is not sufficient to cover the requested migration quantity, the migration will not occur.
• We recommend users do not move their $BIT while the Request is pending.