#dusk $DUSK @Dusk
The other day, I was buying movie tickets when the payment screen froze, so I almost clicked again. Luckily, the confirmation email arrived first. One purchase, and I nearly paid twice.
I thought about that while reading how Dusk handles Moonlight deposits. Dusk uses the transaction ID as an idempotency key, so a scanner can rescan data after a failure without crediting the same transaction twice. What caught my attention was the warning: don’t use the memo for this.
At first, I thought this was simply about preventing double credits. But a memo describes a transaction; the transaction ID identifies the transaction itself. When a system crashes and starts again, that distinction tells it whether it is seeing something new or simply seeing the past again.
That’s when idempotency became more interesting to me. A financial system doesn’t just need to process what happened correctly; it also needs to recognize what has already happened. If failure forces a system to look at the past again, how do you make sure the past doesn’t get counted twice?
$PEPE $MUBARAK
The other day, I was buying movie tickets when the payment screen froze, so I almost clicked again. Luckily, the confirmation email arrived first. One purchase, and I nearly paid twice.
I thought about that while reading how Dusk handles Moonlight deposits. Dusk uses the transaction ID as an idempotency key, so a scanner can rescan data after a failure without crediting the same transaction twice. What caught my attention was the warning: don’t use the memo for this.
At first, I thought this was simply about preventing double credits. But a memo describes a transaction; the transaction ID identifies the transaction itself. When a system crashes and starts again, that distinction tells it whether it is seeing something new or simply seeing the past again.
That’s when idempotency became more interesting to me. A financial system doesn’t just need to process what happened correctly; it also needs to recognize what has already happened. If failure forces a system to look at the past again, how do you make sure the past doesn’t get counted twice?
$PEPE $MUBARAK