[Fees] network fee comparison for small orders, actual numbers
Something I keep coming back to: network fee comparison for small orders, actual numbers.
Sent to the right address on the wrong chain years ago. Nothing to be done. That is the lesson I paid for.
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.
Would rather be corrected in public than confident in private.
best — the order this archive was captured in
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.
confirmations are the only status that means anything
confirmations are the only status that means anything
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
Disagree — a quote expiry is normal when a rate is being held. Pressure to decide immediately is a different thing.
Disagree — a quote expiry is normal when a rate is being held.
Agreed — and the hash is the receipt. Nothing else is.
[removed by moderator]
Memo requirements are chain-specific. The chain you are describing does not use one.
Yes — the same token symbol on two chains catches people constantly and it is unrecoverable.
Retitled from an accusation to a description while the confirmations catch up.
Retitled from an accusation to a description while the confirmations catch up.
This is the check that prevents the only genuinely unrecoverable mistake in this thread.
Agreed that quote expiry is ordinary. Rates move and a time-limited quote is not a pressure tactic on its own.
Nearly sent on the wrong network. The token symbol was identical and the address format was the only clue.
quote expiry is a real thing, not a pressure tactic
the memo field matters on the chains that use one
Got a quote with a fifteen-minute expiry and assumed it was a pressure tactic. It was just a held rate.
the supplier cannot reverse it and neither can you
Pasted rather than typed the address, then checked the first and last six characters. Habit now.