optimism-java / optimism-java

optimism-java / optimism-java


Hildr implements the OP Stack consensus client, with core functionalities developed according to the Rollup Node spec, essentially equivalent to the op-node (excluding the sequencer) functionalities.

Op-besu implements the OP Stack execution client, with core functionalities developed according to the Execution Engine spec, essentially equivalent to the op-geth functionalities.

Prize distribution and scoring

  • Total Prize Pool: 117,362 OP Tokens

  • Primary Prize Pool: 111,362 OP Tokens

  • 6000 OP tokens is reserved for Low Severity findings. These reports are judged based on quality and reviewers are then ranked from 1st to 5th for the purpose of prize allocation.

    • 1st: 3000 OP
    • 2nd: 1500 OP
    • 3rd: 800 OP
    • 4th: 350 OP
    • 5th: 350 OP
  • Scoring described in the competition scoring page.

  • Findings Severities described in detail on our docs page.

Severity definitions

In addition to the standard severity matrix that applies to the findings below are the categories that the findings may classify into:

  • High Severity: Violation of the OP Stack protocol leading to chain forks, as well as serious security issues causing the program to be controlled, or serious performance issues causing the program to fail to operate normally
  • Medium Severity: General performance issues lead to slow program execution, which will not cause deviations in protocol implementation that result in chain forks, and lower-level security issues.
  • Low Severity & Informational: Errors in documentation comments or test code, and optimizable code that does not affect functionality and performance

Documentation

  • Op-besu is a fork of Hyperledger Besu, you could read the document here. And we have a fork diff site, you can read what codes we modified.

Hildr Directory Overview:

  • cli: Command line interface features.
  • config: Configuration file parsing features.
  • derive: Features related to OP Stack derivation.
  • driver: Polling L1 and triggering derivation features.
  • engine: Execution engine interaction features.
  • exceptions: Definitions for various exceptions.
  • l1: Features related to polling L1.
  • network: P2P unsafe block features.
  • rpc: Rollup node RPC interface features.
  • runner: Main program entry point.
  • telemetry: Metrics and telemetry features.
  • types: Data class features.
  • utilities: Helper class features.
  • Hildr: Main method entry point.

Scope

Hildr

op-besu

Build Instructions

  • Op-besu: you could read the doc here or Hyperledger Besu doc .
  • Hildr: you could read the doc here or readme.

Basic POC Test:

  • Op-besu: All the unit tests or integration tests can be referenced. You can find them in the test source dir. For Example.
  • Hildr: All the unit tests can be referenced. You can find them in the test source dir. For Example.

Out of scope

  • Op-besu is a fork of Hyperledger Besu, we only modified around 4k LOC, you could read the fork diff site , only code that affects the op-besu functionality is considered within scope, other things are considered out of scope
  • Hildr currently only implements the verifier function and does not implement the sequencer function. The sequencer part of the code is not fully implemented and is not within the scope.

Contact Us

For any issues or concerns regarding this competition, please reach out to the Cantina core team through the Cantina Discord.

Summary

Status

Reviewing Escalations

Total reward:

117,362 OP

Findings submitted:

363

Start date:

7 Oct 2024 8:00pm (local time)

End date:

28 Oct 2024 8:00pm (local time)