Fix ChatGPT: refactor contract to work in the context of a confidential request #82
Conversation
This file contains 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
haythemsellami
requested review from
ferranbt,
metachris and
zeroXbrock
as code owners
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.
If my understanding is correct, the current implementation is not working on Rigil testnet when sending a confidential request that uses an instance of ChatGPT, more on this issue here flashbots/suave-geth#243.
This PR refactor
ChatGPT.solto not store theapiKeyin storage and just assume it will be stored confidentially somewhere else and passed as an argument to thecomplete()function.