Skip to content

Commit 5d67bde

Browse files
AvvrikAvvrik
authored
Merge pull request #305 from Azuro-protocol/main
upd from main
2 parents c222e56 + df3879d commit 5d67bde

File tree

6 files changed

+19
-32
lines changed

6 files changed

+19
-32
lines changed

‎pages/contracts/live-client-core.mdx‎

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,17 @@
1-
import { PageHeadline, Callout } from 'components'
1+
import { Callout } from 'components'
22

3-
<PageHeadline
4-
title="ClientCore (Live betting)"
5-
subTitle="A Register Engine for the betting"
6-
/>
3+
# LiveCore
74

8-
"LiveCore" contract is designed to accept bets on sport events in real time and reserve payouts for them.
5+
LiveCore contract is designed to accept bets on sport events in real time and reserve payouts for them.
96
Bets are made according to the parameters (event, outcome, odds, amount) approved and signed by the bettor and by the Azuro backend.
107
Each LiveCore bet is "AzuroBet token" as in PrematchCore. The contract does not calculate odds,
118
it only checks the provided parameters and signatures.
129

13-
"LiveCore" contract checks the states of the events: creates new ones and resolves finished events. When the event ends
10+
LiveCore contract checks the states of the events: creates new ones and resolves finished events. When the event ends
1411
at a certain "resolve time", bets made later than the "resolve time" are possible - these bets are considered canceled
1512
and can be returned back to the players (players take back "LP.withdrawPayout()" canceled bets by themselves).
1613

17-
"LiveCore" is contract similar to “PrematchCore” does not store bet amounts and payments, it uses the “LP” contract:
14+
LiveCore is contract similar to PrematchCore does not store bet amounts and payments, it uses the “LP” contract:
1815
sends bets and reserves the amount for payments there.
1916

2017
A snapshot saving approach is used for canceled bets. In this way, bets are saved with time stamps and if bets are placed

‎pages/contracts/live-host-core.mdx‎

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,9 @@
1-
import { PageHeadline, Callout } from 'components'
1+
import { Callout } from 'components'
22

3-
<PageHeadline
4-
title="HostCore (Live betting)"
5-
subTitle="A Register Engine for the betting"
6-
/>
3+
# HostCore
74

85
The contract is responsible for registering and maintaining the life cycle of games and game conditions, and registers game conditions odds. Used to provide game information for various offchain interfaces.
96

107
<Callout type="warning">
118
This contract is at early development/test phase
12-
</Callout>
9+
</Callout>

‎pages/contracts/live-relayer.mdx‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,6 @@
1-
import { PageHeadline, Callout } from 'components'
1+
import { Callout } from 'components'
22

3-
<PageHeadline
4-
title="ClientCore (Live betting)"
5-
subTitle="A Register Engine for the betting"
6-
/>
3+
# Relayer
74

85
"Relayer" contract is intended for execution of prepared and signed (by bettor and by oracle) bets, and payment of relayer's fee.
96
Any "relayer" can send prepared bets using the `Relayer.betFor()` method.

‎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

‎pages/knowledge-hub/azur/azuro-dao.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ import { PageHeadline, Image, Callout } from 'components'
44

55
AzuroDAO is the protocol’s decentralized autonomous organization, with the mandate of safeguarding smart contract functions and ensuring the protocol’s continual going-concern. In contracts infrastructure, AzuroDAO is the owner of the Factory contract to which a part of the profit share is credited by LP after the completion of each Condition.
66

7-
In the context of Azuro prediction markets, AzuroDAO plays a critical role of being the arbiter of last resort for disputed event resolutions, as well as to elect qualified data providers into the set. Decisions are congregated and made via onchain voting, where voting power corresponds the amount of staked AZUR and staking duration, specified under vsAZUR tokenomics.
7+
In the context of Azuro prediction markets, AzuroDAO plays a critical role of being the arbiter of last resort for disputed event resolutions, as well as to elect qualified data providers into the set. Decisions are congregated and made via onchain voting, where voting power corresponds the amount of staked AZUR and staking duration, specified under [redacted].
88

99
As the project scales to steady-state, expect more features to be enshrined into the protocol. AzuroDAO will form the governance backbone of all these features — exact specifications to be disclosed closer to each feature’s release.
1010

@@ -14,4 +14,4 @@ The Schelling point token of AzuroDAO will always be AZUR. There will not be ano
1414

1515
## Become a contributor
1616

17-
We are excited to welcome new contributors to Azuro. You can submit your application via this link → https://azuro.typeform.com/contribute
17+
We are excited to welcome new contributors to Azuro. You can submit your application via this link → https://azuro.typeform.com/contribute

‎pages/knowledge-hub/how-azuro-works/protocol-actors/data-providers.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,9 @@ In contracts infrastructure, the Data Provider is represented as an address to w
1818

1919
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).
2020

21-
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.
21+
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.
2222

2323

2424
<Callout type="feature">
2525
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.
26-
</Callout>
26+
</Callout>

0 commit comments

Comments
 (0)