PartyLayer

Canton wallets

Every wallet in the PartyLayer registry, with how a dApp reaches it, which adapter package drives it, and which capability flags map to which SDK calls.

10 wallets. 5 declare CIP-0103 native support, one declares it is not native, and 4 declare nothing either way.

Where this comes from

This page is generated from registry/v1/stable/registry.json in the PartyLayer repository, on every deploy. It is not a hand-maintained list, so it cannot fall behind the registry it describes: if a wallet is added, its row and its page appear on the next build with nothing written by hand.

Registry sequence 21, channel stable, published 24 June 2026 by PartyLayer. Schema version 1.0.0.

What checking means here, and what it does not. Every entry is validated against a JSON Schema on each build, and a gate asserts that wallets already recorded as CIP-0103 native keep that flag, because losing it silently downgrades detection. The registry carries no cryptographic signature today: the tooling exists in the repository but no signature ships with the published file, so do not read this list as cryptographically attested. Capability flags describe what the PartyLayer adapter supports, which is not the same as what a wallet vendor offers through their own SDK. For that, follow the wallet's own site.

WalletTransportCIP-0103NetworksAdapter package
Console Wallet
Official Console Wallet for Canton Network (browser extension + mobile)
Browser extension, with mobile deep linkNative
evidence · since 2025-11-01
devnet, testnet, mainnet@partylayer/adapter-console
>=0.2.5
5N Loop
5N Loop Wallet for Canton Network
QR or popup, opened by the wallet SDKNot declareddevnet, mainnet@partylayer/adapter-loop
>=0.1.0
Cantor8
Cantor8 Wallet for Canton Network
QR or popup, opened by the wallet SDKNot declareddevnet, mainnet@partylayer/adapter-cantor8
>=0.1.0
Bron
Bron Enterprise Remote Signer for Canton Network
Enterprise API, OAuth2Not declareddevnet, testnet, mainnet@partylayer/adapter-bron
>=0.1.0
Nightly
Nightly Multichain Wallet for Canton Network
Browser extensionNot declareddevnet, testnet, mainnet@partylayer/adapter-nightly
>=0.1.0
Cauri Wallet
Non-custodial passkey-based wallet for Canton Network
Hosted popup, no installNative
evidence · since 2026-08-03
devnet, mainnet@lithiumdigital/cauri-dapp-sdk
>=0.1.0
OneSwap V2 Wallet
Hosted custodial Canton wallet. Approval and submission happen in the OneSwap popup.
Hosted popup, no installNative
evidence · since 2026-08-05
devnet, mainnet@oneswap/wallet-cip0103-adapter
>=0.1.0
Send
Passkey-based Canton wallet. Mainnet only.
Browser extensionNative
evidence · since 2026-04-01
mainnet@partylayer/adapter-send
>=0.3.6
Walley
Popup/remote Canton wallet (CIP-0103), bridged via its official @k2flabs/walley-dapp-sdk ProviderAdapter — no PartyLayer-specific adapter package.
Hosted popup, no installNative
evidence · since 2026-06-13
mainnet, testnet, devnet@k2flabs/walley-dapp-sdk
>=0.8.0
WalletConnect
Connect Canton wallets over WalletConnect (hosted/mobile, e.g. Nightly mobile). Opt-in adapter wrapping @canton-network/dapp-sdk's official WalletConnect adapter.
Mobile, over a relay or deep linkNot nativedevnet, testnet, mainnet@partylayer/adapter-walletconnect
>=0.3.0

Capabilities, and the call each one enables

A flag here is a statement about the PartyLayer adapter for that wallet. Where a flag is false, the corresponding call has no path through that adapter, so decide before you offer the wallet in a picker rather than after a user selects it.

CapabilityCallConsole Wallet5N LoopCantor8BronNightlyCauri WalletOneSwap V2 WalletSendWalleyWalletConnect
Sign messageuseSignMessage()YesYesNoYesYesYesYesYesYesYes
Sign transactionuseSignTransaction()YesNoNoYesNoYesNoNoNoNo
Submit transactionuseSubmitTransaction()YesYesYesNoYesYesYesYesYesYes
Report transaction statussubmit resultYesYesYesNoNoYesNoYesYesNo
Switch networkclient.switchNetwork()NoNoNoNoNoNoNoNoNoNo
Multi-partymulti-party flowsNoNoNoNoNoNoNoNoNoNo

Next