From 04531d83bf51d949f4bf2d61e88e419d1620ea32 Mon Sep 17 00:00:00 2001 From: srdtrk <59252793+srdtrk@users.noreply.github.com> Date: Fri, 19 Jan 2024 15:05:17 +0300 Subject: [PATCH] docs: added docs on denom metadata (#5665) --- docs/docs/02-apps/01-transfer/01-overview.md | 10 ++++++++-- .../version-v8.0.x/02-apps/01-transfer/01-overview.md | 10 ++++++++-- 2 files changed, 16 insertions(+), 4 deletions(-) diff --git a/docs/docs/02-apps/01-transfer/01-overview.md b/docs/docs/02-apps/01-transfer/01-overview.md index da8595c7e88..1e308eb3fdf 100644 --- 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 index 7e257d1e805..994850822b4 100644 --- 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