-
Notifications
You must be signed in to change notification settings - Fork 483
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
Aliases in wallets and the Playground #673
Comments
Aliases for transaction ids just occurred to me. It might actually be quite nice - we could auto-generate a fairly-unique but memorable string (e.g. using the "correct horse battery staple" approach), which would then at least make it easier to see when things are referring to each other. |
I think aliases should be local to a wallet, here's why. Aliases seems like an example of somewhere we need a petname system: http://www.skyhunter.com/marcs/petnames/IntroPetNames.html Consider public key addresses:
Where does this provide benefit? Consider:
Also as a minor convenience point, we allow people to use whatever names they like for hashes. The playgrounds are an unusual example, since the user controls the entirety of what would normally be a multi-party system. So in that case we could just enforce that everyone's petname mappings are the same. |
If we where to use petnames, we’d at least have to pre-populate them with some global default name. For the case of currencies (fungible ones), you really just want to get the currency name that everybody else uses. Generally speaking, petnames seem to make much more sense for non-fungible tokens than fungible ones. |
I think we absolutely want a global nickname registry too. |
Ok, and then petnames shadow nicknames? |
Ideally you don't use nicknames except in clearly marked circumstances ("You've just received a payment from .... (nickname: "Bob"). Would you like to add them as "Bob" to your address book?"). |
@krisajenkins & @j-mueller What is the story with aliases for the Summit version? |
We want to have some kind of alias support in both wallets and the Playground, so that when users are issuing commands and looking at outputs they can see a human-readable identifier rather than a hash.
We probably want these for:
The text was updated successfully, but these errors were encountered: