Recently, there's an interesting detail. Looking at Dusk's technical progress, the part that ordinary people are most likely to overlook is exactly the most exciting part for the community—this time, the core of the Rusk upgrade focuses on thoroughly integrating BLOB transaction processing. In other words, it’s about paving the way for how batch transactions on L2 are finally settled onto the L1 pipeline.

From a data perspective: BLOBs are produced at fixed intervals, roughly one window every 7 minutes. When a batch of EVM transactions cannot fit into a single BLOB, the system automatically splits it into subsequent windows. According to current parameters, a single window can produce up to 6 BLOBs—you can think of this as the number of lanes on a high-speed settlement highway. The clearer the lanes, the more predictable the throughput and costs, which is especially critical for high-stability businesses like DeFi and RWA.

DuskDS has been running stably on the mainnet for some time now, and its role as a data availability layer + settlement layer has been validated. The real innovation lies in its positioning: it is an EVM-compatible execution layer, but the settlement occurs on a non-EVM privacy-compliant L1—this is not just a superficial change, but a hard integration of the developer-friendly toolchain and the compliance foundation required by institutions.

For developers, access to wallets and hardware signing devices in the EVM ecosystem is smoother. For institutions and project teams, DuskDS allows for quick setup of custom L2s, with optional permissioned/non-permissioned modes, flexible sequencer rules, and regulatory requirements embedded into parameters rather than documented separately—this is the kind of compliant DeFi that everyone desires.