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

Design the key schedule with viewing keys/note encryption #132

Open
vveiln opened this issue Mar 2, 2023 · 1 comment
Open

Design the key schedule with viewing keys/note encryption #132

vveiln opened this issue Mar 2, 2023 · 1 comment
Labels
prio:high protocol New protocol or design is needed

Comments

@vveiln
Copy link
Member

vveiln commented Mar 2, 2023

No description provided.

@XuyangSong
Copy link
Collaborator

XuyangSong commented Mar 23, 2023

The nullifier key commitment has a useless zero (nk_cm = Com(nk, zero)). We could use the space for key management. Or we could put the nullifier key in the new key management design.

Could we merge all the user-related info (nk, other key stuff, and the app_data_dynamic) in the circuit and then put the result in the note commitment? That would prevent lots of bit-wise encoding/decoding in SinsemillaCommit(note commitment). For example, I use the address = hash(nk_cm, app_data_dynamic), although the address naming is inaccurate and will be improved. #123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio:high protocol New protocol or design is needed
Projects
None yet
Development

No branches or pull requests

2 participants