-
Notifications
You must be signed in to change notification settings - Fork 2
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: initial draft implementation #330
base: main
Are you sure you want to change the base?
Conversation
metadata[..60].copy_from_slice(front.as_slice()); | ||
metadata[60..].copy_from_slice(&chain_id_bytes); | ||
|
||
// TODO: How to build metadata for the proof? |
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.
Check with what's happening in fhevmjs: the data must be paid out in the same way
.await?; | ||
} | ||
Err(ExecutionError::InvalidProof(_)) => { | ||
// TODO: Should we mark the proof as invalid in the database? |
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 don't know if that's relevant here, but if the proof fails we want the verifier to send an (error) transaction back to the HTTPZ Gateway, instead of just ignoring the request.
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.
It is relevant here, but also in the:
- transaction-sender
- ZKProofManager contract
Maybe can be done in a later sprint if not implemented in the ZKProofManager contract yet.
a17068d
to
8247fb0
Compare
No description provided.