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.

Sign up for GitHub

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

Jump to bottom

When moving between sync committee periods, require next_sync_committee to be provided #410

Closed
srdtrk opened this issue Mar 17, 2025 · 0 comments · Fixed by #415
Closed

When moving between sync committee periods, require next_sync_committee to be provided #410

srdtrk opened this issue Mar 17, 2025 · 0 comments · Fixed by #415
Assignees
@srdtrk
Labels
audit ethereum-light-client Issues related to the 08-wasm ethereum light client

Comments

@srdtrk
Copy link
Member

srdtrk commented Mar 17, 2025

Internal audit: We should disallow light client updates that move us from a sync period to the next without also providing the next_sync_committee
@srdtrk srdtrk added audit ethereum-light-client Issues related to the 08-wasm ethereum light client labels Mar 17, 2025
@github-project-automation github-project-automation bot moved this to Backlog in IBC Mar 17, 2025
@srdtrk srdtrk mentioned this issue Mar 17, 2025
Merged
6 tasks
@srdtrk srdtrk self-assigned this Mar 17, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in IBC Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@srdtrk srdtrk

Labels
audit ethereum-light-client Issues related to the 08-wasm ethereum light client
Projects
IBC
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

imp: added more assertions in verify_header cosmos/solidity-ibc-eureka
1 participant
@srdtrk