Skip to content

Commit 1dde69f

Browse files
delken-azuroDelvin Kennedy
andauthored
update reward distribution description (#325)
Co-authored-by: Delvin Kennedy <delvinkennedy@D-K-Macbook-Air.local>
1 parent 651c64b commit 1dde69f

3 files changed

Lines changed: 32 additions & 18 deletions

File tree

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
# Reinforcement
22

3-
Reinforcement is the initial liquidity amount that is distributed among outcomes of a [Condition](/knowledge-hub/how-azuro-works/components/conditions)
4-
in accordance with the betting odds. It is set at the time of Condition creation and cannot be changed later.
3+
Reinforcement is the initial liquidity amount that is distributed among outcomes of a [Condition](/knowledge-hub/how-azuro-works/components/conditions) in accordance with the betting odds. It is set at time of Condition creation and cannot be changed later.
54

65
It is used to ensure potential payouts for bets where the funds received from other bets on the Condition are insufficient.
7-
Therefore, the reinforcement value also represents the maximum potential loss that the [Pool](/knowledge-hub/how-azuro-works/components/pools)
8-
can incur due to the Condition.
6+
Therefore, the Reinforcement amount also represents the maximum potential loss that the [Pool](/knowledge-hub/how-azuro-works/components/pools) can incur due to the Condition **at initial setup**.

pages/knowledge-hub/how-azuro-works/protocol-actors/bettors.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,4 @@ Do note that apps connected to the protocol are distinct and separate entities f
1212

1313
---
1414

15-
Bettors play an important role towards the functioning of Azuro prediction markets. Profit-motivated bettors seek out mispricings of sell-side odds (pushed by the [Data Provider](/knowledge-hub/how-azuro-works/protocol-actors/data-providers)) across Azuro prediction markets and place bets against it, adjusting onchain odds back to the free market equilibrium in the process.
16-
17-
Betting volume is what drives accurate probabilities in the first place. No bettors, no volume, no functioning prediction markets.
15+
Bettors play an important role towards the functioning of Azuro prediction markets. Profit-motivated bettors seek out mispricings of sell-side odds (pushed by the [Data Provider](/knowledge-hub/how-azuro-works/protocol-actors/data-providers)) across Azuro prediction markets and place bets against it, adjusting onchain odds back to its free market equilibrium.

pages/knowledge-hub/how-azuro-works/reward-distribution.mdx

Lines changed: 29 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -14,34 +14,52 @@ For LPs and Data Providers, after the completion of each [Condition](/knowledge-
1414

1515
## Apps (Frontends)
1616

17-
Apps' reward is paid monthly, separately for each chain.
17+
<Callout type="info">
18+
Visit [this](https://dune.com/queries/4361346/7319176) Dune query to view the historical month-by-month of our apps' reward calculation.
19+
</Callout>
20+
21+
Apps' reward is paid monthly, separately for each chain. Each app's final take-home reward will be the lower of its *NotionalReward* and the sum of its *SpreadRewardCap* for that month.
22+
23+
### SpreadRewardCap
1824

1925
<Formula>
2026
$$
2127
\begin{array}{c}
22-
\textit{AppReward} = 60\% \times \textit{AppRevenue} \\
23-
\textit{SpreadRewardCap} = 50\% \times \textit{Spread} \times \textit{BetSize} \\
28+
\textit{SRCb} = 50\% \times \textit{Spread} \times \textit{BetSize} \\
29+
\textit{SRCt} = \textit{SRCb1} + \textit{SRCb2} + ... + \textit{SRCbi} \\
30+
\\
31+
\\
32+
\text{where} \\
33+
\textit{SRC} \text{ denotes } \textit{SpreadRewardCap}, \\
34+
\textit{SRCb} \text{ represents the } \textit{SpreadRewardCap} \text{ for an individual bet}, \\
35+
\textit{SRCt} \text{ represents the sum of } \textit{SRCb} \text{ over a month's period}, \\
36+
\\
37+
\text{and} \\
38+
\textit{Spread} \text{ is the vig (aka margin) for an individual bet,} \\
39+
\textit{BetSize} \text{ is the amount (aka wager size) of an individual bet.}
2440
\end{array}
2541
$$
2642
</Formula>
2743

44+
### NotionalRevenue
45+
2846
<Formula>
2947
$$
3048
\begin{array}{c}
49+
\textit{NotionalReward} = 70\% \times \textit{AppRevenue} \\
50+
\\
51+
\\
3152
\text{where} \\
32-
\textit{AppReward} \text{ is not higher than } \textit{SpreadRewardCap}, \\
33-
\textit{Spread} \text{ is the vig (aka margin) for each particular bet,} \\
34-
\textit{BetSize} \text{ is the amount (aka wagered cryptocurrency) of each particular bet.}
53+
\textit{AppRevenue} \text{ is the protocol revenue that is attributed to a particular app}, \\
54+
\textit{NotionalReward} \text{ is the notional reward for a particular app before applying } \textit{SRC}.
3555
\end{array}
3656
$$
3757
</Formula>
3858

39-
4059
## DAO
4160

42-
The remaining rewards will be attributable to AzuroDAO, calculated by deducting all other rewards from the total monthly Pool Revenue.
61+
The remaining amount will be attributable to AzuroDAO, calculated by deducting all other rewards from the total monthly Pool Revenue.
4362

4463
<Callout type="info">
45-
LPs’, Data Providers’, and the DAO’s rewards can happen to be negative.
46-
Frontends’ rewards can be only positive or 0.
47-
</Callout>
64+
LP, Data Provider, and DAO rewards can happen to be negative in the event of Pool losses (caused by bettor outperformance). However, App rewards can be only positive or zero.
65+
</Callout>

0 commit comments

Comments
 (0)