feat(gateway-contracts): implement coprocessor contexts#211
Closed
melanciani wants to merge 6 commits intofeat/coprocessor_contexts_in_gatewayfrom
Closed
feat(gateway-contracts): implement coprocessor contexts#211melanciani wants to merge 6 commits intofeat/coprocessor_contexts_in_gatewayfrom
melanciani wants to merge 6 commits intofeat/coprocessor_contexts_in_gatewayfrom
Conversation
d6e8f16 to
e42ed50
Compare
0c0e6c6 to
e86b236
Compare
e86b236 to
d3aab1a
Compare
892a6ba to
4b646c6
Compare
4b646c6 to
11ed791
Compare
isaacdecoded
approved these changes
Jul 1, 2025
Contributor
isaacdecoded
left a comment
There was a problem hiding this comment.
What a great job! 👏
Do you think we should open an issue to unify the imports at some point? 🤔
Contributor
Author
I'll let you create it yes, it's not urgent at all though no worries |
1ac0f60 to
3b928b7
Compare
65045a8 to
2acc6b4
Compare
dartdart26
added a commit
that referenced
this pull request
Sep 24, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
dartdart26
added a commit
that referenced
this pull request
Sep 24, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
dartdart26
added a commit
that referenced
this pull request
Sep 25, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
dartdart26
added a commit
that referenced
this pull request
Sep 25, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
dartdart26
added a commit
that referenced
this pull request
Sep 25, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
isaacdecoded
pushed a commit
that referenced
this pull request
Oct 2, 2025
Add support for a separate uin256 context ID in the event listened to by the gw-listener and using it to sign a `CiphertextVerification` in transaction-sender. Related to #211
bdfb2ee to
1054904
Compare
1c5440e to
08abc73
Compare
Contributor
Author
|
closing this for now as we'll continue work on this later ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
todo:
what have been done :
VerifyProofRequestevent as a new fieldCiphertextVerificationstruct' as a new fieldVerifyProofResponseevent as a new fieldextraDatafield (same forRejectProofResponse)getConsensusS3BucketUrlsinCiphertextCommitsalso updated spec : https://github.com/zama-ai/tech-spec/pull/292
closes https://github.com/zama-ai/fhevm-internal/issues/439
closes https://github.com/zama-ai/fhevm-internal/issues/172