You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.
Current behavior: ChainId allows only base-10 numbers
Desired behavior: ChainId accepts a string
Use case: The current standard used by all known CosmosSDK blockchains are string as ChainId. E.g. cosmoshub-3
Even though the standard for Ethereum blockchains is using a numeric ChainId, in the Cosmos Ecosystem strings are mostly used and expected to be used in the future. Supporting string ChainId's would make the integration seamless for many projects.
Requests may be closed if we're not actively planning to work on them.
The text was updated successfully, but these errors were encountered:
Proposal: ChainId should accept a string
Current behavior: ChainId allows only base-10 numbers
Desired behavior: ChainId accepts a string
Use case: The current standard used by all known CosmosSDK blockchains are string as ChainId. E.g. cosmoshub-3
Even though the standard for Ethereum blockchains is using a numeric ChainId, in the Cosmos Ecosystem strings are mostly used and expected to be used in the future. Supporting string ChainId's would make the integration seamless for many projects.
Requests may be closed if we're not actively planning to work on them.
The text was updated successfully, but these errors were encountered: