We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we are using coins: 100000000000000uosmo,100000000000000uion and denom in the default values.yaml file in defaultChains.
coins: 100000000000000uosmo,100000000000000uion
denom
values.yaml
defaultChains
The side effect of this is, the registry service is currently only able to show a single denom in the assetlist.
Ability to specify multiple denoms as per the chain in the default values (based on the actual chain-registry)
defaultChains: osmosis: image: anmol1696/osmosis:latest home: /root/.osmosisd binary: osmosisd prefix: osmo denom: uosmo denoms: - name: osmo # "<exp 0 denom>, <exp 6 denom>" units: "uosmo, osmo" - name: ion units: "uion, ion" coins: 100000000000000uosmo,100000000000000uion hdPath: m/44'/118'/0'/0/0 coinType: 118 repo: https://github.com/osmosis-labs/osmosis
Add tests in the e2e package to make sure this runs always
The text was updated successfully, but these errors were encountered:
registry
No branches or pull requests
Overview
Currently we are using
coins: 100000000000000uosmo,100000000000000uion
anddenom
in the defaultvalues.yaml
file indefaultChains
.The side effect of this is, the registry service is currently only able to show a single denom in the assetlist.
Proposal
Ability to specify multiple denoms as per the chain in the default values (based on the actual chain-registry)
Add tests in the e2e package to make sure this runs always
The text was updated successfully, but these errors were encountered: