[Discussion] we are measuring confirmations at the wrong time and calling it noise
Something I keep coming back to: we are measuring confirmations at the wrong time and calling it noise.
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.
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.
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
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.
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.
Correction: that address format is not the chain you named. Worth checking before anybody follows this.
Confirmations are the count of blocks built on top of the one containing your transaction.
Disagreeing here: that is a network fee at a busy hour and it is not the supplier’s doing.
send a test amount first if the total is large
the memo field matters on the chains that use one
Sent a test amount first on a large order. Cost me a fraction of a percent and I have done it every time since.
Did you send a test amount first?
Is the fee you are describing the network fee or something the supplier added?
escrow arrangements are rare and worth asking about
the supplier cannot reverse it and neither can you
Moved from the vendor board. Payment mechanics live here.
Disagree — a quote expiry is normal when a rate is being held. Pressure to decide immediately is a different thing.
Agreed. Network first, address second, amount third, and in that order every time.
Keep every transaction hash in a note file with the order reference. It has resolved two queries instantly.
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.
Agreed — and the hash is the receipt. Nothing else is.
Yes — the same token symbol on two chains catches people constantly and it is unrecoverable.
network and address, checked twice, before anything else
- 1send a test amount first if the total is large8 comments in this branch · started by u/sigrid_kaufmann