Developer Hub
Azuro Protocol V3
Smart contract changes v3

Azuro Protocol V3: Changes to smart contracts

⚠️

We are planning Azuro Protocol V3 release around May 1st, and V2 will no longer be supported. A warning will be issued one week before the release. Throughout April, we will update Azuro Protocol based on feedback without making structural changes. Stay tuned for further updates

Bets improvements

In the V2 protocol, bets on pre-match, live and combo events processed in different contracts, with different betting logic, which added complexity to the protocol. In the new version V3, all types of bets (pre-match, live, combo) are processed by a single contract, which allows:

  • pre-match events become live events with the onset of a sporting event
  • combo bets can be made up of pre-match and live events
  • added the ability to accept bets from smart wallets (wallets smart contracts)
  • bets are placed by special bet executors, and the ability to provide gas-free transactions has been added

Placing bet and paying out

Placing a bet occurs in several stages:

  • bettor approves token spending (for the bet) for the Relayer contract (entry point for bets)
  • bettor forms the bet parameters and signs (using EIP-712 standard) it in the WEB3 wallet. All betting in V3 is done in the same way as V2 "live betting", using the EIP-712 parameters signing
  • bettor transfers the signed data to the oracle via API
  • oracle signs received data, forms and transfers the order to the executor (Relayer Executor)
  • the executor (Relayer Executor) execute transaction call of function betFor(OrderData[] orders) method of Relayer contract, orders contains the user's bet data, placing the bet
struct OrderData {
    address betOwner;
    ConditionData[] conditionDatas;
    BetType betType;
    address oracle;
    bytes clientBetData;
    bytes bettorSignature;
    bytes oracleSignature;
}
 
struct ConditionData {
    uint256 gameId;
    uint256 conditionId;
    ConditionKind conditionKind;
    uint64[] odds;
    uint128[] outcomes;
    uint128 payoutLimit;
    uint8 winningOutcomesCount;
}
 
enum BetType {
    ORDINARY,
    COMBO
}
 
enum ConditionKind {
    PREMATCH,
    LIVE
}
  • after placing a bet (transaction executed), the NewLiveBet() event is emitted, and bettor receives a bet token (azurobet)
event NewLiveBet(
    uint256 indexed tokenId,
    address indexed bettor,
    address indexed affiliate,
    BetType betType,
    uint256 nonce,
    uint128 amount,
    SubBetData[] betDatas, // one record for ordinary, many records for combo
    uint128 payoutLimit
)
 
struct SubBetData {
    uint256 gameId;
    uint256 conditionId;
    ConditionKind conditionKind;
    uint128 outcomeId;
    uint64 odds;
}
  • while betFor() execution, if the condition (in bet params) was not registered, it is register with the emiting of the ConditionCreated() event
event ConditionCreated(
    uint256 indexed gameId,
    uint256 indexed conditionId,
    uint128[] outcomes,
    uint64[] odds,
    uint8 winningOutcomesCount
)

Payout on winning bet (same as in V2)

If the bet wins, the user withdraw payout executing lp.withdrawPayout(address core, uint256 tokenId) The winnings are paid to the owner of the bet token and the BettorWin() event is emitted

event BettorWin(
    address indexed core,
    address indexed bettor,
    uint256 tokenId,
    uint256 amount
)
Migrate SDK from v5 to v6Deployment Addresses