Dusk Connect & The New Dusk Wallet

dusk connect

We've taken a major step towards simplifying how developers build dApps on DuskDS.

Until now, users had the Dusk web wallet to interact with the network directly. But it was designed as a standalone web application, not something dApps could integrate with to discover wallets, request accounts, or sign transactions.

Today we're opening two new repositories for developer preview that change this:

  • Dusk Connect - a lightweight SDK that gives dApps a standard way to discover and connect to any compatible wallet on DuskDS.
  • The new Dusk Wallet - a first-party wallet for browser extensions, desktop, and mobile.

Together they provide the missing front-end pieces for DuskDS applications: build contracts with Forge, and use Dusk Connect to communicate with wallets from multiple platforms.

Dusk Connect

Dusk Connect is the standard wallet connection SDK for DuskDS dApps.

It lets applications discover compatible wallets and communicate with them through a shared provider interface. Developers no longer need to build around one specific wallet or invent custom integration code.

The SDK includes:

  • wallet discovery based on the EIP-6963 pattern
  • account access, signing, transactions, and network helpers
  • namespaced RPC methods such as dusk_requestAccounts and dusk_signMessage
  • zero runtime dependencies
  • conformance tests for wallet builders

Repository: github.com/dusk-network/connect

dusk connect ui

The New Dusk Wallet

Alongside Connect, we're also opening the new Dusk Wallet.

This is different from the existing web wallet. The new Dusk Wallet is a first-party wallet for browser extensions, desktop, and mobile, built around Dusk Connect from the start.

That means dApps can talk to it directly: request accounts, ask users to sign, submit transactions, and handle permissions through a familiar wallet flow.

The wallet supports core Dusk flows: public and private transfers, shield/unshield, staking, reward claiming, DRC-20 and DRC-721 asset flows, dApp permissions, and local key storage.

Key material stays local. Extension builds use PBKDF2 and AES-GCM. Native builds use Stronghold with Argon2 for strong security. The wallet also includes auto-lock, failed-unlock backoff, and per-origin permissions.

Repository: github.com/dusk-network/wallet

Why it matters

Forge helps developers build Dusk smart contracts. Dusk Connect helps dApps communicate with wallets. The new Dusk Wallet gives users a first-party wallet that supports that flow.

Together, they make DuskDS dApp development much more practical: write the contract, build the interface, connect a wallet, and let users interact.

Both repositories are open for developer preview. Try them, build against them, and share feedback through GitHub Issues or the Dusk Discord.