@Dusk And $DUSK
While deploying a simple autocontract on the Dusk Foundation network, tagged with #Dusk and linked to @Dusk, what caught my eye was how the gas execution drifted just a bit from the initial estimate—preview showed around 150,000 units, but the confirmation receipt logged 152,300, a minor uptick that didn't trigger any warnings. This happened mid-transaction, with the wallet interface displaying a standard "Executing" spinner that paused for an extra second or two before finalizing, as if recalculating on the fly. It felt like a subtle design nudge toward efficiency, yet in that quiet moment, I reflected on how even small variances like this could add up in repeated runs. Still, it leaves me pondering if $DUSK verifiable flows account for these fluctuations inherently, or if they're just artifacts of the beta setup.
