Document PE Bounty and Bond Design #702
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
souradeep-das
commented
Sep 28, 2020
|
There could have been another approach, where without combining the values in struct, we try to compare and return the max value between the bond and bounty, but I think this is cleaner? |
thec00n
reviewed
Sep 29, 2020
thec00n
reviewed
Sep 29, 2020
thec00n
reviewed
Sep 29, 2020
thec00n
reviewed
Sep 29, 2020
thec00n
reviewed
Sep 29, 2020
Co-authored-by: thec00n <thec00n@fork.at>
Co-authored-by: thec00n <thec00n@fork.at>
Co-authored-by: thec00n <thec00n@fork.at>
kevsul
reviewed
Sep 29, 2020
Co-authored-by: Kevin Sullivan <4653170+kevsul@users.noreply.github.com>
thec00n
reviewed
Oct 9, 2020
thec00n
reviewed
Oct 9, 2020
thec00n
reviewed
Oct 9, 2020
thec00n
reviewed
Oct 9, 2020
thec00n
reviewed
Oct 9, 2020
Co-authored-by: thec00n <thec00n@fork.at>
boolafish
reviewed
Oct 21, 2020
| **_On succesfull challenge:_** | ||
| *Bond -> from `Exit Game Contract` to `Challenger`* | ||
|
|
||
| The **Exit Processor** gets the bounty as a reward for processing an exit. The cost of processing multiple exits from the exit queue at once is less than the cost of processing them individually. For simplicity and to save gas however, the **Process Exit Bounty** amount associated with each exit is given out to the **Exit Processor**. |
There was a problem hiding this comment.
For simplicity and to save gas however,
I am a bit lost on what this part is aiming to explain actually 😅 where it is simplifying and saving gas?
There was a problem hiding this comment.
Thanks! I think it will be better to point out the stacking exits by the exit processor for more incentives part here instead, since saving gas is on their(the exit processors) side. cc @thec00n
There was a problem hiding this comment.
updated ddcb22f
Co-authored-by: boolafish <boolafish945@gmail.com>
boolafish
approved these changes
Oct 23, 2020
boolafish
approved these changes
Oct 23, 2020
kevsul
approved these changes
Oct 23, 2020
Co-authored-by: Kevin Sullivan <4653170+kevsul@users.noreply.github.com>
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.
No description provided.