-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
28 changed files
with
144 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
{ | ||
"overview": "Overview", | ||
"wave1": "Wave #1" | ||
"wave1": "Wave #1", | ||
"wave2": "Wave #2" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,15 @@ | ||
import { PageHeadline, Formula, Callout } from 'components' | ||
import { Formula, Callout } from 'components' | ||
|
||
# The Azuro Waves | ||
# Azuro Waves | ||
|
||
<Callout type="feature"> | ||
Also referred to as “Community Airdrop 2” | ||
The Azuro Waves program is the successor to [Azuro Score](/knowledge-hub/airdrops/azuro-score/overview). | ||
</Callout> | ||
|
||
## About the Azuro Waves | ||
## Overview | ||
|
||
- The distribution of $AZUR will come in Waves and will be 100% linear towards the points accrued by each address. | ||
- The Waves program introduces “Levels” which give point multipliers. This means that all points earned by the eligible activities (which will be 100% transparent), will be multiplied by the level in the Wave which you have. | ||
- Conditions for next waves may change but changes will never be retroactive. There will always be clarity about how points work and how $AZUR will be distributed from the beginning of each Wave. | ||
|
||
**For information about Wave 1, go to [Wave 1](/knowledge-hub/airdrops/azuro-waves/wave1)** | ||
**Wave 2 is currently ongoing. Click [here](/knowledge-hub/airdrops/azuro-waves/wave2) for more information on the program.** |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
import { Formula, Callout } from 'components' | ||
|
||
# Wave #2 | ||
|
||
- Start of Wave 2 → 00:00:00 UTC November 18th, 2024 | ||
- End of Wave 2 → 23:59:00 UTC December 25th, 2024 | ||
- **Total airdrop reward → TBC** | ||
|
||
<Callout type="info"> | ||
Airdrop reward per user = | ||
\{Total airdrop reward\} * ( \{User wave points\} / \{Total wave points\} ) | ||
</Callout> | ||
|
||
## Points rules | ||
|
||
| Activity | Formula | | ||
| --- | --- | | ||
| [Placing Bets](https://azuro.org/ecosystem) | Х points = \{Bet sum\} * min( \{Odds\}; 10) / 5<br />e.g. 1 point = \$2.5 bet at odds of 2 (European odds format) | | ||
| [Liquidity Provision](https://azuro.org/app/liquidity) | Discontinued | | ||
| [DEX LP'ing](https://azuro.org/app/dex-farming) | Discontinued | | ||
| [\$AZUR Staking](https://azuro.org/app/staking)<br />(excl. unbonding) | 1 point = 1 000 AZUR staked/day | | ||
| Ecosystem support activities | Ad-hoc. To be announced separately whenever such rewards are to become available. | | ||
|
||
All points are credited once a day. A minimum holding period of 24 hours is required for the deposits to qualify for the points. | ||
|
||
Points awarded for betting activity will be credited after 100-300 blocks from the time the bet was placed. All bets placed during the Wave period will be included, even if their outcome and resolve date occurs after the end of the Wave period. | ||
|
||
## Points multipliers | ||
|
||
### Levels multiplier | ||
|
||
| Level ID | Level name | Level multiplier | Points needed | | ||
| --- | --- | --- | --- | | ||
| 0 | Mist | | 0 | | ||
| 1 | Sky | x1.1 | 100 | | ||
| 2 | Blue | x1.2 | 200 | | ||
| 3 | Ultramarine | x1.3 | 500 | | ||
| 4 | Bright | x1.4 | 1 200 | | ||
| 5 | Brilliant | x1.6 | 2 500 | | ||
| 6 | Royal | x2 | 6 000 | | ||
|
||
In Wave #2, points that count towards levels multiplier can only be earned from AZUR staking. To illustrate, if you have 650 points from AZUR staking and 5 000 points from betting activities, your levels multiplier will be Ultramarine (x1.3). | ||
|
||
Your weekly points will be multiplied by the multiplier associated with your acquired level at that week. The higher your acquired level, the higher your multiplier! | ||
|
||
Upon the conclusion of each Wave period, your acquired level will move down one tier for the next Wave. For example, if you have the Ultramarine level at the end of Wave 1, then you will start from the Blue level for Wave 2. | ||
|
||
<Callout type="warning"> | ||
If you do not see your level in the Waves tab in the Azuro App, make sure to click the ENHANCE button. You can do this at any stage within the Wave. | ||
However, if you never do it and the Wave ends - you will not have any Level Multiplier points. | ||
</Callout> | ||
|
||
### Leaderboard multiplier | ||
|
||
Making it into the weekly leaderboard gives you point multipliers (applicable to the points you generate in that particular week). | ||
|
||
| Weekly leaderboard position | Multiplier | | ||
| --- | --- | | ||
| 1-10 | 2x | | ||
| 11-50 | 1.7x | | ||
| 51-500 | 1.4x | | ||
| 501-1000 | 1.2x | | ||
|
||
<Callout type="feature"> | ||
You can [implement Azuro Waves Leaderboard into your UI](https://gem.azuro.org/hub/apps/guides/azuro-waves) | ||
</Callout> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 2 additions & 0 deletions
2
pages/knowledge-hub/background/a-primer-on-prediction-markets.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
10 changes: 3 additions & 7 deletions
10
pages/knowledge-hub/background/the-bettor-viewer-flywheel.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,13 @@ | ||
import { Image } from 'components' | ||
|
||
# The Bettor-Viewer Flywheel | ||
|
||
Betting and prediction markets are not mutually exclusive. Betting volumes contribute to the liquidity stock of a well-functioning prediction market, and the more liquidity is involved in a prediction market, the more accurate its odds will be perceived, since there are more people with skin-in-the-game and more monetary resources at-stake in that said prediction market. | ||
|
||
An efficient prediction market is the result of two thriving yet distinct user groups feeding off each other: profit-seeking bettors who form the “money base” of the market, and information-curious viewers who form the “attention base” of the market. | ||
|
||
- Increased attention helps get prediction markets to the eyes of profit-seeking bettors; | ||
|
||
- Bettors place bets against what they deem to be mispriced odds on a prediction market, contributing to that market’s volume and repricing of odds; | ||
|
||
- Interested viewers put greater weight on the accuracy of the prediction market due to the increased volumes, increasing attention and attracting more bettors into the mix; | ||
|
||
- Bettors place increasingly sized bets against the prediction market’s odds as open interest (OI) grows and the market becomes able to take in top-dollar bets; | ||
|
||
- Volumes boom, and viewers increasingly regard the prediction market as the source of truth for that event, further increasing its popularity which attracts more bettor eyeballs; | ||
|
||
- ad infinitum. | ||
- ad infinitum. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 5 additions & 1 deletion
6
pages/knowledge-hub/introduction/event-resolution-azuro-dao.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,11 @@ | ||
import { Image } from 'components' | ||
|
||
# Event Resolution: AzuroDAO | ||
|
||
Unlike first-generation prediction markets which burdens the tokenholder base for all event resolutions, Azuro prediction markets operate under a tiered resolution process. | ||
|
||
In Azuro, the [Data Provider](/knowledge-hub/how-azuro-works/protocol-actors/data-providers) retains the right to resolve the event in good-faith. The [AzuroDAO](/knowledge-hub/azur/azuro-dao) views data provider resolutions under the “innocent until proven guilty” principle: only when a resolution is disputed, then AzuroDAO may step in as the arbiter of last resort. AZUR will be the Schelling point token in presiding over dispute resolutions, whereby voting power is assigned based on the [redacted] mechanism. | ||
In Azuro, the [Data Provider](/knowledge-hub/how-azuro-works/protocol-actors/data-providers) retains the right to resolve the event in good-faith. The [AzuroDAO](/knowledge-hub/azur/azuro-dao) views data provider resolutions under the “innocent until proven guilty” principle: only when a resolution is disputed, then AzuroDAO may step in as the arbiter of last resort. | ||
|
||
AZUR will be the Schelling point token in presiding over dispute resolutions, whereby voting power is assigned based on the [redacted] mechanism. | ||
|
||
In the future, Azuro will look to leverage Web Proofs to resolve events directly from its official source (i.e., premierleague.com) to resolve Premier League markets) once Web Proofs become viable enough for practical implementation. |
6 changes: 5 additions & 1 deletion
6
pages/knowledge-hub/introduction/lp-utilization-virtual-funds.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,11 @@ | ||
import { Image } from 'components' | ||
|
||
# LP Utilization: Virtual Funds | ||
|
||
When you place a bet on Azuro prediction markets, you’re effectively putting in liquidity into the market’s underlying [vAMM](/knowledge-hub/how-azuro-works/components/vAMM) (and shifting its onchain odds in the process). This liquidity will remain with the vAMM until the [Condition](/knowledge-hub/how-azuro-works/components/conditions)’s resolution (and the prediction market is dissolved), or until you decide to redeem your position in advance of the resolution[*]. This forms part of a prediction market’s vAMM [Virtual Fund](/knowledge-hub/how-azuro-works/components/virtual-funds) calculation, which is the sum of betting flows and the worst-case max potential loss to the protocol, in excess of [Reinforcement](/knowledge-hub/how-azuro-works/components/reinforcement). | ||
|
||
Since all concurrent prediction markets share the same [singleton LP](/knowledge-hub/how-azuro-works/protocol-actors/liquidity-providers), each needs to check whether there’s sufficient liquidity on the Azuro LP prior to accepting more bets. The capacity of the singleton LP is updated block-by-block in real-time, where it will continue to facilitate more bets from any active prediction market under its umbrella as long as the sum of Virtual Fund balances across all of its currently active vAMMs does not exceed the pool’s own TVL. | ||
|
||
Data providers stream sell-side odds and bettors aim to exploit any mispricing of said odds, all the while vAMMs maintain Virtual Fund balances by algorithmically ‘booking’ liquidity from the singleton LP on a block-by-block basis. This is capital-efficiency at its finest: through the elegance of the Virtual Fund accounting system, Azuro prediction markets are autonomously allocated optimal liquidity levels from the singleton LP, without needing sophisticated entities to act as an opinionated market-maker for liquidity provisioning. | ||
Data providers stream sell-side odds and bettors aim to exploit any mispricing of said odds, all the while vAMMs maintain Virtual Fund balances by algorithmically ‘booking’ liquidity from the singleton LP on a block-by-block basis. | ||
|
||
This is capital-efficiency at its finest: through the elegance of the Virtual Fund accounting system, Azuro prediction markets are autonomously allocated optimal liquidity levels from the singleton LP, without needing sophisticated entities to act as an opinionated market-maker for liquidity provisioning. |
Oops, something went wrong.