GOBLIXO
Stop and identify the transfer you actually made
If a deposit is missing, do not start by selecting a recovery tool. Establish the sending network, transaction identifier, asset and receiving address. Then check the transaction in an explorer for that network. Your intended route and the route recorded onchain may be different.
A missing balance is not a diagnosis. The transaction could be pending, the asset might not be displayed, or the recipient might not support that network. A transfer to the wrong address is another case entirely. Keep these possibilities separate until the evidence narrows them down.
Write down the four-part destination
Use a record with four fields: network, token identifier where applicable, recipient address and receiving service. Include a required memo or tag separately. Compare this record with the receiver's current deposit instructions instead of checking only a shortened address.
For a fictional example, an exchange accepts a token on network A, but the sender chooses network B because the address looks familiar. A matching address does not make network B a supported deposit route. A successful transaction on B does not establish that the exchange can credit it.
Ask who controls the receiving account
A self-custody address and an exchange deposit address involve different control. If a provider controls the deposit account, its support team and recovery policy determine what assistance it can offer. Owning an exchange login does not mean you have the private key for its receiving address.
For some unsupported EVM-network transfers to a self-custody account, Phantom documents an access path through another compatible wallet. That is a specific scenario, not a universal recovery method. It does not apply merely because two addresses share a familiar appearance.
Treat key handling as a separate security decision
Phantom's documented access procedure can involve importing a key into another application. Its own warning explains that exposing a key to another app changes the security assumptions. Do not export credentials or connect to a rescue site just because a stranger promises an instant fix.
Follow current instructions reached through the provider's official site. If you do not understand which account a procedure controls, stop and ask official support. This guide deliberately provides an investigation framework rather than a universal key-export tutorial.
Check recovery eligibility before paying anything
Coinbase's recovery guidance describes eligibility checks rather than support for every asset and network. A missing transaction in a recovery interface can reflect incorrect details or an unsupported route. A support answer about one token does not establish eligibility for another transfer.
Gather the actual network, transaction identifier, recipient, token details, time and amount. Ask which exact route is supported, whether any fees apply, and what destination the recovery would use. Do not assume a recovery claim is valid because a site can display your public balance.
Prevent a second mistake during the investigation
Do not resend the whole amount, bridge to an exchange speculatively or fund an address suggested by an unsolicited helper. First reconcile the original transfer. Save the relevant explorer record and keep a private note of your support case and the instructions received.
For future deposits, select the receiver's supported network first, then match the sender to it. A carefully checked test transfer may help, but must satisfy any deposit minimum and memo requirements. Neither a test nor a recognizable logo removes the need to verify the complete route.
Keep a route comparison in your case notes: what the receiver requested, what the sender selected, and what the explorer records. Mark unknown fields as unknown. That small distinction prevents an assumption about the intended network from becoming an unsupported claim about where the tokens actually went. Save the evidence.
