What it does
Azuro supplies the market infrastructure behind independently operated apps. Its pooled-liquidity design differs from an exchange that matches two resting orders: liquidity providers are exposed to outcomes across the pool. A user should identify both the protocol and the frontend being used.
For builders, the SDK and toolkit make market data and betting flows reusable. For readers, the useful distinction is between protocol updates and an app’s own terms, fees and promotions. Old Azuro Waves pages remain available as history and do not establish a current airdrop.
Where it stands out
- Shared liquidity for multiple apps
- Public contracts and developer tooling
- Documented market settlement design
What you can do
- 01AMM-based prediction infrastructure
- 02Liquidity pools
- 03SDK and toolkit
- 04Independent frontends
Who’s behind it
Azuro describes three components: the protocol, its SDK and AzuroDAO governance. Individual frontend operators are separate from this protocol profile.
Fees & availability
Fees and costs
Costs depend on the selected app, pool and transaction; liquidity-provider returns depend on actual betting outcomes.
Eligibility and availability
Pool deposits can lose money. Protocol availability does not establish legal access to a particular betting frontend.