Skip to content

Commit

Permalink
Merge pull request #299 from Azuro-protocol/delken-azuro-patch-3
Browse files Browse the repository at this point in the history
added links, made minor word changes
  • Loading branch information
Avvrik authored Nov 1, 2024
2 parents 022b010 + 18239bd commit 96f5d76
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ In contracts infrastructure, the Data Provider is represented as an address to w

Currently, the Data Provider is also responsible for resolving Conditions in good-faith, with AzuroDAO acting as the arbiter of last resort in case of disputes. For instance, Pinnacle (one of Azuro’s Data Providers) has published an extensive document outlining the general rules to which it intends to use as a basis to resolve markets (https://www.pinnacle.com/en/future/betting-rules).

Data Providers are required to put up collateral up to the total Reinforcement amount that they expect to use for the pricing of sell-side odds across involved prediction markets.
Data Providers are required to put up collateral up to the total [Reinforcement](/knowledge-hub/how-azuro-works/components/reinforcement) amount that they expect to use for the pricing of sell-side odds across all of their active markets.


<Callout type="feature">
Currently, data providers are still permissioned due to the critical nature of the role. Once the protocol reaches a certain level of maturity, we aim to open up the data provider role to the free market — permissionless data providers elected via AzuroDAO.
</Callout>
</Callout>

0 comments on commit 96f5d76

Please sign in to comment.