-
Notifications
You must be signed in to change notification settings - Fork 145
SIMD-0204: Slashable event verification #204
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
base: main
Are you sure you want to change the base?
Conversation
67179d1
to
061cf5f
Compare
339aa9a
to
4f69f15
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really great work! Most of my comments are minor nits for clarification
2. Verify that the program account | ||
`8sT74BE7sanh4iT84EyVUL8b77cVruLHXGjvTyJ4GwCe` has a verified build hash of | ||
`<FILL IN AFTER IMPLEMENTATION>` [\[1\]](#notes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't typically do this when upgrading a program via feature gate, but I like it a lot! We should definitely start
5cf8254
to
0d13374
Compare
250711c
to
8ed650f
Compare
8ed650f
to
6fd44fa
Compare
bb895a1
to
e9b7168
Compare
@joncinque @lidatong this should be ready for final review. |
Proposal to deploy a program that records and verifies slashable events on chain
This proposal does not modify any stakes or rewards, the program will only verify and record infractions.
At the moment we only verify duplicate block violations, but a future SIMD will add voting violations as well