-
Notifications
You must be signed in to change notification settings - Fork 2
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
dib542
merged 52 commits into
main
from
509-improve-token-denom-handling-for-ibc-tokens
Jan 24, 2024
Merged
fix: token denom handling for IBC tokens on testnet #516
dib542
merged 52 commits into
main
from
509-improve-token-denom-handling-for-ibc-tokens
Jan 24, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dib542
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 23, 2024 10:29
1c81d92
to
8195c82
Compare
This was referenced Jan 23, 2024
dib542
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 23, 2024 22:06
8195c82
to
f68dc5a
Compare
- 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
- use new env variables instead: - REACT_APP__CHAIN_REGISTRY_ASSET_LISTS - REACT_APP__CHAIN_REGISTRY_CHAINS - REACT_APP__CHAIN_REGISTRY_IBC_DATA
dib542
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 23, 2024 22:40
f68dc5a
to
101a334
Compare
dib542
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 24, 2024 00:47
af0bf51
to
968731a
Compare
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
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 24, 2024 01:21
968731a
to
a9ed6dd
Compare
dib542
force-pushed
the
509-improve-token-denom-handling-for-ibc-tokens
branch
from
January 24, 2024 01:30
a9ed6dd
to
b8eacf2
Compare
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))
🎉 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
chain-registry
package datanow:
chain-registry
package data in GitHubeg.
useTokens(['untrn','ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2'])
chain-registry
package data in GitHubNote that the build for this release is intended to be skipped, as the code no longer works against duality-devnet:
rpc.dev.duality.xyz
andlcd.dev.duality.xyz
.