Forced exits for offline nodes via keeper mechanism #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This seems to be a more-fleshed out subset of RPIP-44. Is there a particular benefit to breaking this out, or should some of the fleshing out be ported instead? |
|
I wasn't sure what was happening with RPIP-44 since it doesn't specify a mechanism, so I just wrote down my complete idea here. If you want to re-assign RPIP-44 to point to this doc that's ok with me, or you can always keep the other one if it's going in a different direction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposal outlines one way to use EIP-7002 to improve Rocket Pool. Specifically, I propose a keeper mechanism to incentivize all users to keep offline nodes accountable.