Documentation

PartyLayer Registry Server Minimal production-ready server for serving wallet registry files. Usage Development Install dependencies pnpm install Run in dev mode pnpm dev Or build and run pnpm build pnpm start Production Set environment variables export PORT=

PartyLayer Tokenization example The M3 Tokenization vertical: a single-page dApp that composes the full CIP-0056 (Canton Token Standard) helper surface from @partylayer/react, the UI primitives, and the theme families against a typed demo backend. It is built in-repo (workspace deps) to

Contributing to PartyLayer Thank you for your interest in contributing to PartyLayer! This document provides guidelines and instructions for contributing. Table of Contents - Code of Conduct - Getting Started - Development Setup - [M

PartyLayer Expo connect demo Runs the actual ConnectButton and WalletList from @partylayer/react-native on a device, a simulator, or the web target, against local builds of our packages. It lives OUTSIDE the pnpm workspace (in demos/, which no workspace glob matches) with its own lockfile,

Deploying the demo apps Production deploy procedure for the two demo apps, apps/tokenization and apps/dvp. Both are static Vite builds served by Caddy on the maintainer's DevNet validator host, with /api reverse proxied to the DevNet gateway. This document covers the apps only. The gateway i

Wallet Adapter Contract > Compatibility reference: New wallets must use the generic CIP-0103 paths; > packages/adapters is closed to new wallet packages. Historical starter/copy > examples below apply only to maintaining existing compatibility integrations. > dApp developers should use the [

Use PartyLayer with an AI coding assistant Give your coding assistant the quick start, the plain-text reference and, for existing projects, the migration guide. These describe the same public APIs developers use. AI assi

PartyLayer API Reference References: - Wallet Integration Guide - Signing transactions from dApps - [OpenRPC dApp API spec](https://github.c

PartyLayer architecture Current application entry point Existing React applications install @partylayer/react @tanstack/react-query, configure PartyLayerKit, and render ConnectButton. The kit creates the public PartyLayerClient; its default catalog loads reviewed wallet runtimes through

Canton application authentication Wallet connection grants a dApp access to wallet methods. Application sign-in is a separate server session. Configure an authentication backend to add sign-in to the ready-made ConnectButton; no new wallet adapter or npm package is required. This integration fol

PartyLayer: CIP-0103 alignment and compatibility limits Standard and evidence The Canton Foundation CIP-0103 specification defines the provider request/event contract, synchronous and asynchronous flows, and error seman

CodeQL review of the initial repository baseline Review date: 2026-10-30. The first full default-branch scan reported 52 open alerts after the newly introduced CI action pin was fixed. A PR-only scan does not enumerate the entire default-branch baseline. Scanner severity alone does not establish e

Dependency security and compatibility maintenance Review date: 2026-10-30. Dependency reports, code review, live-wallet acceptance and an independent audit are different evidence. A clean threshold check is not a claim that every dependency or vendor deployment is vulnerability-free. Framework

Dev and Staging: From Zero to a Working Integration This guide is the practical path for a team integrating PartyLayer, from a first look with nothing installed, through local development against a mock wallet, to a real connection on devnet, and finally to staging and production. It consolidates

Devnet run: verifying requestTransfer This is the legacy optional requestTransfer runbook. For current generic wallet paths, test environments and acceptance requirements, start with wallet acceptance. The optional Console wrapper below is not the default native conne

Error Codes Reference References: - Wallet Integration Guide All errors extend PartyLayerError and have a stable code property for programmatic handling and UI messages. Error Codes | Code | Class | Description | UX Message |

Event to lifecycle phase mapping > Published on the docs site as a section of partylayer.xyz/docs/events. The observability deliverable names six lifecycle phases: connect, authorize, prepare, submit, confirm, and error. The shipped SDK doe

Event Specification > Published on the docs site: partylayer.xyz/docs/events. This document defines the event payloads emitted by PartyLayer SDK. Event System Overview PartyLayer uses a typed event system for state changes: client.on('session:

Adapterless CIP-0103 integration: the two generic paths PartyLayer connects dApps to Canton wallets. You do not need a PartyLayer-specific adapter package to be one of those wallets. There are exactly two generic paths, and every CIP-0103 wallet fits one of them. Neither puts any wallet-specific c

Distribution drafts for maintainer review These are drafts, not sent messages or agreed partnerships. Send only after checking the recipient and the actual wallet's network/capability evidence. Do not imply that all wallet operations have passed live acceptance. Wallet documentation proposal >

Developer discovery and adoption roadmap PartyLayer aims to become the default wallet connection kit for Canton application developers. Full CIP-0103 compliance positioning remains; individual wallet/network capabilities and acceptance evidence stay explicit. Search placement and adoption are outc

PartyLayer Metrics & Telemetry This document describes the metrics collection system in PartyLayer SDK, designed to support ecosystem health monitoring and usage reporting. Overview PartyLayer is an enablement layer, not a transaction producer. Our metrics focus on: - Adoption: How many

Upgrade an existing PartyLayer application This guide targets React 3.1.2+, SDK 0.20.1+ and session 1.1.10+. These are the guide's reviewed baselines, not a promise that every future release is compatible. Commit your working application and lockfile before upgrading; use a branch and

Multi-party transaction patterns > Published on the docs site: partylayer.xyz/docs/multi-party-patterns. Multi-party flows on Canton are expressed as on-ledger workflows between parties. A transfer is a contract the receiver acts on; a settlement

Observability on PartyLayer > Published on the docs site: partylayer.xyz/docs/observability. PartyLayer is vendor neutral about telemetry. It defines a small adapter interface, ships one reference implementation, and forwards every event it emits to wha

Open findings Verified defects that are not fixed and not scheduled. Each entry says what reproduces, on what commit it was checked, and what would have to happen to close it. Why this file exists A defect written up only in a report is a defect that gets rediscovered. Two of the entrie

PartyLayer and Canton Topology: Where Your DARs Go When integrating PartyLayer alongside your own DAML templates, a natural point of confusion is where DAR files need to be published: to the wallets' validators, or to a PartyLayer validator that then bridges them to the wallets. Neither is correct

Performance > Published on the docs site: partylayer.xyz/docs/performance. This document is anchored to measurements, not advice. Every number here is reproducible with pnpm gate:size (the bundle scenarios) or the commands noted in each section. Meas

Canton wallet platform roadmap PartyLayer's target is a ready-made Canton wallet experience comparable to RainbowKit's developer and user experience. This is a product target, not a claim of completed feature parity. The default wallet catalog release is the foundation; the remaining milestones be

Privacy-aware reads on Canton > Published on the docs site: partylayer.xyz/docs/privacy-and-reads. On Canton the ledger itself enforces what a party can see. A contract is only visible to the parties that are stakeholders on it, so a wallet kit does