Documentation

Token flows (Canton Token Standard) Exercise token-standard operations on LocalNet via dpm localnet token. Both generations are supported, routed per instrument: CIP-0056 (Final — existing assets such as Canton Coin) for reads and transfers; creating a new instrument uses Token Standard V2 (CIP-

canton-devkit [ ](https:

LocalNet in CI Stand up a disposable Canton LocalNet for integration tests, then tear it down — using canton-devkit's deterministic exit codes and readiness-wait. When to use The user asks to "test against Canton in CI", "add LocalNet to my pipeline", or "run integration tests in GitHub Actions

DAR upload & inspection Deploy and inspect Daml packages on a running LocalNet via dpm localnet dar (or canton-devkit localnet dar). When to use The user asks to "upload my DAR", "deploy the package to LocalNet", "see what packages are installed", or "diff two package versions". Safe wor

Hot-deploy (watch mode) Tighten the edit→build→deploy loop against a running LocalNet using dpm localnet dar watch and dar build-upload. When to use The user asks for "hot reload", "auto-redeploy on change", or "rebuild and upload in one step" while iterating on Daml code. Safe workflow

Inspect contracts & transactions Read live ledger state with dpm localnet contracts and tx (backed by Ledger API v2). These complement — they do not replace — Daml Shell's one-shot lookups. When to use The user asks to "watch contracts", "see transactions for a party", "what does party X se

Canton LocalNet lifecycle Manage a local Canton network using dpm localnet (or canton-devkit localnet standalone). Every command is idempotent and returns deterministic exit codes. When to use The user asks to "spin up Canton locally", "start a LocalNet", "check if the network is healthy",

Token flows (Canton Token Standard) Exercise token-standard operations on LocalNet via dpm localnet token. Both generations are supported, routed per instrument: CIP-0056 (Final — existing assets such as Canton Coin) for reads and transfers; creating a new instrument uses Token Standard V2 (CIP-

Canton DevKit agent skills These six skills teach agents to use an installed dpm localnet or canton-devkit localnet CLI. Installing a skill does not install DevKit, Daml tooling, or Docker. Install The Skills CLI command is npx skills (plura

Deploying the telemetry collector Two scenarios: local testing (your dev machine) and production (a host the released CLI fleet reports to). Same compose stack, different hardening. The stack is three containers: dpm CLI ──HTTPS POST──▶ collector :8080 ──▶ Postgres ◀── Metabase :3000 (

canton-devkit telemetry collector Self-hosted ingestion endpoint for canton-devkit usage telemetry. Accepts the CLI's per-period counter payload over HTTP and stores it in your own Postgres, with Metabase for dashboards and one-click CSV/Excel export. Nothing leaves your host; you own and

Documentation site development Maintainer notes for the canton-devkit documentation website, built with Astro + Starlight. The published site is [https://bitdynamics-ab.github.io/canton-devkit/](https://bitdynamics-ab.github.io/canton-devki

The telemetry collector is the self-hosted ingestion endpoint for canton-devkit usage telemetry. It accepts the CLI's per-period counter payload over HTTP and stores it in your own Postgres, with Metabase for dashboards and one-click CSV/Excel export. Nothing leaves your host; you own and ca

Agent Configuration This project's canonical agent configuration lives in CLAUDE.md. Agents read AGENTS.md natively; load CLAUDE.md as the single source of truth.

Architecture overview for Canton dAppBooster Tech stack | Subproject | Stack | Purpose | | --- | --- | --- | | LocalNet (external: BootNodeDev/canton-barebones) | Node command-line tool over Docker Compose + the official Splice LocalNet bundl

Agent Configuration This project's canonical agent configuration lives in CLAUDE.md. Agents read AGENTS.md natively; load CLAUDE.md as the single source of truth.

Architecture: canton-connect What the package is and how to use it: README.md. This file maps the seams. Two subsystems carry their own chapter: architecture/connection-machine.md for the states and what settles each promise, and [architectur

The connection machine machine/connectionMachine.ts is the source of truth: the states, events, tags and actors are its setup() and config, and every per-state why rides beside its line as a comment. This chapter holds what the file cannot say from inside one state: the shape at a glance, and

The popup close guard guardedConnect.ts wraps sdk.connect() when the SDK's own popup picker is in use. All of it rests on dapp-sdk internals, so this chapter is the why: what the SDK misses, what the guard does, and where it breaks. The bump procedure it justifies is in [../CLAUDE.md](../C

Agent Configuration: canton-connect Applies only to canton-connect/. Repo-wide rules: ../CLAUDE.md. Deltas only. Scope A thin React layer over @canton-network/dapp-sdk's DappSDK, which owns discovery, the picker, the session and the transports. Browser-only, and built to

The hook names follow wagmi, so a developer arriving from it knows which one to reach for. The result shapes do not, and this is where. | wagmi | canton-connect | why | |---|---|---| | connectors: [injected(), walletConnect({ projectId })] | walletConnectProjectId, additionalAdapters: [new Remo

@bootnodedev/canton-connect > Canton dAppBooster is an open-source stack by BootNode for building Canton dApps on your own machine: a local Canton Network stack, wagmi-style hooks, UI components and CIP-0103 wallet support, wired together from the local network up to the

Agent Configuration This project's canonical agent configuration lives in CLAUDE.md. Agents read AGENTS.md natively; load CLAUDE.md as the single source of truth.

Architecture: canton-create create-canton-dappbooster copies an app and the layers it needs into a new folder. The project it leaves installs the Canton dApp kit from npm. The rules for editing it are in CLAUDE.md. A run src/index.tsx parses the flags and renders App with

Agent configuration: canton-create This file applies only to canton-create/, the create-canton-dappbooster package. For monorepo-wide rules see ../CLAUDE.md. For how a run and the scaffold layers fit together, see architecture.md. Every option is a f

Canton dAppBooster installer > Canton dAppBooster is an open-source stack by BootNode for building Canton dApps on your own machine: a local Canton Network stack, wagmi-style hooks, UI components and CIP-0103 wallet support, wired together from the local network up to the

Contract daml/ holds the app's Daml model, and dpm from the Daml SDK 3.5 builds it. daml/daml.yaml pins a tested patch release, and any installed 3.5 release builds the model. | Script | What it does | | --- | --- | | pnpm build-dar | fetches the Splice DARs it depends on, then builds | |

Local network This project also carries a local Canton stack: - @bootnodedev/canton-barebones runs a Splice LocalNet in Docker, with its config in .canton-localnet/; - @canton-network/wallet-gateway-remote is Wallet Gateway, which the dApp connect

Daml contract source - BootNodeDev/canton-dappbooster/canton-create/scaffold/starter/daml/Main.daml module Main where -- A minimal template to prove the loop: build, upload, exercise from the dApp. template Asset with issuer : Party owner : Party name : Text where signatory issuer observer o