Adds understanding IBC denom tutorial #727

toschdev · 2021-06-22T16:14:00Z

Preview: https://deploy-preview-727--sdk-tutorials.netlify.app/

New tutorial contribution from https://github.com/dgtlntv via @okwme

Maximilian Blazek wrote up these steps, this PR is still a work in progress

send tokens with IBC
trace the Denom
understand how Denoms work
PR includes updates to .vuepress/config.js to add on-page navigation

understanding-ibc-denoms/index.md

barriebyron · 2021-06-30T21:00:27Z

understanding-ibc-denoms/index.md

+  path: transfer/channel-0
+```
+
+From this command, you now know that there is an IBC port `transfer` and channel `channel-0`. But to know the IBC light client behind the port and channel, you need to perform another query. 


a ha that path defines the port and channel! (where do I learn about this path?)

path: transfer/channel-0

barriebyron · 2021-06-30T21:02:12Z

understanding-ibc-denoms/index.md

+
+From this command, you now know that there is an IBC port `transfer` and channel `channel-0`. But to know the IBC light client behind the port and channel, you need to perform another query. 
+
+Why is it called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command  explains the details of the denom path. 


Suggested change

Why is it called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command explains the details of the denom path.

Why is the path in IBC called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command explains the details of the denom path.

I wasn't sure what "it" was in the sentence, I think we are describing the path in IBC (guessing here!)

barriebyron · 2021-06-30T21:03:03Z

understanding-ibc-denoms/index.md

+Why is it called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command  explains the details of the denom path. 
+
+```
+gaiad q ibc channel client-state transfer channel-0 --node tcp://localhost:26557


I got lost here too... is line 40 the command and then starting at line 41 is the output?

barriebyron · 2021-06-30T21:03:27Z

understanding-ibc-denoms/index.md

+
+That's a lot of information, but it doesn't answer the question: how do you know if this IBC client can be relied upon?
+
+* Note the chain ID and the client ID.


not sure what's going on here, but am very interested to learn and know more. Is the asterisk * on line 101 a way of denoting a subheading? or a way to signal one of a series of things that help us know if the IBC client is trusted?

barriebyron · 2021-06-30T21:07:11Z

understanding-ibc-denoms/index.md

+        "height": "70",
+        "round": 0,
+        "block_id": {
+>>>>>>>>> "hash": "78AD39C7DBB0C28AA1DD4DBF909E8FC37522CAB177484871AB3FBD18B2F165B4", <<<<<<<<<<<<<<<<


is this a merge conflict? or ?? intended

understanding-ibc-denoms/index.md

barriebyron · 2021-06-30T21:09:12Z

understanding-ibc-denoms/index.md

+
+Use cosmos-sdk v0.42.4:
+
+```


for some reason I didn't have a cosmos-sdk directory (ouch)

barriebyron · 2021-06-30T21:10:02Z

understanding-ibc-denoms/index.md

+-proto ./proto/ibc/core/channel/v1/query.proto \
+-d '{"port_id": "transfer", "channel_id": "channel-0"}' \
+localhost:9091 ibc.core.channel.v1.Query/ChannelClientState
+{


help! I don't know where commands actually end (I need a lot of teaching!)

barriebyron · 2021-06-30T21:11:32Z

@toschdev I want to learn more about this content, so perhaps we can all learn together as a team and make this tutorial clear as glass! I checked out the branch and made direct editorial changes, and also provided in-line questions and suggestions. Good start.

Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>

…orials into explaining-denoms

barriebyron

@toschdev lots of commits for editorial finesse, only a few substantive suggestions. lmk if you have questions or you want me to commit the suggestions.

KUDOS this is an amazing tutorial!! I understand so much more

README.md

understanding-ibc-denoms/index.md

Thanks for the review, improving the tutorial by a magnitude 🙏 Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>

Adds understanding IBC denom tutorial

b24bf52

toschdev self-assigned this Jun 22, 2021

toschdev requested a review from barriebyron as a code owner June 22, 2021 16:14

Tobias Schwarz and others added 3 commits June 22, 2021 18:25

Format headers

22be870

Working on the format

637f3ea

editorial review, I have many questions of the commands

3a1ac4a

barriebyron reviewed Jun 30, 2021

View reviewed changes

barriebyron marked this pull request as draft July 1, 2021 12:58

barriebyron changed the title ~~Adds understanding IBC denom tutorial~~ [WIP] Adds understanding IBC denom tutorial Jul 1, 2021

Tobias Schwarz and others added 8 commits July 2, 2021 13:40

Apply suggestions from code review

fc65a36

Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>

Applies tutorial workflow

2a53998

Merge branch 'master' into explaining-denoms

c50f837

Split bash command from result

9fe400d

Merge branch 'master' into explaining-denoms

3046296

Implements suggestions

759ac20

Merge branch 'explaining-denoms' of https://github.com/cosmos/sdk-tut…

d1ac96e

…orials into explaining-denoms

Update title

edde04a

toschdev marked this pull request as ready for review July 8, 2021 21:16

toschdev changed the title ~~[WIP] Adds understanding IBC denom tutorial~~ Adds understanding IBC denom tutorial Jul 8, 2021

Update example with current testnet

3718e0e

toschdev marked this pull request as draft July 8, 2021 23:32

Tobias Schwarz added 8 commits July 9, 2021 01:33

Split tutorial further

6c5dc29

Manually guide through the steps listed in the script

d3a027e

Add how to stop the blockchains

19628c4

Merge branch 'master' into explaining-denoms

95b4db7

Add tile for understanding denoms

3150a95

Remove walkthrough, outdated and not working

78e8c2b

correct tile link

a46f3f4

Adjust learning goals

b588f17

Tobias Schwarz added 14 commits July 14, 2021 01:16

Refactor the cosmos registry header

901a11f

Remove cosmos registrar section, not reproducible

f7bb7d7

Merge branch 'master' into explaining-denoms

a11df13

Add approaches to find blockchain channels

37f8b86

Merge branch 'explaining-denoms' of https://github.com/cosmos/sdk-tut…

05b9bde

…orials into explaining-denoms

Swap section about finding paths

3e49e83

Add gaia tag to tutorial

9870de0

update description on registrars

a77354f

update description on registrars

b265636

Update descriptions

855d3df

Update descriptions

68a82cb

remove grpc intro

bcd9757

Example block height query

7985c6c

Remove indication of github issue

c164ae1

toschdev marked this pull request as ready for review July 14, 2021 00:36

Update navbar description

8d32525

toschdev requested review from alijnmerchant21, barriebyron and soniasingla July 14, 2021 10:17

barriebyron approved these changes Jul 14, 2021

View reviewed changes

Apply suggestions from code review

8e5fa21

Thanks for the review, improving the tutorial by a magnitude 🙏 Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>

toschdev merged commit db064bb into master Jul 14, 2021

toschdev deleted the explaining-denoms branch July 14, 2021 17:08


		From this command, you now know that there is an IBC port `transfer` and channel `channel-0`. But to know the IBC light client behind the port and channel, you need to perform another query.

		Why is it called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command explains the details of the denom path.

	Why is it called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command explains the details of the denom path.
	Why is the path in IBC called a light client? Because it is a light client of the _other_ chain, keeping track of its blockhashes. The `ibc channel client-state transfer` command explains the details of the denom path.


		That's a lot of information, but it doesn't answer the question: how do you know if this IBC client can be relied upon?

		* Note the chain ID and the client ID.


		Use cosmos-sdk v0.42.4:

		```

Adds understanding IBC denom tutorial #727

Adds understanding IBC denom tutorial #727

Uh oh!

Conversation

toschdev commented Jun 22, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

barriebyron commented Jun 30, 2021

Uh oh!

barriebyron left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

toschdev commented Jun 22, 2021 •

edited

Loading