Canton Token Standard Local Utility & Test Harness

Development Fund Proposal Submission

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

Summary

This proposal requests funding for Canton Token Standard Local Utility & Test Harness, a focused open-source developer utility for local Token Standard-style workflow testing in Canton applications.

It addresses one repeated workflow gap before teams are ready to depend on DevNet/TestNet Utility infrastructure: local token fixtures, seeded test balances, transfer scenarios, holdings assertions, fixture reset, and CI-ready smoke tests.

The goal is to give application teams, wallet builders, SDK maintainers, QA engineers, DevRel teams, and hackathon builders a deterministic local token workflow target they can reuse instead of rebuilding the same fixture logic in every project.

The intended high-level local developer experience is expected to be similar to:

docker compose up -d
ctsu fixture seed --profile basic-token
ctsu scenario run first-transfer --from Alice --to Bob --symbol tUSD --amount 100
ctsu assert holdings --party Bob --symbol tUSD --amount 100
ctsu fixture 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 funding amounts defined
• [x] Acceptance criteria included
• [x] Alignment with Canton priorities described

Notes for Reviewers

This proposal is intentionally narrow and scoped to avoid overlap with broader SDK, DevKit, CLI, wallet, registry, indexer, auth, verification, and rewards efforts.

It focuses on one repeated workflow gap after local environment setup: deterministic local Token Standard-style development and testing. The deliverable is a reusable harness for fixture seeding, first-transfer scenarios, holdings assertions, fixture reset, CI smoke tests, compatibility documentation, and reference examples.

The main differentiators are:

• focused on local development and integration testing, not production Utility Registry behavior;
• centered on deterministic Token Standard-style fixtures and CI assertions, not general Canton project lifecycle tooling;
• designed as a shared local test target for SDKs, wallets, applications, QA suites, examples, and DevRel workflows;
• useful without changing protocol behavior or requiring privileged MainNet/TestNet/DevNet access for v1 acceptance;
• scoped and priced as a focused public-good developer infrastructure tool.

The proposal also includes a dedicated non-overlap section and supported/deferred compatibility matrix to make clear which parts of the local profile are supported, simulated, or out of scope for the first release.