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
as of cosmos-sdk v0.47.0-alpha1, this has not been implemented. But if this is implemented and new chains start adopting it, we will have a tricky situation where users will have two sets of addresses (even if these chains all use the 118 derivation path):
legacy “short addresses”
new “long addresses”
Short addresses will be used on chains running old versions of cosmos-sdk, and long addresses will be used on those with new versions.
I am wondering if Stargaze Names can be designed to support both address formats.
The text was updated successfully, but these errors were encountered:
Not a problem that needs to be addressed immediately, but I want to point this out here.
The latest version of ADR-028 (https://github.com/cosmos/cosmos-sdk/blob/main/docs/architecture/adr-028-public-key-addresses.md) suggests a new address derivation mechanism that results in 32-byte addresses, instead of the current bitcoin-style 20-byte ones.
as of cosmos-sdk v0.47.0-alpha1, this has not been implemented. But if this is implemented and new chains start adopting it, we will have a tricky situation where users will have two sets of addresses (even if these chains all use the 118 derivation path):
Short addresses will be used on chains running old versions of cosmos-sdk, and long addresses will be used on those with new versions.
I am wondering if Stargaze Names can be designed to support both address formats.
The text was updated successfully, but these errors were encountered: