#dusk $DUSK @Dusk a Zedger transfer can be sent without becoming final for the receiver — and that’s exactly why CLAIM exists.
In Dusk’s Zedger design, SEND doesn’t immediately make a transfer part of the receiver’s accepted balance. The receiver still has to ACCEPT it before the transfer expires.
If that never happens, CLAIM provides the sender a defined way to recover the expired transfer rather than leaving it unresolved indefinitely.
That creates an interesting three-step lifecycle:
SEND initiates → ACCEPT completes → CLAIM handles expiry.
What stands out is that Zedger explicitly accounts for the case where the receiving side simply does nothing. The protocol doesn’t have to assume every initiated transfer will successfully complete.
The unanswered question is more practical: how often does CLAIM actually become necessary under real network activity?
The mechanism is documented. Its real-world usage is the evidence worth watching next.
In Dusk’s Zedger design, SEND doesn’t immediately make a transfer part of the receiver’s accepted balance. The receiver still has to ACCEPT it before the transfer expires.
If that never happens, CLAIM provides the sender a defined way to recover the expired transfer rather than leaving it unresolved indefinitely.
That creates an interesting three-step lifecycle:
SEND initiates → ACCEPT completes → CLAIM handles expiry.
What stands out is that Zedger explicitly accounts for the case where the receiving side simply does nothing. The protocol doesn’t have to assume every initiated transfer will successfully complete.
The unanswered question is more practical: how often does CLAIM actually become necessary under real network activity?
The mechanism is documented. Its real-world usage is the evidence worth watching next.