Documentation

Account and installation setup An existing Noves account and a fresh Data App installation are separate. Reinstalling with a new database does not delete the account, but the installation must identify its validator and complete its own verification before it can use account services. The Data App

Auth0 configuration Create two Auth0 applications. The browser application signs users in and the M2M indexing application indexes participant history. They must not share credentials. In the examples below, APP_URL is the exact public URL, such as https://data.example.com, and AUDIENCE is t

Keycloak configuration The Noves Data App needs two Keycloak clients: | Client | Type | Use | |---|---|---| | noves-canton-data-app-browser | Public, authorization code with PKCE | Human sign-in | | noves-canton-data-app-m2m-indexing | Confidential, service account | Background participant M2M

Verify authentication Verify the browser and M2M paths separately. A successful browser sign-in does not prove that background indexing can authenticate, and a working M2M token does not authorize human users. M2M indexing Before starting the Noves Data App, request another M2M indexing token a

Docker Compose installation Use these instructions to install the Noves Data App with Docker Compose. The examples attach the app to splice-validator_splice_validator and use participant:5001 and http://validator:5003/api/validator. Set the network, participant address, and scan API URL to m

Container environment variables This reference lists the environment variables exposed by the Helm chart and Docker Compose bundle. Start with the required and important settings. The remaining variables already have defaults or are needed only for optional features. Required and important sett

Helm installation Use this guide to install the Noves Data App on Kubernetes. The examples place the app in the validator namespace and use Auth0, NGINX Ingress, and Canton's default Service names. You can change the namespace, participant address, scan API URL, identity provider, and routing sett

Contributor note: installation-secret invariants This note preserves the Helm implementation rules previously embedded in the operator guide. Operator backup and restore policy lives in the Security model; recovery commands live in the [Helm guide]

Migrate from v3.16.1 to v4 of the Noves Data App The Compose migration script requires Docker Compose v2, jq, openssl, and Python 3 (python3) on the host. It checks these tools before upgrading retained image configuration or changing containers. v4 of the Noves Data App upgrades databases f

Noves Data App 4.1.4 release notes (draft) This draft is finalized in the 4.1.4 release bundle commit, which also pins the published image digests. Per-installation credentials In 4.1.4 each installation has its own credential for account features, which the app sets up automatically. Earlier r

Canton Data App 4.2.3 Public parties - Search public parties by name, Featured App name, or party ID fragment without requiring Canton Analytics. - Export a public party as Financial CSV, Activity CSV, or raw JSON without a connected validator or local indexing. Canton Coin transfers include pr

Canton Data App 4.2.4 Account access Existing members can initialize their account when their identity provider omits an email address or display name. Previously saved profile information is preserved. Account permissions still apply. Frontend fixes - Cloud logout completes the identity-pro

Canton Data App 4.2.5 Balances and indexing - Canton Coin balance requests fetch only Canton Coin contracts, reducing work for parties that hold many other contracts. - History activation waits briefly for indexing work and retries when busy. Switching nodes or signing out cancels stale fronten

Canton Data App 4.2.6 Exports - An export interrupted before it finishes, for example while the database is busy, uses bounded retries instead of incorrectly reporting that it exceeded its runtime. If retries are exhausted, the UI tells you to resubmit rather than promising another automatic re

Canton Data App 4.2.7 Database timeouts and diagnostics - Helm exposes database pool size, connection timeout, and command timeout as individual values. The default maximum pool size is 40 and command timeout is 120 seconds. Connection acquisition keeps its 15-second default. Existi

Security model Identities Use two distinct OIDC clients and keep the provisioning administrator separate from both: | Identity | Purpose | Matching Canton user | |---|---|---| | Public browser client and human account | Interactive sign-in. The browser access token is forwarded to the selected

Upgrade to 4.2.7 4.2.7 includes the installation security requirements described below. Upgrade with the full 4.2.7 bundle, either the Docker Compose bundle or the Helm chart. Changing only the image tag is not supported: the bundle carries the configuration the new backend requires. Upgrade direc

Embedded Mode Integration Guide Embed the Noves Data App inside a host application via iframe with full functionality and URL synchronization. --- Table of Contents 1. Overview 2. Prerequisites 3. Data App Configuration 4. [Auth Mode 1:

Encryption at Rest (v4) We recommend encryption at rest for indexed ledger data. The Helm chart and Docker Compose bundle mount storage but do not configure encryption in the underlying storage system. Operators must provide encrypted storage and verify it using evidence from that system. Scope

Noves Data App The Noves Data App is a private block explorer and reporting suite for Canton Network. It lets you browse and filter private ledger

Example prompts Questions canton-mcp answers well. Replace the placeholders with any party on the network — an ANS name, a display name, or a raw party ID all work. Identity & directory 1. Who are the super validators on Canton? 2. Find every party with "<keyword>" in its name. 3. Who is <ans-

<picture> </picture> canton-mcp Ask your AI

Console DApp SDK allows dApps to connect to a Console Wallet account. The Console wallet is a browser extension. All interaction happens inside the dApp. For signing, users will be prompted to sign in their Console Wallet browser extension. Latest version: 3.0.0 Console DApp SDK Console DApp SDK a

MCP server for the Noves Canton API — query Canton Network balances, rewards, classified transactions, prices, identity, and the network directory from any AI agent. Latest version: 0.2.3 <picture>

Chain/transport-agnostic dApp infrastructure - RPC client/server and transports Latest version: 3.4.0 @sigilry/dapp Core package for CIP-103-compliant dApp ↔ wallet extension communication on Canton Network. Provides the t

React hooks and context for @sigilry/dapp Latest version: 3.2.2 @sigilry/react React hooks and context for Canton Network / CIP-0103 wallet connections, built on @sigilry/dapp and React Query. Install yarn add @sigilry/react@^3 @sigilry/dapp@^3 @tanstack/react-query The stable dap

AGENTS.md - canton-contracts Repository role This repository is the reusable OpenZeppelin Daml contracts library for Canton. Keep components independent, auditable, and useful outside any single reference implementation. Research prototypes, local replicas of upstream standards, interoperabilit

Architecture Product boundary canton-contracts contains reusable, on-ledger Daml components and focused integration examples showing how to use them. Broader application implementations, research prototypes, interoperability experiments, and local lookalikes of upstream Canton standards belon

Audits This directory contains security audit reports indexed by package name, package version, source commit, and DAR SHA-256. Each report records its scope, auditor, report date, and finding-resolution status, and applies only to the exact artifacts and scope it identifies.

Contributing Development setup Install DPM and Java 21+. From the repository root, install the Daml SDK declared by multi-package.yaml, then build and validate the workspace: dpm install dpm build --all scripts/check.sh Lint an affected package directly with DP