Deep Dive
1. Major Rusk Testnet Upgrade (November 2025)
Overview: This upgrade deployed a new Rusk release candidate to the DuskDS (Nocturne) testnet. It fundamentally reshapes the network to serve as both a settlement and data availability (DA) layer, a key step before the public DuskEVM testnet launch.
The update introduced EIP-4844-style blob transactions, creating dedicated, low-cost data lanes for large payloads like rollup data or zero-knowledge proofs. It also rolled out new developer endpoints for finalized events and contract metadata, plus a new data-driver interface to simplify integration for third-party services like explorers and indexers. Performance improvements were made to archive nodes and consensus.
What this means: This is bullish for DUSK because it makes the network more capable and developer-friendly. Builders can now settle transactions and publish data on the same chain, which simplifies architecture and could lower costs. The improved performance and new tools make it easier for projects to build on Dusk, supporting future ecosystem growth.
(Source)
2. Legacy Codebase Deprecation (2025)
Overview: The project has officially archived its legacy repositories, including the reference Golang implementation of the Dusk node (dusk-blockchain). This marks the completion of a transition to a new, Rust-based client architecture for improved security, interoperability, and development.
The dusk-pki repository was also archived. These deprecations are strategic, consolidating development efforts on the modern tech stack that powers the mainnet and upcoming DuskEVM.
What this means: This is neutral to bullish for DUSK. While archiving old code isn't a feature addition, it signals strong developer discipline and a commitment to a more robust, maintainable foundation. It reduces complexity and focuses all resources on the active, future-proof network, which is positive for long-term health and innovation.
(Source)
Conclusion
Dusk's development is aggressively modernizing, deprecating old infrastructure while rolling out significant testnet upgrades that enhance its modular capabilities for real-world assets and private finance. How will the successful activation of these testnet features accelerate the timeline for the DuskEVM mainnet?