docs: added docs on denom metadata (cosmos#5665)

notional-labs · Jan 19, 2024 · 04531d8 · 04531d8
1 parent 6e15426
commit 04531d8
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 4 deletions.
diff --git a/docs/docs/02-apps/01-transfer/01-overview.md b/docs/docs/02-apps/01-transfer/01-overview.md
@@ -33,9 +33,15 @@ The denomination trace corresponds to the information that allows a token to be
 origin chain. It contains a sequence of port and channel identifiers ordered from the most recent to
 the oldest in the timeline of transfers.
 
-This information is included on the token denomination field in the form of a hash to prevent an
+This information is included on the token's base denomination field in the form of a hash to prevent an
 unbounded denomination length. For example, the token `transfer/channelToA/uatom` will be displayed
-as `ibc/7F1D3FCF4AE79E1554D670D1AD949A9BA4E4A3C76C63093E17E446A46061A7A2`.
+as `ibc/7F1D3FCF4AE79E1554D670D1AD949A9BA4E4A3C76C63093E17E446A46061A7A2`. The human readable denomination
+is stored using `x/bank` module's [denom metadata](https://docs.cosmos.network/main/build/modules/bank#denom-metadata)
+feature. You may display the human readable denominations by querying balances with the `--resolve-denom` flag, as in:
+
+```shell
+simd query bank balances [address] --resolve-denom
+```
 
 Each send to any chain other than the one it was previously received from is a movement forwards in
 the token's timeline. This causes trace to be added to the token's history and the destination port

diff --git a/docs/versioned_docs/version-v8.0.x/02-apps/01-transfer/01-overview.md b/docs/versioned_docs/version-v8.0.x/02-apps/01-transfer/01-overview.md
@@ -33,9 +33,15 @@ The denomination trace corresponds to the information that allows a token to be
 origin chain. It contains a sequence of port and channel identifiers ordered from the most recent to
 the oldest in the timeline of transfers.
 
-This information is included on the token denomination field in the form of a hash to prevent an
+This information is included on the token's base denomination field in the form of a hash to prevent an
 unbounded denomination length. For example, the token `transfer/channelToA/uatom` will be displayed
-as `ibc/7F1D3FCF4AE79E1554D670D1AD949A9BA4E4A3C76C63093E17E446A46061A7A2`.
+as `ibc/7F1D3FCF4AE79E1554D670D1AD949A9BA4E4A3C76C63093E17E446A46061A7A2`. The human readable denomination
+is stored using `x/bank` module's [denom metadata](https://docs.cosmos.network/v0.50/build/modules/bank#denom-metadata)
+feature. You may display the human readable denominations by querying balances with the `--resolve-denom` flag, as in:
+
+```shell
+simd query bank balances [address] --resolve-denom
+```
 
 Each send to any chain other than the one it was previously received from is a movement forwards in
 the token's timeline. This causes trace to be added to the token's history and the destination port