Skip to content
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

bech32 lower vs UPPER distinction #163

Open
jaekwon opened this issue May 3, 2022 · 2 comments
Open

bech32 lower vs UPPER distinction #163

jaekwon opened this issue May 3, 2022 · 2 comments

Comments

@jaekwon
Copy link
Contributor

jaekwon commented May 3, 2022

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.

@moul
Copy link
Member

moul commented May 6, 2022

additionally to the pub key, do you want to be able to add additional metadata in some ways?

@KorNatten
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🌟 Wanted for Launch
Development

No branches or pull requests

4 participants