unpopular opinion: most of what gets said here about escrow is guesswork
The title is the argument: unpopular opinion: most of what gets said here about escrow is guesswork. Here is the rest of it.
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.
What is and is not the supplier’s fault, since this board generates unfair complaints.
Not theirs: the network fee, chain congestion, confirmation time, the rate moving between quote and send, and a payment sent on the wrong chain. Theirs: which networks they accept, how quickly they credit a confirmed payment, and whether the address they gave you was correct and communicated clearly.
Keeping those columns separate makes the reports here far more useful. A thread titled "supplier took my payment" that turns out to describe forty minutes of unconfirmed transaction helps nobody and follows people around for years.
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.
Corrections welcome, especially the pedantic ones. Pedantry is how this board earns its reputation.
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.
Some chains require a memo or destination tag to route funds to the right account.
zeynep_zielinski is right about confirmations. "Sent" is not a status.
Do you have the transaction hash?
network and address, checked twice, before anything else
Is the fee you are describing the network fee or something the supplier added?
Do you have the transaction hash?
Adding the cheap insurance — test amount first on anything large.
Adding the cheap insurance — test amount first on anything large.
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
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.
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.
Pasted rather than typed the address, then checked the first and last six characters.
Agreed — and the hash is the receipt. Nothing else is.
How many confirmations does it show?
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
This is the check that prevents the only genuinely unrecoverable mistake in this thread.
[removed by moderator]
ask which networks they actually accept before you order
the memo field matters on the chains that use one
Which networks did they list as accepted?
Yes — gas is the network’s, not the supplier’s, and conflating them produces a lot of unfair complaints.
- 1The transaction hash is the canonical receipt: it is public, verifiable by…10 comments in this branch · started by u/neha_rahimi
- 2Some chains require a memo or destination tag to route funds to the right…8 comments in this branch · started by u/zeynep_zielinski