call_with_limit() in Dusk looks like a small contract-call option, but it changes how execution resources can move between contracts.
When one Dusk smart contract calls another, it does not have to hand over whatever gas happens to remain. With call_with_limit(), the caller can give that specific sub-call its own budget.
That creates a more interesting boundary than it first appears. A Dusk transaction can still have gas available while one downstream contract is no longer allowed to spend any more of it. That feels worth watching as Dusk pushes to bring financial markets onchain with EU-licensed institutions, where composed contract calls need predictable execution boundaries. What I don't know yet is whether this gives Dusk contracts a meaningful way to isolate execution resources, or simply moves out-of-gas risk from the transaction level into caller-defined sub-call limits.
The details worth watching are the limit each call receives, what happens when a callee exhausts only that allocation, and whether the caller can continue with the gas that remains.
A high transaction gas limit tells me how much execution budget exists overall. It tells me less about how safely that budget is partitioned across a chain of contract calls.
More useful is whether bounded sub-calls fail predictably without destabilizing the rest of the execution path.
I'd care more about that resource isolation than about the transaction's headline gas limit.
The question is whether Dusk is creating a real execution boundary between contracts, or just adding another place where a composed transaction can run out of resources.
I am watching how real Dusk contracts set these limits and what happens when a bounded call exhausts its allocation.
#dusk $DUSK @Dusk
When one Dusk smart contract calls another, it does not have to hand over whatever gas happens to remain. With call_with_limit(), the caller can give that specific sub-call its own budget.
That creates a more interesting boundary than it first appears. A Dusk transaction can still have gas available while one downstream contract is no longer allowed to spend any more of it. That feels worth watching as Dusk pushes to bring financial markets onchain with EU-licensed institutions, where composed contract calls need predictable execution boundaries. What I don't know yet is whether this gives Dusk contracts a meaningful way to isolate execution resources, or simply moves out-of-gas risk from the transaction level into caller-defined sub-call limits.
The details worth watching are the limit each call receives, what happens when a callee exhausts only that allocation, and whether the caller can continue with the gas that remains.
A high transaction gas limit tells me how much execution budget exists overall. It tells me less about how safely that budget is partitioned across a chain of contract calls.
More useful is whether bounded sub-calls fail predictably without destabilizing the rest of the execution path.
I'd care more about that resource isolation than about the transaction's headline gas limit.
The question is whether Dusk is creating a real execution boundary between contracts, or just adding another place where a composed transaction can run out of resources.
I am watching how real Dusk contracts set these limits and what happens when a bounded call exhausts its allocation.
#dusk $DUSK @Dusk