#dusk $DUSK @Dusk

I keep catching myself making the same mistake with @Dusk: assuming a transfer becomes “mine” the moment it becomes valid.

The Phoenix → XSC flow made me rethink that.
If Phoenix already has the shielded DUSK ready, the receiving wallet satisfies the XSC holder condition, and DuskVM has accepted the zero-knowledge proof, my instinct is still: okay, ownership is done.

But that skips an important distinction.
DuskVM accepting the proof means the XSC condition has been satisfied. The transfer has cleared that verification step.
It does not mean DuskDS has already made the resulting ownership state deterministic and final on Dusk L1.

So there’s this strange sequence:
Phoenix payment ready.
Receiver qualifies.
Proof accepted.

Ownership still waiting for finality.
I was treating DuskVM like the last door. It isn’t.
And honestly, I find that more interesting than calling the transaction “pending.”
The cryptographic question can already be answered while the ledger-state question is still unresolved.

That makes me think the important unit here isn't simply the transaction.
It’s the state transition.
For cross-layer assets, “valid,” “accepted,” and “final” can describe three different moments.
So when a wallet or exchange says “this is mine,” which moment should actually count when the condition is proven, or only when DuskDS makes the ownership state final?

@Dusk #dusk $DUSK

When is ownership truly final on Dusk?