Skip to content

N
nebula
Switch branch/tag
  1. 13 Feb, 2024 9 commits
    • Adrian Sutton's avatar
      op-challenger: Fix prestate checks (#9478) · 70bd6234
      Adrian Sutton authored 
      * op-challenger: Fix prestate validation

Validators were not added to players created for active games, only inactive
Both the VM and output root prestates were validated against the challenger's output root prestate

* op-challenger: Add option to ignore prestate validation failures

* op-e2e: Allow invalid prestates for devnet

Also update the op-proposer options to account for a recent rename.

* op-e2e: Revert setting cannon prestate in devnetL1.json - its actually the alphabet prestate.  Deploy script dynamically loads the cannon prestate.

* op-challenger: Fix block number included in error message.

* op-challenger: Tweak error message

* op-challenger: Only ignore prestate mismatches, not RPC failures.
      70bd6234
    • Mark Tyneway's avatar
      contracts-bedrock: remove LegacyERC20ETH contract (#9472) · e7ff5eb6
      Mark Tyneway authored 
      * contracts-bedrock: remove LegacyERC20ETH contract

The `LegacyERC20ETH` is no longer used as part of the genesis
generation. Is a contract that only lives on OP Mainnet and is
no longer used since the bedrock upgrade. It is completely deprecated
at this point and there is no real reason to keep around its source
code since it isn't placed into modern genesis states. It has no
usage anymore and keeping it around only bloats the lines of code
in the contracts, increases the build time and increases the test
time.

* contracts-bedrock: fix build

* op-bindings: remove LegacyERC20ETH

No longer used

* contracts-bedrock: update gas snapshot
      e7ff5eb6
    • Joshua Gutow's avatar
      op-node,op-service: Add Fallback Beacon Client (#9458) · 39bc6f43
      Joshua Gutow authored 
      * op-node,op-service: Add Fallback Beacon Client

This splits out a very thin wrapper around the Beacon API into the
BeaconClient interface. This interface is then implement by two different
structs. The first is a simple wrapper around the HTTP Client. The second
is a FallBack Client which tries two different underlying clients.

This also a beacon archiver to be used as a fallback while still pulling most
of the relevant data from the beacon node.

* Try all clients in the pool
      39bc6f43
    • Adrian Sutton's avatar
      op-e2e: Extend timeout for waiting for claims when first running cannon (#9500) · 061f0b8b
      Adrian Sutton authored
      061f0b8b
    • Adrian Sutton's avatar
      op-e2e: Add e2e test for uploading sha256 and blob data (#9442) · a00a3a11
      Adrian Sutton authored 
      Also tests that fault proofs work with batches posted as blobs.
      a00a3a11
    • clabby's avatar
      feat(ctb): Remove `deletePendingWithdrawal` (#9498) · a7b55a89
      clabby authored 
      * Remove `deletePendingWithdrawals`

* semver
      a7b55a89
    • Khanh Hoa's avatar
      refactor(op-service, op-node): add missing stop ticker (#9474) · 57d43503
      Khanh Hoa authored 
      * refactor: add missing stop ticker

* chore: rollback
      57d43503
    • Sebastian Stammler's avatar
      log: Fix DynamicLogHandler to also capture derived handlers (#9479) · 32596f3e
      Sebastian Stammler authored
      32596f3e
    • Mark Tyneway's avatar
      contracts-bedrock: delete mainnet deployments (#9315) · 8cc6aec3
      Mark Tyneway authored 
      * contracts-bedrock: delete mainnet deployments

As part of https://github.com/ethereum-optimism/optimism/commit/6b1aa1e7de5d094954b6866f5605078b1ad81914
for some reason the `mainnet` directory was not deleted. This commit
deletes that directory as well. The source of truth for the deployments
is now in the `superchain-registry` repo.

When new contracts are deployed, their contract addresses can be found
there. Specific releases of smart contracts will contain the exact ABIs
for the deployed contracts at a release. These releases can be found
with git tags in the ethereum-optimism github repo.

* contracts-bedrock: commit in `deployments` directory

Future updates will delete this directory and change
the output directory for files like `.deploy`
      8cc6aec3
  3. 12 Feb, 2024 2 commits
  5. 11 Feb, 2024 1 commit
  7. 10 Feb, 2024 9 commits
  9. 09 Feb, 2024 15 commits
  11. 08 Feb, 2024 4 commits