GIP-0080: Optimistic EBO #53
Conversation
|
(Edited the PR title to show the GIP number) |
|
|
||
| - Any staked actor can propose an update for the EBO, which is published in a contract and remains open for a set period to allow for potential disputes. | ||
| - Any staked actor can also challenge the proposed update. If a dispute arises, the initial proposal is discarded, and a new one can be submitted. | ||
| - If a dispute occurs, the resolution mechanism is triggered, and the winner of the dispute will receive the counterparty’s bond as a reward. |
There was a problem hiding this comment.
To avoid certain attack vectors, this should be not the full bond, but half of it?
There was a problem hiding this comment.
Which attack vectors? What do we do with the other half?
gips/0080-optimistic-ebo.md
Outdated
| - After each dispute, the original update gets deleted and can be answered again, even before resolution. This option makes the process quicker for the requestor. This answer can be disputed using the same method as described above. | ||
| - An honest proposer will be rewarded more for the won resolution than the original update. | ||
| - Disputers are incentivized to post the new answer, as they have already computed the query. | ||
| - The payment from the requester will end up going to the proposer with the correct answer |
There was a problem hiding this comment.
Term 'requester' is used just twice (with different spellings) and not defined. Is the requester the dispute raiser (might be simpler to say disputer)?
I believe that this should not be the entire payment.
There was a problem hiding this comment.
The requester is the one who requests data from Prophet and also sets the rewards for proposers to submit responses. The disputer monitors the proposals and challenges them if they are invalid.
|
|
||
| - **Bond threshold**: The amount of stake that triggers a call to the Arbitrator (virtual bond in the escalation system), set at 100K GRT. | ||
| - **Round**: The maximum number of rounds a dispute can escalate, set at 5. | ||
| - **Min Bond**: Minimum amount required for five rounds of escalations to reach the Bond threshold, set at 11111 GRT. |
There was a problem hiding this comment.
Not sure if I missed it, how much higher does bond need to be relative to previous bond? (Or is that in Prophet docs?)
There was a problem hiding this comment.
It's a little confusing and I'm rewriting this section.
MinBond is the amount you need to initiate a dispute. Then the proposers must overtake the minbond by doubling the bond until the proposer or disputer stops answering or the total amount bet exceeds the bond threshold and calls the arbitrator. In this case it would look like this:
Round 0 - (start dispute): 11111
Round 1- proposer 22222
Round 2- disputer 22222
Round 3- proposer 22222
Round 4- disputer 22222
Round 5- proposer 22222 -> call arbitrator
There was a problem hiding this comment.
@RembrandtK The bond gets increased by 1 bond unit (configured in the request) for every escalation. So if we set 11111 GRT as the bond, every escalation increases it by that amount
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
Co-authored-by: Rembrandt Kuipers <[email protected]>
GIP-0080: Implement Optimistic EBO
This PR introduces the Optimistic Epoch Block Oracle (EBO), replacing the current EBO with a decentralized, optimistic oracle design outlined in GIP-0080.
Key Changes:
This update enhances security and aligns with The Graph's goal of progressive decentralization.