1. 15 May, 2024 3 commits
  2. 14 May, 2024 11 commits
  3. 13 May, 2024 9 commits
  4. 12 May, 2024 1 commit
    • refcell's avatar
      feat(op-dispute-mon): L2BlockNumberChallenged Support (#10451) · bde6a96e
      refcell authored
      * feat(op-dispute-mon): L2BlockNumberChallenged dispute monitor support
      
      feat(op-dispute-mon): query for the l2 block number through the game metadata call
      
      fix(op-dispute-mon): query for the l2 block number through the game metadata call
      
      fix(op-dispute-mon): query for the l2 block number through the game metadata call
      
      * fix(op-dispute-mon): block challenge check
      
      * fix(op-dispute-mon): use agreement and metrice
      
      * op-dispute-mon: Separate l2 challenge metric (#10483)
      
      * op-dispute-mon: Consider l2 block number challenged when forecasting but don't make it a new game status.
      
      Add a separate metric to report the number of successful L2 block number challenges.
      
      * op-challenger: Remove unused blockNumChallenged field from list-games info struct
      
      * op-dispute-mon: Consider l2 block challenger in expected credits. (#10484)
      
      * feat(op-dispute-mon): Update L2 Challenges Metrics (#10492)
      
      * fix: change the l2 challenges to tha gauge vec
      
      * fix: consistent metric labels
      
      ---------
      Co-authored-by: default avatarrefcell <abigger87@gmail.com>
      
      ---------
      Co-authored-by: default avatarAdrian Sutton <adrian@oplabs.co>
      bde6a96e
  5. 11 May, 2024 5 commits
  6. 10 May, 2024 11 commits
    • Mark Tyneway's avatar
      contracts-bedrock: portal opaque data test (#10443) · 7daf06d8
      Mark Tyneway authored
      * contracts-bedrock: add deposit event coverage
      
      Adds deposit event differential coverage for the two
      different places where the deposit tx event exists.
      This ensures that a valid event ends up getting emitted.
      Also modularizes the code for serializing the event so that
      there are not footguns when computing the "opaque data".
      
      * contracts-bedrock: revert diff to portal
      
      Removes the diff to the portal, perhaps we want it
      but test still passes without it
      
      * contracts-bedrock: lint
      
      * test: improve
      
      * tests: update
      
      * tests: fixup
      
      * semver: fix
      
      * lint: fix
      7daf06d8
    • Maurelian's avatar
      Test setup results of DeployOwnership script (#10397) · 6c6dc18a
      Maurelian authored
      * ctb: Test ownership setup scripts
      
      * ctb: Add nested config of modules
      
      * Add guard and module checks
      
      * Update packages/contracts-bedrock/scripts/DeployOwnership.s.sol
      Co-authored-by: default avatarMatt Solomon <matt@mattsolomon.dev>
      
      ---------
      Co-authored-by: default avatarMatt Solomon <matt@mattsolomon.dev>
      6c6dc18a
    • Hteev Oli's avatar
      cannon: fix a typo in fuzz test (#10488) · 351f6601
      Hteev Oli authored
      351f6601
    • ids's avatar
      Update conf_depth.go (#10487) · 164b3d2f
      ids authored
      Don't apply the conf depth if l1Head is empty (as it is during the startup case before the l1State is initialized)
      164b3d2f
    • Mark Tyneway's avatar
      op-chain-ops: update bindings import (#10490) · 03f6bd88
      Mark Tyneway authored
      Updates another import to reference local bindings
      rather than global bindings. This test isn't
      going to need to worry about having its bindings be
      updated.
      03f6bd88
    • Mark Tyneway's avatar
      op-service: decouple from `op-bindings` (#10491) · 58fe52b7
      Mark Tyneway authored
      This moves the ERC20 bindings that the `op-service` tests
      depend on into the `test` package that already exists.
      This ensures that these bindings can always exist safely and
      be used as part of the tests.
      58fe52b7
    • Mark Tyneway's avatar
      op-proposer: update test to use local bindings (#10473) · bbe7d14a
      Mark Tyneway authored
      Updates a single import to use the `op-proposer` bindings
      instead of the global monorepo bindings. The big consumer
      of the bindings after this are `op-e2e` and some tests
      in `op-service`.
      bbe7d14a
    • Adrian Sutton's avatar
      op-challenger: Fix highest_acted_l1_block metric (#10485) · 9a22b09e
      Adrian Sutton authored
      Completed games weren't updating their latest acted block because they don't get scheduled which meant the metric always reported 0.
      9a22b09e
    • Adrian Sutton's avatar
      op-dispute-mon: Ensure a zero value is set for sufficient/insufficient labels (#10481) · 2d09010b
      Adrian Sutton authored
      If the collateral for a DelayedWETH contract is sufficient and then becomes insufficient, we need to zero out the metric with the sufficient label and set the values on the insufficient labelled version.
      2d09010b
    • Inphi's avatar
      Fix makefile fuzz targets on osx (#10476) · 48393a6a
      Inphi authored
      48393a6a
    • Mark Tyneway's avatar
      op-chain-ops: decouple from bindings (#10466) · 4dc6aa8e
      Mark Tyneway authored
      * op-chain-ops: decouple from bindings
      
      Another commit that removes bindings from `op-chain-ops`.
      The entire repo is very close to being completely decoupled
      from having a global set of bindings. This does have a little
      bit of code duplication, but it generally results in a more
      simple layout.
      
      Both the `crossdomain` and `upgrades` package end up with their
      own `bindings` package. The `crossdomain` package is mostly
      legacy but the `indexer` still depends on it. The `indexer`
      is in maintenance mode, after reth exex it makes a lot of sense
      to build indexers directly into reth. The `crossdomain` package
      uses the bindings to migrate and serialize L1 to L2 cross domain
      messages. These bindings never need to be updated.
      
      The `upgrades` package has a justfile added that can be used to
      regenerate the bindings. This makes it easier to generate bindings
      based on a specific release. Previously the `upgrades` bindings
      were coupled in a strange way and backwards compatibility
      hacks needed to exist. Now the team working on upgrades can update
      the bindings however they want so the proper upgrade can easily
      be generated.
      
      * upgrades: error case
      
      Since the AddressList doesn't have the `DisputeGameFactory`
      yet, it cannot be pulled into the upgrade scripts. Instead
      return an error so that we MUST update it.
      
      https://github.com/ethereum-optimism/superchain-registry/blob/110e744c97b4873384ad2da365c281639fc0668e/superchain/superchain.go#L194
      4dc6aa8e