Skip to content

Commit c83babc

Browse files
authored
Merge pull request #301 from Azuro-protocol/delken-azuro-patch-3-1
reworded some dispute mechanisms, fixed minor grammatical errors
2 parents c928511 + 18dc486 commit c83babc

File tree

1 file changed

+5
-9
lines changed

1 file changed

+5
-9
lines changed

pages/contracts/safe-oracle.mdx

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,25 +13,21 @@ import { PageHeadline, Callout } from 'components'
1313
This contract does not affect the logic of a Pool's contracts
1414
</Callout>
1515

16-
The SafeOracle contract allows to create and resolve [Conditions](/knowledge-hub/how-azuro-works/components/conditions) on any
16+
The SafeOracle contract allows data providers to create and resolve [Conditions](/knowledge-hub/how-azuro-works/components/conditions) on any
1717
[PrematchCore](/contracts/prematch-core) contract, with an option for any user to dispute the result. If the result is
1818
disputed or not provided within the specified period set at the time of Condition creation,
19-
[Azuro DAO](/knowledge-hub/azur/azuro-dao) will provide the result.
19+
[AzuroDAO](/knowledge-hub/azur/azuro-dao) will step in to resolve the Condition.
2020

2121
The SafeOracle's logic guarantees timely and accurate results for created Conditions or cancels them if the correct
2222
result is impossible to determine. This eliminates the risk of fraud against bettors by the
2323
[data provider](/knowledge-hub/how-azuro-works/protocol-actors/data-providers) and the possibility of their funds being locked due to the data
2424
provider's failure to provide the result.
2525

26-
When creating a Condition through SafeOracle, the data provider places a fixed amount as collateral, which will be
27-
returned to them if their result is timely and accurate. Otherwise, the collateral will be used as a reward for Azuro DAO
28-
and optionally the disputant.
26+
Each data provider will have a certain amount of fixed collateral placed to the protocol, depending on the amount of [Reinforcement](/knowledge-hub/how-azuro-works/components/reinforcement) that they intend to draw upon from the singleton LP at any one time. This collateral doubles as slashable assets in the case of false resolutions, if deemed by AzuroDAO.
2927

30-
A dispute can be opened by a disputant only within a limited timeframe after the data providers result for the Condition.
31-
After this period, the result will be accepted and executed on the LP contract. When opening a dispute,
32-
the disputant also places a collateral, which is half of the data provider's collateral. If the DAO determines that
33-
the result is incorrect, the disputant will double their collateral; otherwise, they will lose their funds.
28+
Each market's settlement will have a short delay post-resolution to allow for members of AzuroDAO to raise a dispute if necessary. Disputants will be required to place a small bond to deter griefing attacks to the protocol's dispute mechanism.
3429

30+
If the data provider's original resolution is determined to be accurate, the disputant will lose their bond to the data provider. Conversely, a portion of the data provider's collateral will be slashed and redistributed to the disputant, while the AzuroDAO resolves the market to the correct outcome and renounces the data provider's ownership of the associated [Pool](/knowledge-hub/how-azuro-works/components/pools ownership) (ejected from the set). Amount of slashed collateral will scale relative to the amount at risk of the disputed market.
3531

3632
### Reference
3733

0 commit comments

Comments
 (0)