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

Move nickname derivation code into nucypher-core? #7

Open
fjarri opened this issue Feb 24, 2022 · 2 comments
Open

Move nickname derivation code into nucypher-core? #7

fjarri opened this issue Feb 24, 2022 · 2 comments
Labels
API Related to public API enhancement New feature or request

Comments

@fjarri
Copy link
Contributor

fjarri commented Feb 24, 2022

Nickname derivation in nucypher (from staker addresses/fleet state checksums, see https://github.com/nucypher/nucypher/blob/main/nucypher/acumen/nicknames.py) is non-trivial to reproduce in other languages (although possible). Should we move it into this crate? In case nucypher-ts wants to use it.

@fjarri fjarri added API Related to public API enhancement New feature or request labels Feb 24, 2022
@theref
Copy link
Contributor

theref commented Mar 25, 2022

I haven't had a proper read through the source code yet, but this is probably a good place to start https://github.com/healeycodes/niceware

@fjarri
Copy link
Contributor Author

fjarri commented Mar 25, 2022

Another possibility is RFC 1751. Our current nicknames cover about 25 bits of space, so 2 words from niceware or 3 words from the RFC will be enough.

EDIT: or the standard mnemonic generation can be used too. The reason the current scheme was chosen in the first place is because it can be tied to colors and not just words and abbreviated conveniently as an "icon" (2 letters + 2 colors).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Related to public API enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants