-
Notifications
You must be signed in to change notification settings - Fork 5
Remove the NullifierKeyCommitment from the AVM layer #70
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
Conversation
janmasrovira
commented
Jul 29, 2025
- Closes Don't expose nullifierKeyCommitment directly to the user #37
AVM/Class/Translation.lean
Outdated
| { object := {newObj with nullifierKeyCommitment := Anoma.NullifierKeyCommitment.universal} | ||
| { object := newObj | ||
| ephemeral := true | ||
| key := Anoma.NullifierKey.universal } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we remove the key field from ConsumableObject if it's always universal anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not done for ConsumableObject, only for Object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed the key field from ConsumableObjects and replaced all references to Universal
lukaszcz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.