Update RPIP-53 with Appendix #182
Merged
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
xrchz
reviewed
May 2, 2024
RPIPs/RPIP-53.md
Outdated
|
|
||
| - Eligible claimers for Entry A and Entry B are both determined at the time of claiming. | ||
|
|
||
| Note that if this is the scenario at the time of claiming Entry A, then only B can claim Entry A. However, the rewards will go to A and C. B itself won't earn anything and it will have to pay for gas, so this situation only works trustlessly when the owner of B also owns C. |
There was a problem hiding this comment.
Why does C get node A's rewards?
There was a problem hiding this comment.
Looks like that's a mistake, thanks for the catch. Updated to reflect that B will get the RPL here.
xrchz
reviewed
May 2, 2024
xrchz
reviewed
May 2, 2024
xrchz
approved these changes
May 2, 2024
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 adds an appendix of how various unintuitive scenarios will play out in accordance with v10 (and in some cases, with vanilla Houston for posterity). Also adds a bit of clarity surrounding the ordering of nodes when assessed in the claimer construction.