Kept coming back to the Rusk repo this evening, and the quiet consistency of the v1.7 work is what actually landed.@Dusk_Foundation
Rusk is the main reference client for Dusk, written in Rust. It sits at around 204 stars right now. The public 1.7.0 and 1.7.1 releases from June tightened archive storage, improved consensus handling, and strengthened Phoenix support.
The codebase includes the core modules: consensus, DuskVM, the prover service, recovery tools, and wallet-core. Regular commits are still landing, and multi-node testing infrastructure continues to expand.
That part is real and practical. The node work is moving forward without much noise.
What kept nagging after I closed the tab is the gap between the steady engineering and the wider conversation. The reference client keeps receiving focused updates. Yet most of the attention still sits on the higher-level products and announcements built on top of it.
The people actually running nodes, checking the archive improvements, or testing the multi-node setups remain a smaller group than the overall narrative suggests.
Still wondering how long that split stays in place — solid client work continuing quietly while the louder discussion stays fixed on the layers above it.
#dusk $DUSK
Rusk is the main reference client for Dusk, written in Rust. It sits at around 204 stars right now. The public 1.7.0 and 1.7.1 releases from June tightened archive storage, improved consensus handling, and strengthened Phoenix support.
The codebase includes the core modules: consensus, DuskVM, the prover service, recovery tools, and wallet-core. Regular commits are still landing, and multi-node testing infrastructure continues to expand.
That part is real and practical. The node work is moving forward without much noise.
What kept nagging after I closed the tab is the gap between the steady engineering and the wider conversation. The reference client keeps receiving focused updates. Yet most of the attention still sits on the higher-level products and announcements built on top of it.
The people actually running nodes, checking the archive improvements, or testing the multi-node setups remain a smaller group than the overall narrative suggests.
Still wondering how long that split stays in place — solid client work continuing quietly while the louder discussion stays fixed on the layers above it.
#dusk $DUSK