We are excited to announce an update to the DuskDS devnet, which includes a reset to incorporate the work we’ve been doing in the last month to facilitate DuskEVM to work with DuskDS.
This update focuses on improving blob management, mempool efficiency, and preparing for mainnet rollout, improving overall DuskDS node stability, DuskEVM support and reliability.
Key Features
-
Blob Expiration and Deletion: Introduced blob expiration mechanisms, including deletion of expired blobs after 10 days to optimize storage and performance for non-archive nodes.,
-
Blob Charging: Added gas charging for blobs to ensure fair resource usage.,
-
Blob Configuration and Activation: Implemented configurable blob settings, including activation height for mainnet activation of blobs, as well as a settable expiration date for longer data retention, and blob pricing.,
-
Blob Validation and Verification: Improved blob validation with commit and hash verification for increased integrity of included blobs.,
-
Mempool Improvements:
-
Allowed transactions with higher gas limits to replace older ones at equal price, enabling better transaction prioritization.,
-
Improved handling of sequential nonces in the mempool for more efficient transaction processing. The mempool now prioritizes sequential transactions to be included in the chain faster.
-
Bug Fixes
- Syncing Node Blob Storage: Resolved an issue that prevented syncing nodes from properly storing blobs, improving network synchronization reliability.,
For detailed technical changes, refer to the changelog on GitHub here: https://github.com/dusk-network/rusk/blob/lunare-20250805/rusk/CHANGELOG.md
We’ve been actively experimenting with a DuskEVM testnet on the current devnet for the last two weeks, which have yielded results leading to further stabilization of DuskDS and DuskEVM.
This update to our DuskDS devnet is the first step towards the public rollout of our DuskEVM public testnet.
Stay tuned for more updates!