-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: leak escrow keys #54
Conversation
Meaning we don't manually pass the secret anymore
The escrow's owner is Bob, so I had to make Alice retrieve the AccountNote, and additionally check that matches the secret in the log emitted by `leak_keys`
This is redundant with
Same with these assertions
|
For consistency with
|
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.
self.escrow.to_field()
can be removed as it is redundant with the content of the note
[note_hash_for_nullify, self.escrow.to_field()], |
Also, some dependencies imported into the escrow and clawback escrow contracts, and tests are not used.
The nullification_secret in the EscrowKeys event is not currently used, but I'm keeping it for now to explore potential future use cases
Regarding this, if nullification_secret can be derived from the escrow secret, then it is redundant to emit it.
In the escrow and clawback escrow e2e tests, Also, is this still an issue?
|
chore: add missing colon
o I remove the additional checks, Flamegraph shows a difference of one opcode, but gate-couting remains the same in both functions. without asserts: Opcode count: 1992, Total gates by opcodes: 10564, Circuit size: 10621 with asserts: Opcode count: 1993, Total gates by opcodes: 10564, Circuit size: 10621
Closing this, migrated to defi-wonderland/aztec-extensions |
I'm re-enabling the call to
Escrow::leak_keys
and have modified the E2E tests so that Bob can claim the escrow's tokens without cheating (i.e., without manually passing it), but instead by retrieving the secret from the private log emitted by the contract.The
nullification_secret
in theEscrowKeys
event is not currently used, but I'm keeping it for now to explore potential future use cases