Product suitability for #dusk depends on the layer that is created. Here is the product :
- DuskDS for consensus, settlement, data availability, and the Dusk transaction model
- DuskEVM for Solidity applications, EVM devices, and developer workflows compatible with Ethereum
- DuskVM for Rust/WASM contracts executed directly on Dusk L1.
Fortress for identity, credentials, and selective disclosure patterns
- Dusk Connect for wallet detection and account connection in Dusk applications
- Dusk Trade for tokenization product-level asset workflows such as registration, wallet connection, buying, selling, and settlement coordination
$DUSK @Dusk
- DuskDS for consensus, settlement, data availability, and the Dusk transaction model
- DuskEVM for Solidity applications, EVM devices, and developer workflows compatible with Ethereum
- DuskVM for Rust/WASM contracts executed directly on Dusk L1.
Fortress for identity, credentials, and selective disclosure patterns
- Dusk Connect for wallet detection and account connection in Dusk applications
- Dusk Trade for tokenization product-level asset workflows such as registration, wallet connection, buying, selling, and settlement coordination
$DUSK @Dusk