PartyLayer

Canton Network's wallet landscape is growing quickly, with multiple institutional and self-custodial wallets each exposing their own connection and signing patterns. For dApp developers this means rebuilding wallet integration repeatedly and maintaining brittle, wallet-specific code. PartyLayer was created to solve this fragmentation: one SDK, one API, every wallet. It builds on the CIP-0103 dApp/wallet interaction standard and focuses purely on the developer-experience layer.

One unified API across all supported Canton wallets — write once, support every wallet - Typed React hooks plus a framework-agnostic core (vanilla JS, extensible to other frameworks) - CIP-0103-compliant connectivity, aligned with the official Canton standard - A conformance test runner to verify wallet implementations against CIP-0103 - Registry-backed wallet verification to protect users from spoofed wallets - Fully open-source and modular — adopt only the packages you need

Canton is built for institutional finance, with privacy and on-ledger control as first-class properties. That makes high-quality, standards-aligned developer tooling essential — institutions need predictable, auditable integration paths. PartyLayer exists to make building on Canton faster and safer by reducing the wallet-integration burden, so teams can focus on their actual product. It is intentionally complementary to the official dApp SDK and the CIP standards rather than a replacement.

- Positioned as Canton's application-layer wallet toolkit — analogous to wagmi + RainbowKit on Ethereum - A single unified API across multiple Canton wallets - Ships a CIP-0103 conformance runner — not just an integration library, but a way to verify wallets meet the standard - Registry-backed wallet verification (registry.partylayer.xyz) for authenticity checks - Modular design: 14 packages under @partylayer/*, so teams adopt only what they need - Open-source, and referenced within the Canton developer community as a complementary building block

Overview of PartyLayer, supported wallets, core features (unified API, React hooks, CIP-0103 conformance runner, registry-backed verification), links to documentation and npm packages, and roadmap.

PartyLayer began as an internal need while building Canton dApps — the team kept rewriting wallet integration for each new wallet. That repeated pain became the core thesis: abstract wallet differences behind one clean API and contribute the result back to the ecosystem as open-source infrastructure. The project tracks the CIP-0103 standard closely.

PartyLayer reduces multi-wallet integration from a per-wallet engineering effort to a single integration. It standardizes how Canton dApps talk to wallets, provides a way to verify wallet conformance to CIP-0103, and helps protect users through registry-backed verification. The project is open-source and has been referenced within the Canton developer community as complementary to other emerging tooling efforts.

Expanded framework support (e.g., Vue) alongside existing React and vanilla-JS packages - A modernized React data layer with improved async state and caching patterns - Helpers for CIP-0104 transaction cost visibility - Reference templates for common Canton dApp patterns (tokenization, settlement flows) - Broader wallet coverage as the Canton wallet ecosystem grows