feat(tee-proof-verifier): add backward compatibility logic #244
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
pbeza
force-pushed
the
pab/backward-compatible-offchain-proof-verifier
branch
2 times, most recently
from
5f17538 to
347da99
Compare
pbeza
changed the base branch from
pab/solidity-compatible-offchain-proof-verifier
to
main
pbeza
changed the base branch from
main
to
pab/solidity-compatible-offchain-proof-verifier
pbeza
force-pushed
the
pab/backward-compatible-offchain-proof-verifier
branch
from
347da99 to
bd918fb
Compare
|
Closing in favor of #245. |
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.
This is the first version of the TEE proof verifier's backward compatibility logic, which tries both the new and old verification processes. It's a simpler approach that doesn't use explicit
report_dataversioning. An alternative, more rubust approach was implemented in #245.