Toolkit v6.5 & SDK v7.6 — August 25, 2026

This release adds bet reports — a turnover / returns / profit / ROI summary over a bettor’s bets — plus new filter fields shared by the bet list and the report, and a settledPayout field that keeps a bet’s historical payout visible after redemption.

New: bet reports

getBetsReport (toolkit)

A new framework-agnostic function — no React required, so it can be called from any JS/TS frontend — fetches every v3 bet matching a filter and aggregates it into a per-token turnover / returns / profit / ROI report:

import { getBetsReport, BetStatusFilter } from '@azuro-org/toolkit'
 
const report = await getBetsReport({
  chainId: 137,
  filter: { bettor: '0x...', status: BetStatusFilter.Settled },
})
 
const row = report.single ?? report.byToken[0]

It walks the bettor’s whole history with a timestamp cursor rather than skip, so the report is exact over every matching bet — not just the pages a list happens to have loaded — and surfaces isTruncated when a very large history hits the walk’s page cap.

ROI covers the bets that were at risk (profit / turnover × 100, where settled means Won, Lost or cashed out) and is null — never NaN — when turnover is zero. Three kinds of bet stay out of it: pending ones, surfaced as pendingCount / atStake; voided ones, surfaced as canceledCount / refunded, because a void returns the stake in full and a bet that was never at risk says nothing about how a bettor bets; and freebet-funded ones, since the stake wasn’t the bettor’s own money, reported in their own freebet bucket instead.

See the full docs for the return shape and the count-semantics rules that keep freebet bets from being double-counted.

useBetsReport (SDK)

A TanStack Query wrapper around getBetsReport:

import { useBetsReport, BetStatusFilter } from '@azuro-org/sdk'
 
const { data: report } = useBetsReport({
  filter: { bettor: '0x...', status: BetStatusFilter.Settled },
})

useBetsReport takes the same filter object as useBets — pass it the same filter you pass to the list, and the report is guaranteed to describe exactly the bets the list shows.

New useBets / getBetsReport filter fields

Both useBets and getBetsReport (and, by extension, useBetsReport) now share one filter shape with three new fields, on top of the existing bettor / affiliate / status:

type BetsFilter = {
  bettor: Address
  affiliate?: Address
  status?: BetStatusFilter
  kind?: BetKind          // new — single (Ordinar) vs combo (Express)
  createdFrom?: number    // new — inclusive lower bound, unix seconds
  createdTo?: number      // new — inclusive upper bound, unix seconds
  isFreebet?: boolean     // new — true = freebet-funded only, false = own-funds only, omit = both
  /** @deprecated renamed to `status` */
  type?: BetStatusFilter
}

filter.type is now deprecated in favour of filter.status (when both are set, status wins), and useBets’s previously-undocumented orderBy / orderDir props have been corrected on the docs site: useBets never accepted them — only useLegacyBets does.

BetStatusFilter and BetKind

BetType — the enum used for lifecycle filtering (Unredeemed, Pending, Accepted, Settled, CashedOut) — is renamed to BetStatusFilter, since these are lifecycle statuses, not bet types. A new BetKind enum (Single | Combo) covers what BetType never did: filtering by single vs combo bets.

Combos with a voided leg are no longer credited that leg

A leg of a combo can be voided on its own — the game is cancelled, or the outcome is settled as Canceled while the rest of its condition resolves normally.

Both the report and the bet list now read what the surviving legs are worth for that shape:

• getBetsReport / calcBetsReport rebuild returns as stake × calcMinOdds(surviving leg odds) — which is how a combo is actually priced.
• useBets applies the same figure to settledPayout and to payout — the latter matters most, since it is what a redeem button shows the bettor.

Redeemed bets are untouched: their recorded payout is the amount that was actually paid.

New isSelectionCanceled({ selectionResult, outcomeResult, conditionStatus }) is the single place that decides whether a leg was voided — no single field answers it, since a leg can be voided while its condition stays Resolved. useBets and the report share it, so a summary can never describe a different set of legs than the rows above it.

Bet.settledPayout

Bet.payout answers “is there money to claim?” — it’s gated on redeemability and becomes null once a bet is redeemed. That made it a poor fit for historical or aggregate views, where a redeemed winning bet would render as a blank payout.

The new settledPayout: number | null answers “what did this bet return?” instead, and stays populated after redemption:

type Bet = {
  // ...
  payout: number | null          // unchanged — gates a redeem action
  settledPayout: number | null   // new — the bet's recorded payout, survives redemption
}

Use settledPayout wherever you display a bet’s historical result — a bet list, or next to an aggregate like a bets report — and keep using payout only to decide whether to show a redeem button. payout itself is unchanged, so no existing consumer needs to change anything.