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

​

What every wallet must provide

Regardless of path, a conforming wallet must:

• Implement the CIP-103 request methods (connect, status, listAccounts, getPrimaryAccount, signMessage, prepareExecute, ledgerApi, …).
• Emit the CIP-103 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-103 compliant, submit a pull request to the appropriate bundled list: The providerId must match how the wallet appears once available. For dApp-side options, see Wallet discovery.

​

Next steps

• Browser Extension — Announce a provider from an extension.
• CIP-103 Specification — The full protocol your wallet must implement.