proxmox/docs/04-configuration/naming-conventions/02_DBIS_NAMESPACE_AND_UTRNF_MAPPING.md

DBIS namespace and UTRNF mapping

Purpose: Resolve collisions between the Universal Token Role Naming Framework (01_UTRNF_REFERENCE.md) and DBIS / GRU / Chain 138 conventions. This document is authoritative for interpreting symbols in this repository.

---

1. Glossary (read this first)

Term	Meaning in this repo
UTRNF c prefix	In the generic framework: collateral token (locked collateral in a lending-style protocol).
DBIS c* symbol	Compliant GRU settlement / e-money token on Chain 138 (and related networks), e.g. cUSDC, cUSDT, cXAUC. Not defined as UTRNF collateral.
DBIS cW*	Compliant wrapped or public-chain / bridge-facing representation; see GRU transport and mapper docs.
tokenRole / registry	Machine-readable classification; overrides naive prefix parsing when present.

Rule: Never classify cUSDC, cUSDT, or other DBIS c* tokens using UTRNF’s “c = collateral” row. Use this mapping doc plus registry fields (04_REGISTRY_AND_JSON_FIELDS.md).

---

2. DBIS-reserved prefixes and families

2.1 c + underlying ticker (compliant base money)

• Meaning: Canonical compliant fiat / commodity-linked GRU tokens (V1 today; V2 evolution per GRU_C_STAR_V2_STANDARDS_MATRIX_AND_IMPLEMENTATION_PLAN.md).
• Examples: cUSDC, cUSDT, cEURC, cXAUC, cXAUT.
• Canonical addresses and decimals: EXPLORER_TOKEN_LIST_CROSSCHECK.md, ADDRESS_MATRIX_AND_STATUS.md.

2.2 cW + suffix (compliant wrapped / bridge side)

• Meaning: Wrapped or mapped representation for transport and public-chain interoperability (not the same contract family as every base c*).
• Configuration: C_TO_CW_MAPPER_MAPPING.md, config/token-mapping-multichain.json, GRU_TRANSPORT_ACTIVE_JSON.md.

2.3 Other common Chain 138 symbols

• WETH / WETH10: Wrapped native or project WETH variant; not GRU c*. Treat as wrapped native or bridge-adjacent per contract docs.
• LINK: Chainlink token on Chain 138 as deployed; role is utility/oracle collateral, not GRU base money.

---

3. UTRNF prefixes used as-is in DBIS (when applicable)

When introducing new instruments that are not GRU c* base money, the following UTRNF prefixes can align with the reference grammar if symbols do not conflict with reserved c* / cW* families:

UTRNF prefix	Typical use in DBIS context
a	Lending-style supplied asset / receipt token (if a product exposes Aave-like semantics).
vd / sd	Variable / stable debt receipts.
y	Vault or strategy share token.
lp	DEX or PMM liquidity share (pair composition in symbol or metadata).
r	Protocol reserve or treasury share (internal accounting).
s	Synthetic price exposure (distinct from c* compliant money).
i	Incentive / reward distribution token.
x	Wrapped external asset where the ecosystem chooses x over w.

Wrapped native: Many ecosystems standardize on WETH, WBTC, etc. DBIS may use either UTRNF x or de-facto w* names; document the choice per deployment.

---

4. Collision matrix (UTRNF vs DBIS)

UTRNF role	UTRNF prefix	DBIS collision?	Action
Collateral (locked, lending)	c	Yes	Do not map DBIS cUSDC to this row. Use gruCompliantBase or equivalent registry field.
Asset (supplied)	a	No	Use if product introduces a* tokens.
Variable / stable debt	vd / sd	No	Use if debt tokens are deployed.
Liquidity	lp	No	Align with pool naming in docs / aggregators.
Synthetic	s	Low	Avoid ambiguous s symbols that look like tickers without registry context.
Wrapped	x	Low	Distinguish from WETH10 / bridge-wrapped naming in 03_BRIDGES_CROSS_CHAIN_NAMING.md.

---

5. Registry-first and version-aware identity

Per GRU V2 direction:

• Symbol alone is insufficient during V1/V2 coexistence or duplicate ERC-20s on an explorer.
• Use assetId, assetVersionId, and forwardCanonical (or equivalent) in registries.
• Explorer and APIs may show cUSDC; bridges and routers must resolve versioned canonical records, not bare strings.

---

6. GRU monetary layers (M00, M0, M1)

GRU denominations (M00 / M0 / M1) describe monetary policy layers, not ERC-20 symbol prefixes. If a token is tied to a specific layer, represent that in registry metadata (e.g. gruLayer) rather than overloading the ticker. See in-repo gru-docs/ (e.g. formulas / executive summary) and GRU_STANDARDS_PROFILE.md.

---

7. Diagram: UTRNF adoption vs DBIS c*

flowchart LR
  subgraph utrnf [UTRNF_grammar]
    a[a_prefix]
    vd[vd_prefix]
    lp[lp_prefix]
    utrnf_c[c_as_collateral]
  end
  subgraph dbis [DBIS_Chain138]
    cstar[c_star_compliant_money]
    cw[cW_wrapped_bridge]
    reg[registry_fields]
  end
  utrnf -->|"adopt where no conflict"| dbis
  utrnf_c -.->|"do not map to cUSDT_cUSDC"| cstar
  cstar --> reg
  cw --> reg

---

8. Accounting hint (portfolio tools)

For generic UTRNF portfolios, tools may use prefix rules from doc 01. For DBIS Chain 138, treat c* balances as GRU compliant cash / settlement tokens unless a registry marks a contract as legacy or non-canonical. Debt and LP positions require contract-level roles from the relevant protocol (PMM, vaults, etc.), not inference from c*.