Canton Opens Its Wallet Stack to Developers, Built on the CIP-0103 dApp Standard
A Wallet SDK, a dApp SDK and a Wallet Gateway let wallets, exchanges and institutions connect apps, validators and signing providers through one standard interface.
The Canton Network published what it called a complete wallet stack for developers on 16 June 2026. The release has three parts, a Wallet SDK, a dApp SDK and a Wallet Gateway, and it implements CIP-0103, the dApp Standard that the Canton Foundation approved on 29 January 2026.
The three pieces
According to the Canton blog post:
- Wallet SDK (
@canton-network/wallet-sdk): a TypeScript toolkit for wallets, exchanges and institutions to create parties, prepare and send transactions and run other core wallet operations.
- dApp SDK (
@canton-network/dapp-sdk): a front-end toolkit for connecting to any CIP-0103 compatible app or wallet, with a discovery component and a "Connect Wallet" interface.
- Wallet Gateway: software an institution deploys in its own environment to connect its validator to signing providers through configurable signing drivers.
The code sits in a public GitHub repository of the canton-network organisation, which GitHub lists under the Apache License 2.0. The post names Fireblocks and BitGo only as examples of key management providers a bank might keep using; it does not name wallets that have adopted the stack.
The standard underneath
CIP-0103 was written by Marc Juchli of Digital Asset and Alexey Chyker and Eugene Birski of PixelPlex. It defines a vendor-neutral dApp API so that an application does not have to build its own integration for every wallet, validator and key management setup.
- Any app, any wallet. Wallets implement the API, and any compliant app can talk to any compliant wallet.
- Choice of node and signer. Users can connect through the validator and the signing method they trust, including external signing.
- A small surface. The standard covers ledger reads, ledger writes and message signing, with a common set of error codes.
- Keys stay put. Private keys remain with the signing provider, and the wallet enforces user authorisation against requests from untrusted apps.
The proposal says Canton apps had been tightly coupled to specific network, key management and wallet integrations, forcing developers to rebuild similar patterns again and again.
Context
On Canton, every user's party has to be hosted by a validator, which makes connecting a wallet more involved than on networks where a key pair is enough. The blog post puts it bluntly: "Without a validator hosting your party, you don't exist on the network." The post also says average daily users on the network have more than tripled in the past six months, a figure CantonCap could not check independently.
