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

Sort attester slashing indices to avoid arbitrary ordering #1126

Merged
merged 1 commit into from
May 27, 2019

Conversation

michaelsproul
Copy link
Contributor

Closes #1125

@dankrad
Copy link
Contributor

dankrad commented May 27, 2019

This looks like a good solution. Have we checked if we are iterating over dicts/sets anywhere else where it could cause problems?

@djrtwo
Copy link
Contributor

djrtwo commented May 27, 2019

Nice catch!

@dankrad I have a PR in the works that turns some of the things in the spec to sets to make it explicit that order does not matter. I'll do the opposite check too to make sure that order is preserved where necessary.

@djrtwo djrtwo merged commit 7327f12 into ethereum:dev May 27, 2019
@michaelsproul michaelsproul deleted the sort-attester-slashings branch May 27, 2019 22:45
@michaelsproul
Copy link
Contributor Author

michaelsproul commented May 28, 2019

Thanks :) If there's going to be a v0.6.2 release could it include this patch?

@djrtwo
Copy link
Contributor

djrtwo commented May 31, 2019

Releasing it in v0.6.3!

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.

Attester slashings are done in an arbitrary order and do not commute
3 participants