three years of USDC threads, summarised so you do not have to read them
three years of USDC threads, summarised so you do not have to read them, which sounds obvious until you try to state the evidence for it.
Pasted rather than typed the address, then checked the first and last six characters. Habit now.
The sequence that makes this boring, which is the goal.
Ask which networks are accepted before you order. Pick the one with a sensible fee at that hour. Paste the address rather than typing it and verify the first and last several characters. Check whether the chain requires a memo. Send a test amount if the total is large. Wait for confirmations before treating anything as done. Save the transaction hash with the order reference.
Seven steps, most of them seconds long, and between them they eliminate every failure mode that gets posted on this board.
Sent to the right address on the wrong chain years ago. Nothing to be done. That is the lesson I paid for.
Screenshot none of this. Read the whole thread, including the parts where I am told I am wrong.
best — the order this archive was captured in
Some chains require a memo or destination tag to route funds to the right account. Omitting it on those chains is one of the more common ways payments go astray.
ask which networks they actually accept before you order
ask which networks they actually accept before you order
Adding the cheap insurance — test amount first on anything large.
Asked which networks HJ accepted before ordering and picked the cheapest one at that hour. Saved more than the difference in price.
Confirmations are the count of blocks built on top of the one containing your transaction. Until there are some, the transaction is not settled in any meaningful sense.
This. A test transaction on a large order costs a fraction of the fee and removes the whole class of risk.
Confirmations are the count of blocks built on top of the one containing your transaction.
Agreed — and the hash is the receipt. Nothing else is.
Nearly sent on the wrong network. The token symbol was identical and the address format was the only clue.
Confirmation took forty minutes on a busy evening and I had already written half an angry message. Deleted it.
Moved from the vendor board. Payment mechanics live here.
Correcting myself upthread: it was 7 confirmations, not the number I posted, and it settled fine.
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
Did you send a test amount first?
Memo requirements are chain-specific. The chain you are describing does not use one.
the supplier cannot reverse it and neither can you
confirmations are the only status that means anything
quote expiry is a real thing, not a pressure tactic
quote expiry is a real thing, not a pressure tactic
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
Cosigning on keeping the hash. It is the only receipt in existence and people screenshot their balance instead.
A test transaction costs one extra network fee and verifies the address, the network and the recipient’s crediting process before the main amount moves.
A token symbol identifies an asset, not a network. The same symbol commonly exists on several chains with incompatible address formats, and sending across that boundary is generally unrecoverable.
nobody legitimate needs the payment in the next ten minutes
Right, and confirmations are the status. "Sent" means nothing until the chain agrees.
The one mistake that cannot be undone, and why it keeps happening.
The same token symbol exists on multiple chains. The wallet interface shows you the symbol prominently and the network in small type. Sending on the wrong chain to an address that looks perfectly valid usually means the funds are unrecoverable by either party.
The protection is procedural rather than technical: confirm the network in writing with the recipient before sending, verify the address format matches that network, and send a small test first. None of that requires understanding the chain — it requires treating the network field as the most important thing on the screen, which the interface design does not encourage.
keep the hash, it is the only receipt that exists
Yes — the same token symbol on two chains catches people constantly and it is unrecoverable.
Yes — gas is the network’s, not the supplier’s, and conflating them produces a lot of unfair complaints.
Correction: that address format is not the chain you named. Worth checking before anybody follows this.
send a test amount first if the total is large
the memo field matters on the chains that use one
- 1Some chains require a memo or destination tag to route funds to the right…7 comments in this branch · started by u/reflux_report
- 2The one mistake that cannot be undone, and why it keeps happening. The same…7 comments in this branch · started by u/blunt_coldbox_2024