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

Broken Ethereum committee change proof #181

Closed
tchataigner opened this issue Aug 22, 2024 · 0 comments · Fixed by #183
Closed

Broken Ethereum committee change proof #181

tchataigner opened this issue Aug 22, 2024 · 0 comments · Fixed by #183
Labels
bug Something isn't working ethereum Related to the Etheruem Light Client

Comments

@tchataigner
Copy link
Contributor

tchataigner commented Aug 22, 2024

While testing for the new bls crate commit, I noticed that both our benchmark and test for committee change proof generation seemed to be broken.

I do not get yet why they fail as they work up until commit c9293b3 (#165), and all that PR does is update deps to sphinx dev (sphinx#152, 93e4598).

The command ran were:

# Goes on forever
zk-light-clients/ethereum/light-client$ cargo +nightly-2024-08-13 nextest run --verbose --release --profile ci --all-features --package ethereum-lc --no-capture --run-ignored all -- proofs::committee_change::test

# Both proof test are failing with SIGSEV
zk-light-clients/ethereum/light-client$ RUST_LOG=debug cargo +nightly-2024-08-13 nextest run --verbose --release --profile ci --all-features --package ethereum-lc --no-capture --run-ignored all -- proofs::committee_change::test

I discovered it on the branch feature/update-bls-version that updates our deps to the latest update of the bls crate.

@tchataigner tchataigner added bug Something isn't working ethereum Related to the Etheruem Light Client labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ethereum Related to the Etheruem Light Client
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant