TK-1420: TON->Gram#664
Merged
Merged
Conversation
Successful WEB deployment 🚀🚀🚀Well done! |
d0a3eb5 to
a8da6b5
Compare
nvasilchuk
approved these changes
Jun 5, 2026
Successful iPad build 🚀🚀🚀Well done! |
nvasilchuk
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://tk-1420-prod.tonkeeper-web.pages.dev
Introduce a single source of truth for the native coin/chain DISPLAY names so the wallet can be rebranded (e.g. TON/Toncoin -> GRAM) without hunting through the codebase, and de-hardcode every client-owned spot that showed "TON"/"Toncoin".
Client changes (rename now lives in one place):
Protocol/identifier values intentionally left as the literal 'TON':
CryptoCurrency.TON value, BLOCKCHAIN_NAME.TON, TON_ASSET.address/id, rate-token keys. Changing these would break asset matching and backend calls.
Boundary: only FRONTEND-owned strings are de-hardcoded here. Display values that come from a backend are passed through unchanged and must be renamed by the ecosystem on the API side.