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
Since we use the bech32 address in std, we need to add validation regarding capitalization, else unexpected bugs will occur.
Another solution is to forgo bech32 and use a different string representation... This is about whether gno.land std packages prefer to include the prefix and deal with malleability, or prefer to strip the prefix but use an efficient representation with string kind.
The text was updated successfully, but these errors were encountered:
From a non-dev POV I used to love the bech32, it was easy to recognise the address and the token.
Ever since cw20 came along, it made it more confusing, like all the tokens on Juno now have juno1 addresses and it's easy to get confused for people who are not used to it imo.
If Gno will allow different tokens on the chain, it will face the same problem with the prefix.
Since we use the bech32 address in std, we need to add validation regarding capitalization, else unexpected bugs will occur.
Another solution is to forgo bech32 and use a different string representation... This is about whether gno.land std packages prefer to include the prefix and deal with malleability, or prefer to strip the prefix but use an efficient representation with string kind.
The text was updated successfully, but these errors were encountered: