#dusk What happens if you reserve more gas than a DUSK transaction actually uses? The unused part is not simply lost.
When a transaction sets its gas price and gas limit, Dusk also includes a stealth address in the fee data. If execution finishes without consuming all the allocated gas, the remaining value can be returned to that address as a refund.
That detail is easy to miss, but it matters. Users need enough gas allowance to let a contract finish, yet they should not have to treat every unused unit as wasted $DUSK .
The design also fits Dusk’s broader approach of keeping transaction handling precise without making the refund process unnecessarily public.
One question I would still watch in practice is how predictable those refunds feel during more complex contract execution.
For me, this is a small mechanism with a practical message: good transaction design is not only about charging for computation, but also about handling what was never actually used. $DUSK @Dusk
When a transaction sets its gas price and gas limit, Dusk also includes a stealth address in the fee data. If execution finishes without consuming all the allocated gas, the remaining value can be returned to that address as a refund.
That detail is easy to miss, but it matters. Users need enough gas allowance to let a contract finish, yet they should not have to treat every unused unit as wasted $DUSK .
The design also fits Dusk’s broader approach of keeping transaction handling precise without making the refund process unnecessarily public.
One question I would still watch in practice is how predictable those refunds feel during more complex contract execution.
For me, this is a small mechanism with a practical message: good transaction design is not only about charging for computation, but also about handling what was never actually used. $DUSK @Dusk