-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add notes about disputes #75
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@Chralt98 Can you take a quick peek at this and tell me if this is still required or if there's any overlap? |
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.
I mean we still offer authorized markets on the polkadot js and ultimately in our protocol for main-net. However the decentralised court system should be fully controlling the dispute resolution by the time it is applied to the main-net. So, I think this deprecated functionality shouldn't be mentioned in the documentation.
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.
Should we mention here that the advisory committee can close markets early?
I am also currently wondering if we need this, if we have the more advanced feature of closing markets early (with fat finger protection).
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.
I mean we still offer authorized markets on the polkadot js and ultimately in our protocol for main-net. However the decentralised court system should be fully controlling the dispute resolution by the time it is applied to the main-net. So, I think this deprecated functionality shouldn't be mentioned in the documentation.
Authorized is not deprecated though.
@@ -21,6 +21,11 @@ platform. It is allowed to make the following decisions: | |||
- Reject advised markets if they are deemed valid (requires majority approval) | |||
- Close markets (requires two-thirds approval) or destroy markets (requires full | |||
approval) which are in gross violation of our rules of conduct | |||
- Resolve disputes for markets with the [Authorized] dispute mechanism |
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.
- Resolve disputes for markets with the [Authorized] dispute mechanism |
|
||
<!-- Links --> | ||
|
||
[authorized]: ./using-zeitgeist-markets.md#disputes |
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.
<!-- Links --> | |
[authorized]: ./using-zeitgeist-markets.md#disputes |
Every time a report is submitted (by the oracle or a stand-in), the market is | ||
not resolved for another 24 hours. During this period of time, other users can | ||
submit a _dispute_ if they believe that the report is incorrect. | ||
When a report is submitted (by the oracle or a stand-in), the market is not |
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.
Is the stand-in the outsider
? Can we avoid naming conflicts here?
resolved for a certain window of time called the _dispute period_. During this | ||
period of time, other users can submit a _dispute_ if they believe that the | ||
report is incorrect. To do so, they stake a certain amount of ZTG, the _dispute | ||
bond_ and report the outcome they believe to be correct (the _suggestion_). |
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.
bond_ and report the outcome they believe to be correct (the _suggestion_). | |
bond_. |
How the dispute is resolved depends on what _dispute mechanism_ was selected | ||
during market creation. The currently available dispute mechanisms are: |
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.
How the dispute is resolved depends on what _dispute mechanism_ was selected | |
during market creation. The currently available dispute mechanisms are: | |
How the dispute is resolved depends on the [decentralized court] _dispute mechanism_. |
- _Authorized_: After the market has been disputed, the [Advisory Committee] | ||
decides which outcome the market will resolve to. | ||
- _[Decentralized Court]_ (currently disabled): A group of randomly selected | ||
jurors vote secretly to find a [Schelling point] among the market's outcomes, | ||
which is then used as the resolved outcome. |
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.
- _Authorized_: After the market has been disputed, the [Advisory Committee] | |
decides which outcome the market will resolve to. | |
- _[Decentralized Court]_ (currently disabled): A group of randomly selected | |
jurors vote secretly to find a [Schelling point] among the market's outcomes, | |
which is then used as the resolved outcome. | |
In short: A group of randomly selected jurors vote secretly to find a [Schelling point] among the market's outcomes, which is then used as the resolved outcome. |
I didn't check the non-modified lines of this file. I think if we just mention court as the dispute mechanism we are fine for the future, because why mentioning (soon) deprecated code? |
Co-authored-by: Chralt <chralt.developer@gmail.com>
Just getting the ball rolling on getting the docs up to speed.