The official Dusk protocol node client and smart contract platform for the privacy-focused blockchain.
Rusk is the official node client and smart contract platform for the Dusk blockchain. It implements Dusk's succinct attestation consensus and a privacy-preserving virtual machine, serving as foundational software for running nodes, executing smart contracts, and interacting with the Dusk network.
Blockchain developers and node operators building or interacting with the Dusk network, particularly those focused on privacy-preserving smart contracts and decentralized applications requiring zero-knowledge proofs.
Developers choose Rusk for its modular, performant, and secure reference implementation of the Dusk protocol, which emphasizes privacy, scalability, and developer accessibility through comprehensive tooling like a CLI wallet, JavaScript SDK, and integrated zero-knowledge proving services.
The reference Dusk platform implementation and tools
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The codebase is split into independent crates like consensus, VM, and wallet-core, enabling focused development and customization as shown in the repo overview table.
Includes a zero-knowledge prover service and privacy-preserving virtual machine (Dusk-VM), core to Dusk's protocol for confidential smart contracts and transactions.
Offers a CLI wallet, JavaScript SDK (w3sper.js), and data drivers for encoding/decoding, reducing barriers for web integration and asset management.
Provides Docker files for ephemeral and persistent nodes, simplifying setup and scalability in containerized environments, as detailed in the Docker support section.
Requires Rust nightly toolchain, specific GCC/Clang versions, and Deno, with multiple make commands for keys and state generation, creating a steep entry barrier.
Tied to the Dusk blockchain, it lacks the broad developer tools, documentation, and community support of mainstream platforms like Ethereum.
Zero-knowledge proof generation and verification are computationally intensive, potentially demanding high hardware resources and slowing transaction throughput.