made me look at transaction fees a little differently.
I was reading through Dusk’s transaction flow and found a detail that is easy to miss: gas price can actually influence which transactions get selected first.
EVery transaction sets a gas limit and gas price.The fiNal fee is based on gas actually used not the full limit. Unused gas isn't charged.
What caught my attention is what happens next.
Dusk’s block generator considers transactions from the mempool in descending gas-price order, while still respecting block limits and execution dependencies.
that sounds like a small implementation detail.
I dont think it is.
For regulated applications predictable execution isnt only about privacy or compliance
the underlying fee market also needs to behave in a way developers can reason about.
the open question for me is how this behaves as Dusk usage grows and transaction demand becomes more competitive.
That’s the kind of infrastructure detail I want to understand better.
what's your take??
@Dusk
#dusk $DUSK
I was reading through Dusk’s transaction flow and found a detail that is easy to miss: gas price can actually influence which transactions get selected first.
EVery transaction sets a gas limit and gas price.The fiNal fee is based on gas actually used not the full limit. Unused gas isn't charged.
What caught my attention is what happens next.
Dusk’s block generator considers transactions from the mempool in descending gas-price order, while still respecting block limits and execution dependencies.
that sounds like a small implementation detail.
I dont think it is.
For regulated applications predictable execution isnt only about privacy or compliance
the underlying fee market also needs to behave in a way developers can reason about.
the open question for me is how this behaves as Dusk usage grows and transaction demand becomes more competitive.
That’s the kind of infrastructure detail I want to understand better.
what's your take??
@Dusk
#dusk $DUSK
