User story / Problem statement
Currently the UI names Canton Coin throughout: the token constant, the amount formatters, four hardcoded strings, and every doc sentence describing the Amulet path. A fresh wallet account also has no way to get something to vest.
Expected outcome
The dApp presents DBT with its own mark, a dashboard action taps the faucet, and no doc still describes the Amulet path.
Acceptance criteria
Technical notes
No registry route reports the faucet cap, so the tap amount is a constant that must stay at or under bootstrap's maxPerTap. The root README.md is deliberately untouched: the lines this makes redundant are PR 3's to delete.
User story / Problem statement
Currently the UI names Canton Coin throughout: the token constant, the amount formatters, four hardcoded strings, and every doc sentence describing the Amulet path. A fresh wallet account also has no way to get something to vest.
Expected outcome
The dApp presents
DBTwith its own mark, a dashboard action taps the faucet, and no doc still describes the Amulet path.Acceptance criteria
utils/tokens.tsxexportsDBTwith an inline SVG mark, andcanton-coin.pngis deletedCCstring remains in user-facing copydapp/frontend/architecture.md, its README and CLAUDE.md, and the rootarchitecture.mddescribe the registry pathTechnical notes
No registry route reports the faucet cap, so the tap amount is a constant that must stay at or under bootstrap's
maxPerTap. The rootREADME.mdis deliberately untouched: the lines this makes redundant are PR 3's to delete.