The deposit went through, but the contract did not behave the way I expected on the next call. Nothing dramatic. The $DUSK had arrived, the transaction was there, yet the useful part of the interaction was still waiting on another state change.

That made me stop treating the deposit as the event itself.

When DUSK moves into a smart contract, the value is crossing into a different kind of control. It is no longer just sitting in an account waiting for the owner to move it. The contract can make that value available to another piece of logic, hold it against a condition, or leave it untouched until a later transaction changes the state.

The awkward part is that these steps can look almost identical if you only watch the transfer. They aren't. The value moved. The contract state changed, or didn't. Execution consumed gas separately. A retry can cost more even when the underlying DUSK position hasn't changed.

I find that distinction more useful than simply saying DUSK is programmable. The real test is what happens after the deposit when several contract calls start depending on the same state.

That is where I’d keep watching.

@Dusk_Foundation #dusk