Summary: Token Decimals TCR is best understood not as a generic token list, but as a narrow challengeable sidecar registry for one specific metadata failure mode: ERC-20 tokens whose contracts do not reliably expose decimals() while downstream token-list schemas still require a decimals field. Its primary materials describe it as the fallback path that lets Kleros’s Token Curated Registry and Uniswap-style token lists include otherwise-valid tokens whose onchain decimal metadata cannot be read directly. The reusable mechanism insight is that Token Decimals TCR separates broad token admission from one disputed metadata field, turning how many decimals does this token use? into its own curation and arbitration layer instead of burying that judgment inside wallet maintainers, frontend hardcodes, or opaque list operators.
What it does:
Provides a dedicated Kleros-curated registry for decimal values when token contracts revert or fail to expose decimals() in a way token-list consumers can use
Serves as a compatibility layer for the broader Kleros token list, which follows the Uniswap token-lists schema where decimals is mandatory
Lets contributors publish and challenge decimal metadata instead of forcing downstream apps to choose between exclusion and manual overrides
Gives token-list consumers a dispute-backed fallback path when a token is otherwise valid but its contract metadata is incomplete or nonstandard
Makes metadata correction modular: the main token registry can focus on token identity and correctness, while the decimals sidecar handles one stubborn schema field
Key claims:
The T2CR docs are explicit that tokens reverting on decimals() will not appear in the main token list unless they are accepted in the Token Decimals TCR. That makes this a dependency layer for inclusion, not just an auxiliary note.
The strongest analytical split is between token existence and token metadata legibility. Token Decimals TCR shows that even when a token contract is real and recognizable, one missing field can block downstream discoverability if schemas are rigid.
The docs also surface a useful implementation caveat: the T2CR view-contract example returns 0 when a token does not implement decimals(). Token Decimals TCR therefore functions as a correction path for an otherwise lossy contract-reading layer.
This is a good corpus entry because it exposes a lower-middle control surface that broad token list discussions often flatten away: who supplies metadata for nonstandard tokens, how disputes are resolved, and whether compatibility lives in standards, app-level exceptions, or separate registries.
Token Decimals TCR is especially useful when comparing Token Lists, Kleros Tokens Registry, wallet token directories, and challengeable registries, because it isolates one narrow field-level governance problem instead of treating token listing as a single bundled decision.
Whitepaper: No standalone Token Decimals TCR whitepaper surfaced in this pass. The strongest primary materials were the T2CR docs, Kleros Tokens documentation, the public list endpoint, and the docs README collected in ../whitepapers/token-decimals-tcr-primary-sources-2026-05-13.md.