Recently, some people have been paying attention to the developments of the Dusk project, but what’s truly worth watching isn’t just slogans and promises, but rather how far the "engineering progress bar" has advanced.

In the latest community discussions, several substantial progress points were mentioned. DuskDS, as the data availability and settlement layer, has been running stably on the mainnet for some time. The Rusk upgrade is the final critical step before the launch of DuskEVM mainnet — the core goal is to completely open up the BLOB transaction processing channel. Simply put, it’s about thoroughly paving the entire pipeline for how batch transactions from L2 are settled onto L1.

There are some very practical technical details worth noting. BLOBs are produced at fixed intervals, roughly every 7 minutes there is an output window. If a batch of EVM transactions cannot fit into one BLOB, the system will automatically allocate them to subsequent BLOBs. According to the current parameters, each window can produce up to 6 BLOBs. You can think of this as the "number of lanes on the settlement highway" — the clearer and more orderly the lanes, the more stable the throughput capacity and cost expectations, which is crucial for high-stability businesses like DeFi and RWA.

What’s even more interesting is its positioning approach. DuskEVM is an EVM-equivalent execution layer, but settlement occurs on a non-EVM privacy-compliant L1 — this isn’t just a superficial change, but a hard integration of the "developer-friendly toolchain" with the "institutional compliance foundation."

The benefits of this approach are quite straightforward. On one hand, wallets and hardware signing devices in the EVM ecosystem can connect more smoothly; on the other hand, for institutions and project teams, it’s even possible to quickly build custom L2s based on DuskDS — choosing permissioned or permissionless modes, setting different sequencer rules, and embedding regulatory requirements directly into parameters instead of just writing them in PPTs.