the confirmations question that gets asked weekly, answered properly
the confirmations question that gets asked weekly, answered properly, which sounds obvious until you try to state the evidence for 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.
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.
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.
If somebody has the same thing measured a different way, post it next to mine and we will see whether they agree.
best — the order this archive was captured in
Rate quotes expire because the underlying rate moves. A short expiry is ordinary; urgency about your decision is a separate signal and should be read separately.
Pasted rather than typed the address, then checked the first and last six characters. Habit now.
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.
Small fix — that is the network fee, not a supplier charge. The distinction matters for the complaint you are making.
Which network, exactly?
Which network, exactly?
Adding the cheap insurance — test amount first on anything large.
Wallet address redacted from the post above. Hashes are fine here; addresses are not.
Agreed. Network first, address second, amount third, and in that order every time.
Careful, that address format belongs to a different chain and sending to it would not end well.
ask which networks they actually accept before you order
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.
fees vary by chain and by hour, not by supplier
A test transaction costs one extra network fee and verifies the address, the network and the recipient’s crediting process before the main amount move
This is the check that prevents the only genuinely unrecoverable mistake in this thread.
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
Correction: that address format is not the chain you named. Worth checking before anybody follows this.
The transaction hash is the canonical receipt: it is public, verifiable by either party, and it is what a support query should quote.
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
Nearly sent on the wrong network. The token symbol was identical and the address format was the only clue.
Escrow is not standard in this space. Wanting it is reasonable; expecting it as default is not.
Confirmation took forty minutes on a busy evening and I had already written half an angry message. Deleted it.
network and address, checked twice, before anything else
Got a quote with a fifteen-minute expiry and assumed it was a pressure tactic. It was just a held rate.
send a test amount first if the total is large
Right, and confirmations are the status. "Sent" means nothing until the chain agrees.
Did you send a test amount first?
Memo requirements are chain-specific. The chain you are describing does not use one.
Push back: an unconfirmed transaction is not a missing payment. Wait for confirmations before escalating.
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
Not convinced. That fee is the network fee at that hour, and it has nothing to do with the supplier.
- 1network and address, checked twice, before anything else9 comments in this branch · started by u/cormac_erdogan