Exchanging ETH from a self-custody wallet usually involves five connected steps: choose an available exchange direction, confirm the required network, obtain the deposit address, sign and broadcast the ETH transfer, and monitor both the blockchain transaction and the exchange request. The exchange process is broadly similar for software and hardware wallets. The main difference is where the private key is held and how the outgoing transaction is approved.
This guide covers transfers from wallets you control. It does not cover ETH held in a custodial exchange account, decentralized exchange contracts, bridges between networks, or buying ETH with a bank card. Rates, service fees, network costs, limits, verification requirements, supported networks, and available asset pairs are dynamic and must be checked before creating a request.
A compact knowledge map and three reading routes
The essential nodes are: wallet type → exchange direction → receiving network and address → transaction fee → signature → blockchain status → exchange status → receipt in the destination wallet.
- To understand quickly: read “What changes between wallet types,” then “The exchange mechanism,” and finish with “Checks that prevent common mistakes.” The result is a clear picture of who controls the ETH, where the transaction is signed, and why the address and network must match.
- To prepare for a real exchange: follow “Information to collect before starting,” “Procedure from a software wallet,” “Procedure from a hardware wallet,” and “How to verify the result.” The result is a usable checklist for creating and monitoring a request without assuming that current conditions will remain unchanged.
- To understand the technical side: start with “The exchange mechanism,” open the technical details about transaction signing, and then read the sections on network fees and blockchain verification. The result is an understanding of what the wallet, Ethereum network, and exchange service each do.
What changes between software and hardware wallets
A wallet is an interface for interacting with an Ethereum account. It displays balances, prepares transactions, and uses the account’s key to authorize actions. The ETH itself is recorded on the blockchain rather than stored as a file inside the wallet application or physical device. [1]
In a software wallet, the signing process is handled within a mobile app, browser extension, or desktop program. Its convenience makes it suitable for routine transfers, but the device and wallet interface must be protected from malicious software and phishing pages.
A hardware wallet keeps private keys offline and normally requires transaction approval on the physical device. The companion application may prepare and broadcast the transfer, but the device signs it. This separation reduces exposure of the private key if the connected computer is compromised, although it does not protect against approving an incorrect address or misleading transaction details. [2]
The receiving exchange service does not need your recovery phrase or private key. A legitimate ETH transfer only requires the deposit details supplied for the request and your authorization through the wallet. Anyone who obtains the recovery phrase can control the associated accounts, so it should never be entered into an exchange form, support chat, or unfamiliar website. [2]
The exchange mechanism from start to finish
The basic concept is ETH transfer followed by settlement of the selected exchange direction. First, the service shows the conditions of a currently available direction. After you create a request, it provides the details needed to send ETH. Your wallet constructs a transaction containing the receiving address, amount, fee settings, and other network data. You review and sign it, after which the transaction is broadcast to the relevant blockchain. An Ethereum transaction is a cryptographically signed instruction and must be included in a validated block before it can be treated as completed on-chain. [3]
The service then identifies the incoming transfer according to the request details and applies its current processing and compliance rules. The destination asset is sent only under the conditions shown for that request. Verification requirements may differ by exchange direction and by the results of compliance checks, so they should be reviewed before sending funds rather than assumed from an earlier operation.
Technical view: what the wallet signs
A standard ETH transaction includes a sender, a recipient, a value, a sequential account nonce, fee parameters, and a digital signature. The private key creates the signature that authorizes the transfer; the private key itself is not transmitted to the exchange or published on the blockchain. After submission, the network generates a transaction hash that can be used to follow the transfer through pending, included, and later confirmation states. [3]
Information to collect before starting
Prepare the destination wallet address for the asset you expect to receive. Confirm that you control it and that it supports the asset and network specified in the request. An asset name alone is not enough: ETH and token balances can exist across Ethereum Mainnet and multiple other networks, while an exchange may support only selected routes at a given time. Ethereum documentation distinguishes Mainnet from layer-2 networks and test networks; these environments must not be treated as interchangeable. [4]
Before creating the request, check:
- that the ETH exchange direction is currently available;
- the exact sending network required by the service;
- the asset and network expected at your destination address;
- the displayed exchange amount, service conditions, and applicable limits;
- whether identity or source-of-funds information may be requested;
- how long the request remains valid, if an expiry is shown;
- that enough ETH remains available to pay the wallet’s estimated network fee.
Ethereum network fees are called gas fees. They change with network demand and are separate from any service fee included in the exchange conditions. Wallets usually estimate gas before approval, but the displayed estimate should be reviewed at the moment of sending rather than copied from an old transaction. Gas on Ethereum is paid in ETH. [5]
Procedure from a software wallet
- Create the exchange request. Select ETH as the asset you are sending and choose an available destination asset and direction. Enter the destination details requested by the service.
- Read the request conditions. Check the network, deposit amount, address, fee information, limits, validity period, and possible verification conditions displayed for this specific operation.
- Open the correct ETH account. In the software wallet, switch to the network required by the request. Do not rely only on the familiar appearance of an address.
- Enter the deposit details. Copy the address directly from the active request. Compare the beginning and end of the address after pasting. If the service specifies an exact amount, preserve it unless the request instructions say otherwise.
- Review the wallet’s transaction screen. Confirm the destination address, network, ETH amount, and estimated gas. Make sure the fee will not reduce the outgoing value if your wallet uses a “send maximum” function.
- Sign and broadcast. Approve the transaction only after the details match. Save the transaction hash and the request identifier.
- Monitor both statuses. The wallet or explorer shows the blockchain transfer, while the request page shows the exchange’s processing state. These are related but separate records.
Use the official wallet application or a previously verified bookmark. A copied address can be altered by clipboard malware, and a convincing imitation of a wallet or exchange page may be designed to capture credentials. Ethereum’s security guidance recommends checking transaction details carefully and treating blockchain transfers as irreversible. [1]
Procedure from a hardware wallet
The request is created in the same way, but approval adds a physical verification step:
- Connect or unlock the hardware wallet through its supported companion application.
- Open the Ethereum account that holds the ETH on the required network.
- Prepare the transfer using the deposit address and amount from the active request.
- Review the information shown by the companion application.
- Compare the recipient and amount with the details displayed on the hardware device itself.
- Approve the signature on the physical device, then allow the companion application to broadcast the signed transaction.
- Record the transaction hash and monitor the request without disconnecting in the middle of a firmware or application operation.
The device screen is an important security boundary. If the address shown there differs from the exchange request or computer screen, reject the transaction. Do not approve merely because the companion application labels the action as an ETH transfer. Also avoid entering the hardware wallet’s recovery phrase into the connected computer; routine sending should not require that phrase.
Checks that prevent common mistakes
Network and asset must match
Confirm the sending network in three places: the exchange request, the selected account in the wallet, and the final signing screen. A valid-looking hexadecimal address does not prove that the chosen network is accepted. Sending through an unsupported network may prevent automatic identification or recovery of the deposit.
Separate the exchange amount from gas
The wallet needs enough ETH for both the amount being transferred and the network fee. If the request expects a defined deposit amount, using the entire wallet balance can cause the actual transfer value to differ or can prevent submission. Review the final ETH value rather than only the total deducted from the account.
Treat the deposit address as request-specific
Do not reuse an address from an old request unless the service explicitly confirms that it remains valid for the new operation. Rates, limits, networks, addresses, and verification conditions can change. Create and follow one active request instead of combining instructions from several sessions.
Use a cautious first transfer when appropriate
If the current limits and request structure allow it, a smaller initial operation can help confirm that the wallet, network, and destination details are understood correctly. This does not remove exchange-rate exposure or guarantee recovery from an incorrect transfer. It is simply a way to limit the amount exposed to an operational mistake.
How to verify the transaction and exchange result
After broadcasting, use the transaction hash to check the sender, recipient, transferred value, network, and blockchain status in an appropriate explorer. A pending transaction has not yet been included in a block. An included transaction has an on-chain record, while later confirmations provide stronger assurance that it will remain part of the chain. [3]
A successful blockchain status does not by itself prove that the exchange is complete. It confirms what happened on-chain. The service must still match the deposit to the request, apply its stated conditions, and send the destination asset. Conversely, an exchange page that has not yet updated does not justify sending the same ETH again. First compare the transaction hash, address, amount, and network, then use the service’s stated support procedure if the records do not align.
When the destination transfer appears, verify it independently in the receiving wallet and, where applicable, on the corresponding blockchain explorer. Check the asset, network, receiving address, and confirmed amount. Keep the request identifier and transaction hashes until both sides of the operation are accounted for.
Practical application: preparing one ETH exchange request
Consider a conditional example: a user holds ETH in a hardware wallet and wants to receive another supported asset in a separate wallet. The user first checks whether that exact direction and the required networks are currently offered. They copy the destination address from the receiving wallet, create the request, and compare its ETH deposit instructions with the network selected in the hardware wallet application. The transfer is signed only after the address and amount match on the physical device. The user then follows the ETH transaction hash and waits for the exchange request to progress before checking the outgoing transaction in the destination wallet.
The exchange service supports ETH along with selected other crypto assets, but this does not mean that every pair, network, or direction is available. Current conditions must be checked for the intended operation. Bank-card exchanges between Russian rubles and cryptocurrency are planned rather than an available feature, so they should not be included in the present workflow.
Once the sending wallet, destination address, and required networks are ready, check the currently available ETH exchange directions. Review every condition shown in the request before transferring ETH, especially if the market price is moving: exchange values can change, blockchain transactions are generally irreversible, and rules may differ between countries.