BAC-L3-COSMOS-121Cosmos SDK
IBC II — token transfer between chains
IBC's founding use case, and its main subtlety: the token you receive is not the original token, and its worth depends on the path it took.
- Level
- L3 — Infrastructure engineer
- Duration
- 4 h
- Track
- Cosmos SDK
- Maintainer
- Cosmos Lead Architect
Learning objectives
- 01Perform a transfer between two chains and verify it on both sides
- 02Explain the denomination derived from the path taken
- 03Handle packet timeout and refund
Guided lab
Transfer a token between chains, send it back, and verify total supply conservation.
Independent lab
Trigger a packet timeout and document the refund procedure.
Security angle
Two tokens with the same name arriving by different paths are not fungible: confusing them costs funds.
Assessment
Round-trip transfer verified by supply checks on both sides.