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(contracts): challenger edge case to avoid multiple slashing events for the same commitment #248

Open
Tracked by #259
merklefruit opened this issue Sep 30, 2024 · 0 comments
Assignees
Labels
C: smart-contracts Component: smart contracts T: bug Type: Bug

Comments

@merklefruit
Copy link
Collaborator

Discussion here: #239 (comment)

The problem is on how the commitments and challenges are indexed and stored.
There are different ways in which this can be solved, but this shouldn't block the current milestone.

@merklefruit merklefruit added C: smart-contracts Component: smart contracts T: bug Type: Bug labels Sep 30, 2024
@merklefruit merklefruit changed the title fix(challenger): edge case to avoid multiple slashing events for the same commitment fix(contracts): challenger edge case to avoid multiple slashing events for the same commitment Sep 30, 2024
@merklefruit merklefruit self-assigned this Oct 1, 2024
@mempirate mempirate added this to the v0.4: Holesky 2 milestone Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: smart-contracts Component: smart contracts T: bug Type: Bug
Projects
None yet
Development

No branches or pull requests

2 participants