Documentation

Canton dApp A React and Vite app on the Canton dAppBooster libraries: - @bootnodedev/canton-connect for the wallet session and its hooks; - @bootnodedev/canton-dappbooster for the headless components; - @bootnodedev/canton-theme for the default style sheet, which src/index.css imports once

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 — @bootnodedev/canton-dappbooster The kit's structural seams and the contract every component follows. This is the "why"; the per-component authoring checklist is in CLAUDE.md. Repo-wide rules live in ../CLAUDE.md. This package is an MVP meant to lift

Agent Configuration — canton-dappbooster This file applies only to canton-dappbooster/. For monorepo-wide rules, including the filename casing table and the colocate-then-promote placement rules, see ../CLAUDE.md. Deltas for this package only are below. Scope L2 headless com

@bootnodedev/canton-dappbooster > 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

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.

Agent Configuration — canton-theme This file applies only to canton-theme/. For monorepo-wide rules see ../CLAUDE.md; for the L2/L3 seam this package sits on, ../canton-dappbooster/architecture.md. Deltas for this package only are belo

@bootnodedev/canton-theme > 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 UI

Agent configuration for Canton dAppBooster This file is the canonical monorepo-wide agent configuration. AGENTS.md files are compatibility shims that point here or to a sibling CLAUDE.md. Each subproject can layer its own CLAUDE.md for stack-specific deltas: -

Contributing to Canton dAppBooster Requirements - Node >=24.15.0 - pnpm - Docker - dpm (Daml SDK 3.5.2) Setup git clone git@github.com:BootNodeDev/canton-dappbooster.git cd canton-dappbooster nvm use corepack enable pnpm install Local development Amulet Vesting dApp Intera

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 — Amulet vesting dApp The app's internal seams and the reasoning behind them. What this is and how to run it is in README.md; repo-wide rules live in ../../CLAUDE.md and the cross-component picture in ../../architecture.md

Agent Configuration — example-dapps/amulet-vesting This file applies only to example-dapps/amulet-vesting/. For monorepo-wide rules, including the filename casing table and the colocate-then-promote placement rules it layers on, see ../../CLAUDE.md. The internal seams are in

Daml contract source - BootNodeDev/canton-dappbooster/example-dapps/amulet-vesting/daml/AmuletVesting.daml module AmuletVesting where import Splice.Amulet import Splice.AmuletRules import Splice.Expiry (TimeLock(..), maxTime) import AmuletVesting.Schedule (VestingSchedule, vestedAmount, vali

Daml contract source - BootNodeDev/canton-dappbooster/example-dapps/amulet-vesting/daml/AmuletVesting/Schedule.daml module AmuletVesting.Schedule where import DA.Time (subTime, convertRelTimeToMicroseconds) import DA.List (last, head) -- | How CC accrues over time. Fraction-based so escrow l

Provenance The amulet-vesting Daml package was vendored from the cc-vesting-contracts repository. No DAR is checked in; pnpm build-dar produces it, and the Splice DARs it data-depends on are fetched rather than committed (see README.md). | Field | Value | |-------|-------| | S

dApp Daml The vesting dApp's Daml model: the amulet-vesting package, holding the factory, the proposal, the contract and the residual claim. It escrows real Canton Coin as a Splice LockedAmulet. Its scenarios stay in the repository it was vendored from; see [PROVENANCE.md](https://github.com

Provenance This dApp was vendored, frontend-only, from the vesting-lite branch of the cn-dappbooster monorepo. | Field | Value | |-------|-------| | Source repo | https://github.com/BootNodeDev/cn-dappbooster | | Source branch | feat/vesting-lite | | Source commit | e7e59b2c3e9b7de019418c12a3

Amulet vesting dApp > 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 UI. 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 of the vesting dApp The app's internal seams and the reasoning behind them. What this is and how to run it is in README.md; repo-wide rules live in ../../CLAUDE.md and the cross-component picture in ../../architecture.md.

Agent Configuration — example-dapps/token-vesting This file applies only to example-dapps/token-vesting/. For monorepo-wide rules, including the filename casing table and the colocate-then-promote placement rules it layers on, see ../../CLAUDE.md. The internal seams are in [

Provenance This dApp started as a copy of example-dapps/amulet-vesting, moved off Canton Coin onto a canton-token-forge instrument by the #157 epic. Its two Daml packages are binaries; vendor/PROVENANCE.md records where each comes from. The rest of this file is the Amul

Token vesting dApp > 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 UI. The i

Canton dAppBooster ![GitHub branch status](https://img.shields.io/github/checks-status/bootnodedev/canton-d

Vendored Canton Admin API Protos This directory contains a copy of selected Canton participant admin API protos used by @c7-digital/admin. Source Upstream: https://github.com/digital-asset/canton Pinned commit: df0ed749f (2026-04-22) Source path: community/admin-api/src/main/protobuf/com/d

@c7-digital/admin TypeScript client for the Canton participant admin gRPC API. This package wraps a small, read-only subset of the Canton admin API: | Service | RPC | Purpose | |---|---|---| | ParticipantStatusService | ParticipantStatus | Health + version | | TrafficControlService | Tr

AGENTS.md Guidance for AI coding agents (Cursor, Claude Code, Codex, etc.) in the **c7_ledger** monorepo. Project overview TypeScript clients for Canton Network services, published to npm under @c7-digital/*: | Package | Path | Role | |---------|------|------| | @c7-digital/ledger | ledger

ledger/ — agent notes @c7-digital/ledger: type-safe Canton JSON Ledger API v2 client. Layout src/ ledger.ts Ledger class — submit, query, ACS streams, missing-package recovery client.ts TypedHttpClient websocket.ts ACS / updates / completions streams error.ts LedgerApiError, readE

Ledger Build A standalone, repeatable build system for generating TypeScript types from OpenAPI and AsyncAPI specifications with value.proto branding. Features - One target spec: specs/ holds the JSON Ledger API spec pair of one Canton line (see the [supported versions table](../README.md