Dusk gets sharp when issuance clears but distribution doesn’t move, even though nothing is missing.
The batch is ready. Numbers line up. Entitlements were signed off days ago. From the issuer’s side, the asset already feels gone. The moment it’s supposed to leave custody and fan out, the execution path pauses on something nobody budgeted time for: whether the recipients still qualify right now, under the posture that applies to this distribution window.
The list hasn’t changed.
The math hasn’t changed.
The proofs have.
That difference isn’t visible until the state tries to advance. The chain doesn’t care that eligibility was checked last week or that the roster came from the same source of truth as every other round. It only cares about what can be attested to at execution. If that doesn’t line up, nothing moves.
I’ve seen this hit in the quietest way possible. No error. No revert. Just a batch that doesn’t settle while everyone is staring at the same block height like it owes them something. Someone asks if the transaction even fired. Someone else is already drafting an update that assumes it did.
It didn’t.
The instinct is always the same. Loosen the gate for a moment. Let the distribution through and fix the paperwork after. Treat eligibility like a checkbox instead of a live boundary. Dusk doesn’t give you that lane. If the credentials gating this asset aren’t current for this action, the state transition simply doesn’t qualify.
What makes it awkward is the asymmetry. The issuer can prove the issuance is correct. The ledger is fine. Other activity keeps closing. Only this path stays open, waiting on attestations that everyone assumed were background work.
So the scramble starts where nobody wants it.
Which recipients drifted.
Which proofs need refreshing.
Whether the cutoff was too tight or the workflow too optimistic.
Nothing is technically wrong, but the schedule is.
Dusk treats distribution like execution, not ceremony. If the entitlement logic and the credential cycle aren’t aligned, the chain doesn’t stretch time to make them feel aligned. It just waits.
The tokens don’t go anywhere.
The batch stays “ready.”
And everyone learns, again, that readiness isn’t the same thing as eligibility when the clock actually matters. #Dusk
