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

About Potential Front-running Problem of Challenge Function #4

Open
0xferit opened this issue May 5, 2022 · 0 comments
Open

About Potential Front-running Problem of Challenge Function #4

0xferit opened this issue May 5, 2022 · 0 comments
Labels
question Further information is requested

Comments

@0xferit
Copy link
Member

0xferit commented May 5, 2022

The challenge function can be front-run. This might be exploited by a challenger, who wants to grab the bounty of other challengers, or by the claimant itself, as a way to withdraw funds.

A challenge is not a surefire way to win a bounty as Kleros can rule against the challenge (the original challenger might be wrong, so the front-runner can lose money by attacking), but still, this attack possibility might be annoying and it's better if we patch.

One way to patch it is to introduce a commit and reveal scheme. Or we can ignore it because the attack does not look so promising, and as implementing a defense will be at the expense of a gas hike for regular usage, we can save gas by ignoring the attack.

@0xferit 0xferit added the question Further information is requested label May 5, 2022
@0xferit 0xferit moved this to Todo in PMW First Iteration May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant