Transfers
Prepare exact terms, review fees and follow the original operation to its recorded result.
Step by step
- In Wallets, open a wallet and choose Send funds next to an address. The sender and network are preselected; change them on the left if needed. Reloading keeps the exact source selected.
- Enter the recipient address or choose a saved address. The list contains only addresses on the same network; search covers the current page and Next loads another page. A saved address does not establish ownership or authorize a transfer.
- Optionally choose Save recipient, enter a name and visibility, and review the address. This is a separate address-book action and sends no funds. If its result is unknown, check the saved list before trying again.
- Choose the exact asset, recipient and amount. Request a fee estimate and review the principal separately from the native network fee. Expired quotes must be refreshed before a new preparation.
- Run the available preflight, then explicitly prepare the transfer. If account confirmation is required, it completes before the immutable local operation record and first creation request. Read-only estimates and preflight do not themselves reserve or send money.
- For an ordinary Ethereum transfer, choose Send with a connected wallet or Sign using a file. The page first checks whether this transfer already has a saved wallet handoff. Financial-document and replacement attempts retain their separate file-signing path.
- A saved original operation is continued with the same terms and permanent identifier. After a timeout, read its stored result or explicitly recover it; never create a second transfer to guess whether the first succeeded.
- Open Current tasks or transfer history to return to the original detail page. Included, confirmed and finalized describe recorded chain evidence; payment verification and accounting credit are separate.
- For a Node fee overrun, read the saved actual native fee and evidence. Review and acknowledge only the displayed current check. A timeout requires reading the original transfer state, never guessing a fee or sending another transfer.
- To send from a standalone address, open its address card or finish Connect an external wallet. After control verification, choose Transfer. The exact saved address connection is used without creating a Wallet. Review the same asset, recipient, amount and fee steps.
- For wallet-managed sending, connect a detected extension or configured WalletConnect on the exact sender account and network. Review the terms, tick the acknowledgement and confirm the transfer method with the required platform verification. Then choose Open wallet confirmation once. Only the first saved handoff response permits this call.
- The wallet signs and broadcasts. Check its amount, recipient, asset and fees before confirming. A lost reply, cancellation, account/network change, closed page or reload never offers another send or a file-signing fallback for the same handoff. Read the original transaction hash from wallet history.
- Choose Save original hash after checking the full hash. Once recorded, it cannot change. Reported hash — verification pending is a claim, not transaction or payment evidence. Verify and recover original transaction asks the backend to retrieve and verify the exact saved signed bytes without broadcasting.
- After a lost hash-report response, read the saved handoff or recover the same hash claim; do not replace it. Missing provider lookup remains unknown. Only verified recovery exposes the transaction hash as verified transfer data; use the normal observation action to read its chain result.
- For the file path, download the saved package, sign without broadcasting in a compatible signer, then import the exact signed artifact. The backend verifies it before explicit relay. Bitcoin and TRON continue to use this path.
- After verified signing or wallet recovery, Check on-chain outcome reads the saved hash. Relay the saved artifact is available only for an eligible saved transaction with current relay permission. It sends the original bytes, never a new transfer; an unknown relay result requires reading the original outcome first.
- For a prepared human HD wallet transfer, select an active signer association for this exact address. An already paired device can be selected only when its current registration revision and identity match the confirmed association. The device is not an alternative source, and this screen does not create device pairings or import keys.
- Review the recipient, asset, amount, fee cap and device, then choose Sign with device and send. This execute action may import an available original result and continue sending. If the device has not returned its result, the saved task remains waiting; its original signer cannot be replaced.
- Waiting for device means admitted work has not been delivered. Device received the task means its original command was disclosed, not that signing or payment succeeded. Both states offer only status refresh, without a new account confirmation. Do not create another transfer or change signer after a timeout.
- When Signing result received appears, review the original transfer. With recovery permission, tick the import review and choose Import original device result: it verifies and saves the original artifact without signing again or sending. The original initiator with current create and submit permissions can instead explicitly Continue transfer and send, which may relay the original artifact. Each action retains normal account confirmation and current server checks.
- Task admitted, Task delivered to device and Result received are different saved times. A received result is not a settled transfer or accounting credit. Device registration may later be revoked; recovery still refers to the original task and never grants a new signature.