Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong address for Challenger #1208

Open
Maar-io opened this issue Dec 31, 2024 · 1 comment
Open

Wrong address for Challenger #1208

Maar-io opened this issue Dec 31, 2024 · 1 comment

Comments

@Maar-io
Copy link

Maar-io commented Dec 31, 2024

The address 0x9BA6e03D8B90dE867373Db8cF1A58d2F7F006b3A for Challenger on Contract page for mainnet is actually System Config Owner address.

The EOA which is resolving games is 0xd22d93fe3341b7f5837ce83b57169c10f06ff0e0.

@sbvegan
Copy link
Collaborator

sbvegan commented Jan 3, 2025

Hey @Maar-io, thanks for opening this issue. The EOA that is resolving games is account that is associated with the op-challenger services that guards the fault proof system. This is different from the privileged role, also called the challenger: https://docs.optimism.io/chain/security/privileged-roles#challenger. I'm going to keep this issue open and add some clarification around the docs on the difference between these two roles. The information below is for our tech writers:


Description

There is confusion around the different accounts that are associated with the hot wallets that fund the op-challenger and the challenger role. We need to update the docs to clarify the difference.

Resources

Acceptance criteria

  • The different sections of the documentation that reference the challenger role and the op-challenger should have a description that separates the two concepts.

Action items

  1. Reach out to proofs support if you need information on understanding these two roles
  2. Open a PR to add this additional context to the docs
  3. Get a review from @proofs-support
  4. Get a peer review
  5. Merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants