Documentation/canton-network-docs/SDKsdApp SDKWallet ProvidersView on canton-network-docs ↗
canton-network-docs/SDKsdApp SDKWallet Providers

Integration Overview

This section is for wallet authors who want their wallet to be CIP-103 compatible, so it can interoperate with Canton dApps and be listed in the wallet picker the dApp SDK opens on connect(). Choose one or more of the integration paths below.

​
Choose your integration

How your wallet connectsApproach
Browser extensionBrowser extension: announce with canton:announceProvider, and an optional target for postMessage
Remote (server-side) walletRemote wallet: expose a public CIP-0103 RPC URL
Mobile / QR walletWalletConnect via additionalAdapters

​
What every wallet must provide

Regardless of path, a conforming wallet must:
  • Implement the CIP-0103 request methods (connect, status, listAccounts, getPrimaryAccount, signMessage, prepareExecute, ledgerApi, …).
  • Emit the CIP-0103 events (statusChanged, accountsChanged, txChanged).
  • Remain solely responsible for authorization and signing.
  • Present clear approval UI before signing or executing.
See the CIP-103 specification for the full protocol.

​
Get listed in the SDK

Once your wallet is CIP-0103 compliant, submit a pull request to the appropriate bundled list:
GoalFile
Appear as a Suggested Wallet (install / setup prompt when not yet detected)wallets.json
Appear as a connectable remote wallet by defaultgateways.json
The providerId must match how the wallet appears once available. For dApp-side options, see Wallet discovery.

​
Next steps