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

fix: Fix Claim Verification Failing Issue and Lighthouse Issue #4

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

jjtny1
Copy link
Collaborator

@jjtny1 jjtny1 commented Feb 11, 2025

Claim verifications are currently broken producing the following output:

INFO [02-10|18:43:36.907] Derivation complete: no further L1 data to process
INFO [02-10|18:43:36.907] Derivation complete: no further data to process
INFO [02-10|18:43:36.907] Derivation complete                      head=825c01..9963f1:42
INFO [02-10|18:43:36.918] Validating claim                         output=11ff6c..59ef98 claim=e18264..bc8dab
CRIT [02-10|18:43:36.918] Application failed                       err="invalid claim: claim: 0xe18264e7c31daab79e4291dc1fb0268edc74daf849e66ea6c92ad26f48bc8dab actual: 0x11ff6c7cb6a7e02ba49301870e91d169d8c94a0685d4bda91cd3afd79459ef98"

This is because we are not setting the holocene timestamp and it defaults to 0 (aka active at genesis) but our custom defined config does not pass it onwards to op-program. So op-program runs into an error when attempting to run it's derivation (it expects holocene data but doesnt get it)

In addition, lighthouse is currently broken, so using teku instead: ethpandaops/optimism-package#160

@jjtny1 jjtny1 requested a review from BrianBland February 11, 2025 21:40
@jjtny1 jjtny1 merged commit 6db8eb8 into main Feb 12, 2025
0 of 2 checks passed
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

Successfully merging this pull request may close these issues.

2 participants