feat: vest a canton-token-forge instrument instead of canton coin

[lmcorbalan]

Summary

Closes #157

Canton Coin tied every write to Splice reference data: AmuletRules, an open mining round and a
wallet-service tap. The dApp now vests a DBT token-forge instrument through one InstrumentConfig
from a CIP-56 registry, which drops the Daml toolchain from the repository and grant creation to a
single wallet approval.

Changes

• Vests a DBT token-forge instrument; Canton Coin vesting is removed, not kept alongside
• Both DARs ship as vendored binaries and the Daml package is gone, so dpm is no longer required
• dev-stack.sh runs the canton-token-forge registry on 3013 and bootstrap seeds the instrument
• The value-moving choices take one InstrumentConfig disclosure, so a grant costs one approval
• A grant reserves only the amount it vests and the rest comes back as change
• The funder can cancel and the receiver can decline a grant that was never accepted
• An in-app faucet taps DBT from the dashboard header
• The deployed origin forwards the registry routes same-origin, replacing the wallet RPC proxy

Deviations

• The branch has never been synced with main and conflicts in 33 files; integrating it is a separate pass
• Reserve only the granted amount once the factory splits its inputs #180 and Let a funder cancel and a receiver decline an unaccepted grant #181 were filed after the epic and landed here, so the branch carries more than the three sub-epics its checklist lists
• Root architecture.md keeps the dar node and the AmuletRules edge against Sweep the Canton Coin path out of the docs #186: both are still true
• Cancel and decline live on /pending, not the dashboard, which renders no pending grants
• Editing the root README.md was authorized for Delete dapp/daml and the Canton Coin path #156, against the standing guardrail
• Every ledger step was proven headlessly against a live LocalNet; no CIP-0103 wallet prompt has been observed

Acceptance criteria

• A grant is created, accepted, withdrawn, cancelled and residual-claimed in DBT end to end
• dpm is not required to run the repository
• No AmuletRules or mining round reaches a write
• Creating a grant is one wallet approval, not two

Test plan

Automated tests

1. Run pnpm install
2. Run pnpm lint, pnpm typecheck, pnpm build, pnpm test, pnpm knip, pnpm docs:check and pnpm run check:anatomy from the repo root
3. Expect every gate to pass, with dapp/frontend at 223 tests

Manual verification

1. Check out this branch, run ./scripts/dev-stack.sh up and wait for 3010, 3012 and 3013 to answer
2. Open http://localhost:3012 and connect a CIP-0103 wallet as the funder
3. Tap the faucet in the dashboard header and expect the DBT balance to rise by 1000
4. Create a grant and expect exactly one wallet approval
5. Open /pending as the funder, cancel a grant, and expect its reserved holdings back in the balance
6. Create another grant, accept it as the receiver, then withdraw, cancel and claim the residual
7. Expect both balances to settle and no Splice call anywhere in the flow

Breaking changes

• pnpm run build-dar is gone; both DARs ship under vendor/ and pnpm run deploy-dar -- <dar> uploads them
• VITE_WALLET_RPC_URL is replaced by VITE_REGISTRY_URL, and a deployment also needs REGISTRY_URL pointing at a reachable registry

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

To be added before review.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
demo.canton-dappbooster	Error		Sep 11, 2026 8:21pm UTC
docs.canton-dappbooster	Ready	Preview	Sep 11, 2026 8:21pm UTC