Open
Conversation
…e.yml - Add tools/mockteeprover: mock TEE prover with /task/ API (no /v1 prefix) - Extract TEE containers (mockteerpc, mockteeprover, tee-proposer, tee-challenger) into docker-compose-tee.yml - Fix tee-challenger: use mockteeprover:8690 instead of mockteerpc:8090, read GAME_WINDOW from env - Update 7-run-tee-game.sh to use combined compose files and check MOCKTEEPROVER_IMAGE_TAG Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add TEE_SIGNER_PRIVATE_KEY to example.env for mockteeprover - Hardcode tee-challenger game-window to 86400s to prevent games falling out of window before resolution Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…solution - Switch tee-challenger private key from OP_CHALLENGER to OP_PROPOSER - Add --selective-claim-resolution flag - Remove --additional-bond-claimants (tx sender is now proposer) - Add CHALLENGER_ADDRESS env var support in add-tee-game-type.sh Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Change TEE_SIGNER_PRIVATE_KEY to proposer key - Add CHALLENGER_ADDRESS for new contract deployment Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…_CHALLENGER Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…contract Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…Addr overrides Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…NGER_ADDRESSES Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
This pull request introduces support for running TEE (Trusted Execution Environment) game types in the devnet environment. It adds new configuration options, build logic, and Docker services for TEE-related components, including mock TEE RPC, TEE proposer, and TEE challenger. Additionally, the PR improves environment setup scripts for better branch management and updates configuration files to support these new features.
TEE Game Support and Docker Services:
mockteerpc,tee-proposer, andtee-challenger, including all necessary environment variables, dependencies, and port mappings indocker-compose.yml.devnet/7-run-tee-game.shto automate TEE game setup, check for required images, and start the new services.0-all.sh) to include the TEE game setup step.Environment and Build Configuration:
.envandexample.envfiles with new variables for TEE-related builds and images (OP_STACK_TEE,OP_CONTRACTS_TEE,MOCKTEERPC, etc.), and added aTEE_GAME_TYPEparameter. [1] [2]init.shto support branch switching for all major components, including new logic to build TEE-related images and the mock TEE RPC image based on environment variables. [1] [2] [3] [4] [5] [6]OP Succinct/Dispute Game Improvements:
5-run-op-succinct.shto dynamically update theANCHOR_STATE_REGISTRY_ADDRESSin both proposer and challenger.envfiles after deploying a new game implementation.Miscellaneous:
ANCHOR_STATE_REGISTRY_ADDRESSto the example.envfiles for both the proposer and challenger. [1] [2]These changes collectively enable TEE game workflows in the devnet, improve build and environment management, and lay the groundwork for more advanced dispute game scenarios.