@Dusk You know how every time you interact with any decentralised app on @Dusk , you have to go through the exact same initial choke point?

DUSK Contract is the only entry point for all non-coinbase state transitions on the network. The protocol separates the native asset layer from the generalised compute layer but they have the same exact state space.

This is why: The only asset that can compensate the network for computational gas is $DUSK . This rule means that each standard transaction must first call the DUSK Contract to perform fee logic before routing execution to a destination smart contract.

Do you think this unified state model will be able to handle heavy smart contract congestion? #dusk $DUSK @Dusk