Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: token denom handling for IBC tokens on testnet #516

Merged
merged 52 commits into from
Jan 24, 2024

Conversation

dib542
Copy link
Collaborator

@dib542 dib542 commented Jan 23, 2024

This PR fixes the usage of assets/tokens in the app from using a master list of "all possible" tokens to using "runtime" tokens: token information from up to date chain-registry package information on GitHub.

previously:

  • token list was derived from all active chain IBC connections cross-referenced with static chain-registry package data

now:

  • token lists are derived as needed at runtime from current chain-registry package data in GitHub
    • the context of which tokens should be queried for needs to be provided in terms of native chain denom strings:
      eg. useTokens(['untrn','ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2'])
  • chain information is derived as needed at runtime from current chain-registry package data in GitHub

Note that the build for this release is intended to be skipped, as the code no longer works against duality-devnet: rpc.dev.duality.xyz and lcd.dev.duality.xyz.

dib542 added 24 commits January 24, 2024 08:12
    - for local dev tokens: DEV_ASSET_MAP can still be used
    - previously only one IBC channel was selected per chain ID
    - now all channels are used
    - need to be specific to be able to select a specific IBC denom
      of a token than has multiple IBC denoms, possibly even
      connecting the same chains over different connections
@dib542 dib542 force-pushed the 509-improve-token-denom-handling-for-ibc-tokens branch from f68dc5a to 101a334 Compare January 23, 2024 22:40
@dib542 dib542 force-pushed the 509-improve-token-denom-handling-for-ibc-tokens branch from af0bf51 to 968731a Compare January 24, 2024 00:47
@dib542 dib542 changed the title fix: improve token denom handling for IBC tokens fix: token denom handling for IBC tokens on testnet Jan 24, 2024
@dib542 dib542 force-pushed the 509-improve-token-denom-handling-for-ibc-tokens branch from 968731a to a9ed6dd Compare January 24, 2024 01:21
@dib542 dib542 force-pushed the 509-improve-token-denom-handling-for-ibc-tokens branch from a9ed6dd to b8eacf2 Compare January 24, 2024 01:30
@dib542 dib542 merged commit 2265fe9 into main Jan 24, 2024
1 of 2 checks passed
@dib542 dib542 deleted the 509-improve-token-denom-handling-for-ibc-tokens branch January 24, 2024 01:34
dib542 pushed a commit that referenced this pull request Jan 24, 2024
## [1.0.1](v1.0.0...v1.0.1) (2024-01-24)

### Fixes

* token denom handling for IBC tokens on testnet ([#516](#516)) ([2265fe9](2265fe9))
@dib542
Copy link
Collaborator Author

dib542 commented Jan 24, 2024

🎉 This PR is included in version 1.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve token/denom handling for IBC tokens
1 participant