Proposal: Canton Token Standard Local Utility & Test Harness

Development Fund Proposal Submission

Proposal file: proposals-canton-token-standard-local-utility.md

Summary

Open-source local utility and test harness for Canton Token Standard development - including Daml fixture models, deterministic token scenarios, a Java/Spring Boot local utility service, a TypeScript CLI, Docker-based local setup, GitHub Actions support, documentation, and reference examples.

The project fills a developer experience gap for Canton application teams, wallet builders, SDK contributors, QA engineers, DevRel teams, and hackathon builders that need to test token workflows locally and in CI without depending on DevNet/TestNet Utility infrastructure for every development cycle.

For avoidance of doubt, the example below describes a local-only development profile rather than the production Utility Registry workflow.

The intended local developer experience is expected to be similar to the following illustrative flow:

docker compose up -d
ctsu create-instrument --symbol tUSD
ctsu mint --party Alice --symbol tUSD --amount 1000
ctsu transfer --from Alice --to Bob --symbol tUSD --amount 100
ctsu holdings --party Bob --symbol tUSD

For CI and smoke tests, the same flow would also support automation-oriented helpers such as:

ctsu assert-balance --party Bob --symbol tUSD --amount 100
ctsu reset

These commands are illustrative examples of the intended local developer ergonomics, not a finalized CLI contract. Exact command names, argument shapes, and supported local workflow boundaries will be finalized during Milestone 1 as part of the architecture, scope, and compatibility work.

Checklist

• [x] Proposal file added under /proposals/
• [x] Milestones and acceptance criteria included
• [x] Timeline included
• [x] Funding breakdown included in the proposal file
• [x] Alignment with Canton priorities and Token Standard adoption described
• [x] Non-overlap with SDKs, wallets, LocalNet managers, production registries, indexers, and rewards tooling explicitly described
• [x] Required access and dependencies described
• [x] Risks, mitigations, sustainability, and maintenance plan included

Notes for Reviewers

No core repo changes required - the project is a standalone open-source developer utility and test harness intended to run alongside local Canton development environments and CI pipelines.

Not a new SDK - the project does not compete with existing or proposed SDKs; it provides a reusable local token workflow target that SDKs, applications, wallet integrations, and QA suites can test against.

Not a production registry replacement - the first version is scoped to local development, deterministic fixtures, local registry-like development APIs, documented limitations, and CI validation workflows.

Not a LocalNet manager - the project does not attempt to manage the full Canton lifecycle; ctsu up is scoped to starting the utility's local Docker Compose profile and documented dependencies.

Developer workflow focus - the intended flow is to let teams create local test instruments, mint balances, execute transfers, reset fixture state, and assert expected token outcomes in a repeatable way.

Multi-stack by design - the core utility service is planned around Java/Spring Boot and Daml fixtures, with a TypeScript CLI and reference examples to make the tool easy to adopt by application developers.

Forward-looking delivery - the proposal does not request retroactive funding. The initial architecture, local skeleton, and first golden-path prototype are included in the milestone plan.

Ecosystem utility - the output is intended to support application developers, wallet teams, SDK maintainers, DevRel workflows, test automation, and teams building token-based applications on Canton.