DUSK makes more sense when I look at the problem first. Financial assets can move onchain, but institutions still need privacy, predictable rules and infrastructure that does not fall apart when usage grows. That is the gap DUSK is trying to work on.

Right now, the most interesting activity is happening around Nocturne. The team recently found performance degradation after deploying more than 10,000 large smart contracts during testing. An early fix reduced the bottleneck by about 80%, but the team is still testing before treating the issue as solved.

I actually like seeing this kind of problem exposed before wider deployment. A network can look fine with a small state, then behave very differently once applications start piling up.
Recent Nocturne work also touched mempool handling, node startup, wallet address handling and low gas limit transactions. The goal is simple: make the network behave better when there is real pressure.

The developer side is still active too. Dusk’s public repositories show updates to its documentation, wallet, DuskEVM genesis setup and Hyperlane integration through July.

Feels quiet lately, but the work is not. I am more interested in how Nocturne performs as state grows than another partnership announcement. @Dusk_Foundation
#dusk
$DUSK