unpopular opinion: most of what gets said here about confirmations are guesswork
unpopular opinion: most of what gets said here about confirmations are guesswork. It is the sort of thing everyone half-believes and nobody writes down.
Got a quote with a fifteen-minute expiry and assumed it was a pressure tactic. It was just a held rate.
Sent to the right address on the wrong chain years ago. Nothing to be done. That is the lesson I paid for.
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.
I will update this if the picture changes rather than quietly leaving it up.
best — the order this archive was captured in
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.
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
Escrow is not standard in this space. Wanting it is reasonable; expecting it as default is not.
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
Pasted rather than typed the address, then checked the first and last six characters. Habit now.
Sent a test amount first on a large order. Cost me a fraction of a percent and I have done it every time since.
Wallet address redacted from the post above. Hashes are fine here; addresses are not.
confirmations are the only status that means anything
screenshot the transaction hash, not the wallet balance
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.
network and address, checked twice, before anything else
escrow arrangements are rare and worth asking about
quote expiry is a real thing, not a pressure tactic
Asked which networks KP accepted before ordering and picked the cheapest one at that hour. Saved more than the difference in price.
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.
Network fees are set by chain congestion at the time of sending. They are paid to the network, not to the recipient, and they vary by hour as well as by chain.
Disagree — a quote expiry is normal when a rate is being held. Pressure to decide immediately is a different thing.
fees vary by chain and by hour, not by supplier
Disagree — a quote expiry is normal when a rate is being held.
amara_kuipers is right about confirmations. "Sent" is not a status.
Is the fee you are describing the network fee or something the supplier added?
keep the hash, it is the only receipt that exists
amara_kuipers is right about confirmations.
This is the check that prevents the only genuinely unrecoverable mistake in this thread.
- 1The transaction hash is the canonical receipt: it is public, verifiable by…7 comments in this branch · started by u/enzo_ferrari
- 2Network fees are set by chain congestion at the time of sending. They are…7 comments in this branch · started by u/nora_ramos