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

Remove this repo, and migrate to chain:address format #221

Open
shawntabrizi opened this issue Aug 27, 2024 · 5 comments
Open

Remove this repo, and migrate to chain:address format #221

shawntabrizi opened this issue Aug 27, 2024 · 5 comments

Comments

@shawntabrizi
Copy link
Member

Context: https://forum.polkadot.network/t/ux-proposal-consensus-based-address-formats/6072

Accepted Solutions:

cc @joepetrowski

@bkchr
Copy link
Member

bkchr commented Aug 27, 2024

Maybe should be a RFC?

@joepetrowski
Copy link

joepetrowski commented Sep 10, 2024

We still need a registry somewhere that gives the prefix for each consensus system, but then we would really just have three: Polkadot, Kusama, and testnets. So perhaps a repo/registry is overkill and we just go to using chain specs? In which case, I think @bkchr is right, we should have an RFC telling UI/app devs to use the prefix of the consensus system to which it belongs.

Or, both are right :). Delete the repo and have an RFC with recommendations on what should be done instead.

@bkchr
Copy link
Member

bkchr commented Sep 10, 2024

I mean I'm not against removing/moving this repo to somewhere else. :)

@shawntabrizi
Copy link
Member Author

registry somewhere that gives the prefix for each consensus system

Couldn't that live on-chain on the consensus system? Just query Kusama if you want to know the prefix.

This whole registry was about making sure that everyone could "claim their prefix", which is no longer a pattern we want to encourage given the consensus based format.

@joepetrowski
Copy link

Couldn't that live on-chain on the consensus system? Just query Kusama if you want to know the prefix.

Yes, it does, but that doesn't mean people look for it there or use it. I would say archive this repo, but we should also not just make it disappear but rather provide instructions about what to do instead of using it.

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

No branches or pull requests

3 participants