You can prepare an ETH or token transfer in MyEtherWallet (MEW) and sign it with your BitBox02 Multi. Before approving, check the recipient's accepted network and verify the transaction details on the device. These steps cover ordinary transfers in MEW's legacy web interface.
The device can display readable details for native transfers and tokens it recognizes. Some tokens or contract interactions cannot be fully interpreted on its screen. If you cannot verify what you are authorizing, stop rather than relying only on the browser summary.
Before you send
- Open the intended account using Connect your BitBox02 to MyEtherWallet (MEW). Keep the BitBox02 connected and unlocked.
- Confirm the recipient's full address and the exact asset and network they accept. For an exchange deposit, check that exchange's deposit instructions, including supported network and minimum amount. An address beginning with
0xdoes not tell you which network the recipient accepts. - Check that MEW is showing the intended sending account and network.
Network fees require the network's native currency
For these ordinary transfers, keep enough of the network’s native currency in the same sending account to pay the fee, even when sending a token. On Ethereum, fees are paid in ETH; on BNB Smart Chain, in BNB; on Polygon PoS, in POL. A token balance or a native-currency balance on another network cannot pay this fee.
This procedure does not cover swaps, bridges, staking, custom transaction data, or token-spending approvals. If the recipient requires a memo or another input not covered here, resolve that requirement before proceeding.
Prepare and authorize the transfer
The browser collects the transaction details; the BitBox02 is where you review and authorize the signature. Approval can lead directly to broadcast, so complete your checks before confirming on the device.
Stop if the device cannot show enough information
A token can appear in MEW while the BitBox02 displays Unknown token or Unknown amount. Adding the token to MEW does not teach the device its identity or decimals. Reject the transaction and seek a verified way to review that asset before proceeding. A small test does not make an unverified signature safe.
The screenshots show the English MEW interface. Their addresses, assets, balances and fee amounts are examples; use your own verified transaction details.
1. Open the send form
Select Send in MEW's left-hand navigation. The form contains Token, Amount, a recipient-address field, and Transaction Fee.
2. Select the network and asset
Check the Network panel at the upper right of the desktop layout. Open the Token dropdown using the downward arrow at the right of the field. The network selected in Network determines the assets in this list. With Ethereum selected, you can choose native ETH or the listed ERC-20 tokens on Ethereum.
To use another network, select the button with the current network name in Network and choose the intended network, following Switch EVM networks in MyEtherWallet with your BitBox02 if needed. Wait for the network and balances to update, then reopen Token. It now shows assets on that selected network; choosing the same token name on another network does not move your earlier balance there. Select the intended asset and check that its balance belongs to the sending account. If a token's name or symbol could be ambiguous, verify its contract on this network before choosing it.
3. Enter the amount
Enter the amount in Amount and check the selected asset's unit. When sending the native coin, allow for the fee as well as the transfer amount. For a new destination, consider a small transfer first if the recipient's minimums and the fees make that practical.
4. Enter and check the recipient
Paste the recipient's full address into To Address. Compare the entire value after pasting with the address obtained from the recipient's verified instructions. Do not use a token contract as the recipient of an ordinary payment, and do not infer the correct network from the address format.
5. Choose and review the network fee
Wait for Transaction Fee to load, then check the fee amount and the network's native-currency unit. Select the fee field beneath Transaction Fee, which shows an estimated price, time and downward arrow. MEW opens Select transaction fee with Normal priority, Higher priority and Highest priority.
Choose an available priority whose fee you accept. A higher priority requires more of the native currency; options can be unavailable if the account lacks enough of it. MEW closes the chooser and updates the selected fee in the send form. Check that fee before continuing. The times shown are estimates, not guaranteed confirmation times. Leave the advanced gas-limit and data fields unchanged for this ordinary-transfer procedure.
6. Review the transaction in MEW
Select Next to open Transaction Confirmation. Check the recipient, asset, amount, TRANSACTION FEE and TOTAL against your intended transfer.
Select the Transaction details row beneath the summary to expand it. Check Network, the complete From address and Sending. The sending address must match your intended account. For a native-coin transfer, also compare the complete To address with the recipient’s verified instructions. For a token transfer, the expanded section can instead show Via Contract Address: compare that with the verified token contract on this network, and check the payment recipient in the summary above. The contract is not the recipient’s receiving address. If anything differs, select Cancel and correct the form before continuing.
7. Request signing on the BitBox02
Once the browser details are correct, select Confirm & Send in the confirmation window. MEW sends the transaction to your BitBox02 for review and signing on the selected network. For an Ethereum transfer, the device asks you to review the Ethereum transaction. This is a signing request, not proof that the transaction has already been submitted to the blockchain; complete the device checks in the next steps.
8. Review every device prompt
Read the network information when shown, the complete recipient address, the asset and amount, and the fee. Follow the device prompts to view all details. If a token-contract address is shown, compare it with the verified contract for the intended asset on that network. Reject the transaction if any detail differs, if the token or amount is unknown, or if you cannot interpret the requested action. Do not approve unexplained raw contract data or an unfamiliar network warning.
9. Approve only the verified transfer
If you can verify all required details and they match your intention, confirm on the BitBox02 using its prompts. The device signs the transaction, and MEW can then broadcast it without another separate browser approval. Once you approve, do not assume that closing the tab will cancel the transfer.
10. Track the actual transaction
MEW may show Transaction initiated with a View Progress link. Open that link to view the transaction on the selected network's explorer and keep the transaction hash. Check the explorer's status rather than treating the browser message or device signature as proof of completed payment.
Confirm the result before another attempt
A signature authorizes a transaction. Broadcast submits it to the network. A pending transaction has not completed, and successful execution must be checked on the actual network's explorer. Verify the destination and amount; for a token, check the token-transfer record. An exchange can require additional confirmations before crediting the deposit.
If the transaction failed on the blockchain, the intended transfer did not complete, but a network fee may still have been charged. If it remains pending, do not create another ordinary transfer to solve the delay: that can cause a duplicate payment. Pending replacement or cancellation needs a separate procedure for that transaction.
If MEW reports an error after device approval, use the transaction hash, where available, to check whether submission succeeded. If there is no hash or the status is uncertain, resolve that uncertainty before retrying.
If you cannot complete the transfer
If Next is unavailable, check the recipient field, amount, available asset balance, and native fee balance in the selected account and network. If a known received token is absent, use Find funds sent on another EVM network with MyEtherWallet and your BitBox02 to establish its identity and display first.
For an unknown device display, signing error, or uncertain submission, contact BitBox Support with the failed step, non-sensitive error, network, asset, known firmware version, and transaction hash if one exists. For exchange crediting, contact the recipient exchange with its deposit record. Never share recovery words, passwords, passphrases, private keys, or wallet backups, and never reset or restore the device to retry a payment.