- 29 Sep, 2022 20 commits
-
-
protolambda authored
Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
protolambda authored
Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
Version Packages
-
github-actions[bot] authored
-
Matthew Slipper authored
Develop -> Master
-
protolambda authored
* op-e2e/actions: action tests base test util * actions: extend action testing doc comments * actions: docstring about format and args Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
op-node: Switch L1 Traversal to a pull based model
-
Matthew Slipper authored
-
Matthew Slipper authored
op-node: Switch L1 Retrieval to pull based
-
Matthew Slipper authored
op-node: Switch channel bank and channel in reader to a pull based stage
-
Matthew Slipper authored
op-node: Switch batch queue to be pull based
-
Joshua Gutow authored
The progress API is very nearly removed from the engine queue stage.
-
Joshua Gutow authored
The attributes queue actually had pretty few modifications to work with the progress API. The logic of switching the batch queue over was a bit more complex because the batch queue is very stateful, but still not the worst.
-
Joshua Gutow authored
Like the rest of the changes, this also required modifications to the next stage - the batch queue in order for it to manage the progress API. This commit required even more changes than usual. I changed the pipeline to be reset to a common starting point and now use the L2SafeHead block to filter out adding batches & L1 blocks to the batch queue.
-
Joshua Gutow authored
This again requires a fair amount of changes to channel_in_reader.go for the channel in reader to maintain its progress state.
-
Mark Tyneway authored
* ctp: fixup deploy scripts for the nft bridge The most important one is the deploy script for the `Proxy` that will end up at the predeploy on L2. There are specific checks for the correct deployer account being used. Will likely require some changes to the hardhat config when doing the actual deployment. * ctp: update deploy scripts * ctp: update deploy scripts * ctp: move away from deterministic deployments * op: deployments * fixes * deploy-script: refactor * deploy: comments
-
Joshua Gutow authored
The L1 Retrieval stage is now responsible for pulling data from the L1 Traversal stage. In addition, the pipeline is responsible for advancing the state of the L1 Traversal stage. The L1 Traversal stage only provides access to the current L1 block once - it pretends to be a queue that is consumed from.
-
Joshua Gutow authored
This makes the L1 Retrieval a purely pull based stage. This commit required large modifications to the channel bank stage in order for the channel bank to maintain it's own progress.
-
Matthew Slipper authored
`check-changed` fails on stacked PRs. This PR updated the CircleCI config to simply run tests if check-changed fails in order to prevent PRs from getting blocked.
-
Joshua Gutow authored
This new name is more idiomatic in go and avoids a confusion with the '642'.
-
- 28 Sep, 2022 4 commits
-
-
protolambda authored
-
smartcontracts authored
Removes refunds for failed NFT deposits. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Mark Tyneway authored
This will make it easier to test the e2e nft deployment scripts. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
smartcontracts authored
* feat(ctb): no refunds Removes refunds from the StandardBridge flow. * regenerate bindings Co-authored-by:
Matthew Slipper <me@matthewslipper.com>
-
- 27 Sep, 2022 16 commits
-
-
Maurelian authored
-
Mark Tyneway authored
* contracts-bedrock: fuzz L2ToL1MessagePasser Fuzzes the L2ToL1MessagePasser for state changes to its storage. This specifically tests that the storage slot that the proofs are generated against is computed correctly. This is important to test as any changes that break the proof would also break this test. The fuzz runs were used to generate test cases in https://github.com/ethereum-optimism/optimism/pull/3469 for off chain computation of the storage slots for withdrawals. * contracts-bedrock: regenerate snapshot * bindings: regenerate Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by:
Matthew Slipper <me@matthewslipper.com>
-
Matthew Slipper authored
* ci: Remove publish dependencies The publish tasks don't need to depend on upstream tests. This will let us run Hive tests earlier in the pipeline, and shave off additional CI runtime. * remove deployer deps * remove job altogether * ci: Fix contracts tests Need to include these artifacts for the contracts tests to work.
-
Matthew Slipper authored
Need to include these artifacts for the contracts tests to work. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
* ci: Fix Hive artifacts I'm still seeing sporadic errors with the l1ops tests. This PR fixes the artifacts upload so that I can debug further. * fix paths
-
Mark Tyneway authored
Will allow for e2e testing of the nft bridge scripts on `ops` Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
* ci: Use workspace rather than cache * remove test code Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Maurelian authored
Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Mark Tyneway authored
Allow `paths` to be unset in the hardhat config. The default path will be used if a top level `paths` object is not included in the hardhat config. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Mark Tyneway authored
Slight improvement to the `MintManager`. Making the reference to the `governanceToken` an immutable is just better than placing it in storage. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Mark Tyneway authored
* op-chain-ops: address aliasing helpers Implement address aliasing helpers in go. Fuzz them to make sure that roundtrip aliasing is reliable. Add foundry fuzz tests that are used to generate test vectors. Note that the JS implementation does not take into account the modular arithmetic, I do not believe that it is used anywhere important currently. See: https://github.com/ethereum-optimism/optimism/blob/develop/packages/core-utils/src/optimism/alias.ts Perhaps we should move our differential fuzzing to use go instead of typescript or along with the typescript because most utilities that we wrote in JS are now also written in go. * chore: make mod-tidy * op-bindings: regenerate * contracts-bedrock: gas snapshot * specs: update address-aliasing
-
smartcontracts authored
Moves the msg.value == amount check when bridging ETH deeper into the call stack. Has the effect of making the function less of a footgun for future developers. Co-authored-by:
Matthew Slipper <me@matthewslipper.com> Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
* ci: Docker login on push Increases the reliability of Docker publish jobs by logging in to Docker Hub first. The secret used is read-only, and scoped to public repositories only. Note that the `l1ops` Hive test will continue to fail until https://github.com/ethereum-optimism/hive/pull/43 is merged. * remove repo * specify nameservers * Update config.yml Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Joshua Gutow authored
This provides a new set of objects which provide the following API guarantees: - The opening of a data for a new L1 block will never. - If it failed to get transactions, it does so in the calls to `Next`. This greatly simplifies usage of this object when constructing new data. If the node did not keep track of the internal state, the external users of this API would have to keep track of this state in a more complex way. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
-
Matthew Slipper authored
-