Setting up and verifying a mining payout wallet
Confirm the destination, protect recovery information and reconcile the first payout before scaling up.
ASIC.tools · Reviewed

Separate receiving from spending
A receiving address identifies a destination; private keys or recovery secrets authorize spending. A pool needs the supported receiving details, not your wallet recovery phrase. Decide whether the destination is a self-custody wallet or an account held by another service. These choices have different recovery dependencies. Write down who controls access and how the operator will recover it if the everyday device is lost.
Confirm asset and network compatibility
Check the pool’s payout asset and the receiving service’s supported network before entering an address. Similar names and copied symbols do not establish compatibility. Confirm whether the destination requires additional information or a minimum deposit. Obtain the address from the wallet or service itself and verify it again after pasting. Do not let a saved clipboard value replace the destination you intended to use.
Protect the setup
Enable the pool’s available account protections and understand any address lock before activating it. Keep wallet backups offline or otherwise protected according to the wallet’s documented recovery method. A backup that has never been checked may be incomplete. Never send recovery material to pool support, a repair shop or a site promising to validate it. Protect the email account used for recovery as carefully as the pool account.
Test and reconcile a payout
Review the pool threshold, processing schedule and any applicable fee. When practical, verify a small supported payout before accumulating a large balance. Record the transaction identifier and compare the pool deduction with the amount received. An internal pending payout is different from a broadcast transaction, and a broadcast transaction is different from a confirmed deposit. Follow the receiving service’s confirmation rules rather than assuming immediate availability.
Maintain the destination over time
Review the address after wallet migrations, account changes or deposit policy updates. Keep payout records independent of the pool dashboard, which may have a limited history. If funds do not appear, identify whether the issue is scheduling, threshold, transaction status or recipient processing before changing the address again. Do not publish sensitive wallet recovery information in a public support request; the transaction identifier is usually sufficient for initial tracing.


