Deployed a small test contract on DuskEVM this week, not long after @Dusk_Foundation pushed the testnet live, and the gas estimate confused me for a second. I'd budgeted for a normal EIP-1559 execution fee, the kind you get used to on any L2. The actual cost came in higher, and digging into it, I realized it wasn't a pricing bug, it was two separate charges bundled together. #dusk

DuskEVM splits fees into an execution fee and a data-availability fee, since the batcher has to post transaction data to DuskDS separately from the sequencer executing it. I'd read that in the docs earlier and skimmed past it. Paying for it directly made it click in a way the documentation didn't.

What struck me is that "fast inclusion" and "settled" are genuinely different moments here, and the fee structure is basically forcing you to pay for both stages up front, whether you think about them or not. I'd assumed L2 gas was just execution cost with a markup. Wrong assumption, apparently.

Curious whether that DA cost stays proportionally small once real volume shows up, or whether it starts to bite. $DUSK
Which part surprised you most?