You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Working devnet
* Update dockers for l1 services
* Fix op-proposer
* Fix node js script
* Remove npm from script
* Install foundry
* Add op-deployer path
* Install dasel
* Fix reshape-allocs script
* Continue fixing reshape-allocs script
* Continue fixing reshape-allocs script
* Convert branch name
* Undo branch name change
* Fix typo
* Fix dockerfile for l1-genesis
* Update dockerfile for op-geth
* More conflicts
* More conflicts
* Fix l2-genesis
* Fix context path
* Fix deployer for terraform
* Fix path
* More fixes and rebuild
* Add preparation scripts to l2 CI
* Fix l1 rpc path
* Move l2-rollup command to dockerfile
* Add config path in docker for op-node
* Add preparation steps to op-node CI
* Add l2-config to CI
* Force jwt
* Remove newline
* Add image for batcher
* Add CI for batcher
* Restore servcie order
* Add image for proposer
* Copy deployer dir
* Add game address fix
* Combine duplicate image scripts
* Update to v4
* Restore login verison
* Fix deployment artifacts
* Add dependency
* Add file path
* Fix file copy
* UPdate init
* Update GAME_FACTORY to use proxy dispute game factory address
* Fix incorrect path string in GAME_FACTORY settings
* Add Espresso contract configs to prepare-allocs
The prepare-allocs.sh script doesn't currently have the Espresso Smart Contracts
enabled.
This change enables the contract and sets the preApprovedBatcherKey to work in
a non-TEE environment.
* Modify game-type for op-proposer
The default game type when the `game-type` parameter is unspecified is `0`. By
default there does not seem to be a `Dispute Game` deployed for `game-type` `0`,
however, other game types do exist, including `game-type` `1`.
This change sets the `game-type` of the `op-proposer` to `1` for the
`docker-compose.yml` file.
* Specify a `create2Salt` value for espresso deployment
When the `op-deployer` performs the `apply` operation, it utilizes the values in the
`state.json` file to inform how it should behave. Namely among these is the
`create2Salt` value. The `op-deployer` utilizes the `create2` method for
performing deployments according to specifications. This salt value is utilized and
helps to assist in determining the resulting contract addresses. For convenience, it
would be nice to have some deterministic values to test against for repeatability.
This change modifies the `state.json` file before running `op-deployer` `apply`
in order to ensure that we can see deterministic contract address generation.
* Add dependency
* Copy deployment artifacts
* Add scripts for demo and documentation
* Fix syntax
* Remove another COPY
* Add exposed ports for more nodes in docker-compose
The `verifier`, `caff-node`, and `sequencer` all do not have their ports forwarded to
the host machine. Having these ports exposed can make testing / debugging easier
by utilizing the optimism RPC API.
This change exposes these ports.
* Fix CAFF environment variables
The CAFF environment variables utilized in the `docker-compose.yml` need to have
a prefix of `OP_NODE_`, otherwise they will not apply. These not applying causes
the `caff-node` to never make progress.
This change corrects the misconfigured `caff-node` environment variables, and
cleans up an unnecessary one.
* Set `caff.node` to `true` for `caff-node`
The `caff-node` is meant to be running a derivation based on information retrieved
from Espresso's network. However, it needs to be enabled to do so. This change
enables the `caff-node`'s mode by explicitly setting `caff.node` to `true` in the
launch configuration.
* Support alias and input check
* Undo changes to fix the build and make progress
* Fix CI
* Remove commented-out code
---------
Co-authored-by: Artemii Gerasimovich <[email protected]>
Co-authored-by: Theodore Schnepper <[email protected]>
0 commit comments