Challenger Component

🔐 Challenger Component: Upholding Integrity in Orb3

The Challenger plays a pivotal role as a trusted entity within the Orb3 ecosystem. Its primary responsibility is to ensure the integrity and authenticity of assertions made within the Orb3 rollup protocol.

Key Responsibilities of the Challenger:

BLS Key-Pair Creation: The Challenger starts by creating a BLS key-pair, a crucial step for ensuring secure and verifiable transactions within the network 🔑.
Key Registration with the Referee: After generating the key-pair, the Challenger registers the public key with the Referee Smart Contract. This registration is essential for the Referee to recognize and validate the Challenger’s actions and signatures 📝.
Signing Assertions: When a validator in the Orb3 rollup protocol makes an assertion, the Challenger's role is to sign this assertion using its private key. This signature is a testament to the legitimacy and accuracy of the assertion ✍️.
Submission and Verification: The signed assertion is then submitted to the Referee, which verifies the signature. The Referee's verification process is critical for maintaining the integrity of the network and ensuring that each assertion is valid and trustworthy.
Recording as a Challenge: Once verified, the signature is recorded by the Referee as a challenge associated with the particular assertion. This challenge acts as a marker of authenticity and integrity for the assertion within the network 🌐.

Through these processes, the Challenger Component significantly contributes to the security and trustworthiness of the Orb3 network. It ensures that all assertions made in the Orb3 rollup protocol are accurately validated, thereby maintaining the overall integrity of the ecosystem.

PreviousReferee Smart Contract NextKey

Last updated 1 year ago

Was this helpful?

Key Responsibilities of the Challenger:

BLS Key-Pair Creation: The Challenger starts by creating a BLS key-pair, a crucial step for ensuring secure and verifiable transactions within the network 🔑.

Key Registration with the Referee: After generating the key-pair, the Challenger registers the public key with the Referee Smart Contract. This registration is essential for the Referee to recognize and validate the Challenger’s actions and signatures 📝.

Signing Assertions: When a validator in the Orb3 rollup protocol makes an assertion, the Challenger's role is to sign this assertion using its private key. This signature is a testament to the legitimacy and accuracy of the assertion ✍️.

Submission and Verification: The signed assertion is then submitted to the Referee, which verifies the signature. The Referee's verification process is critical for maintaining the integrity of the network and ensuring that each assertion is valid and trustworthy.

Recording as a Challenge: Once verified, the signature is recorded by the Referee as a challenge associated with the particular assertion. This challenge acts as a marker of authenticity and integrity for the assertion within the network 🌐.