ThrillPots Release Notes

Release NameRelease MonthRelease State
ANTICIPATIONJanuary 2026Beta 2

IMPORTANT: As with most of our releases, the intent is that all packages are deployed to their latest versions (stipulated in Docker Images (beta images)).

General

This release is not mandatory

POTENTIALLY BREAKING CHANGES

  • ThrillConnect service now only sends JackpotUpdate events when the ticker values have changed.

New Features

ThrillPots

  • Exclusion Rules for contributions and jackpot visibility
    • Exclusion rules make it possible to restrict access to jackpots based on:
      • Game Code(s) -- you can now prevent certain game codes from participating in the jackpot
      • Game Category(s) -- you can now prevent certain game categories from participating in the jackpot
      • Player ID(s) -- you can now prevent certain players from participating in the jackpot
      • Player Segment(s) -- you can now prevent certain player segments from participating in the jackpot
    • The "Get Jackpot For Source" APIs now support an additional query parameter (game_code) which can be passed as context for exclusion rule checks. This will allow you to determine whether a jackpot should be shown to a player in the context of a specific game or not.

ThrillConnect

  • Exposed APIs to provide Latest Winners functionality to frontend clients. More details

ThrillOffice

  • New ThrillPots Template Management admin view
  • New ThrillPots Source Management admin view
  • New ThrillPots Exclusion Rules Management admin view
  • New Jackpot Model Switching admin interface
  • Reconciliation view now features multiple view modes. The supported modes are:
    • Delta mode: only shows the monthly movement per jackpot
    • Groupped mode: group all instances into one consolidated row per month
  • Jackpot state management - admin users can now pause and unpause the jackpot instance

Changes/Improvements

ThrillPots

  • Improvements to Community Payout Strategy: Random Active Players
    • Improvements have been made to the random selection mechanism for players that fall under the Active Players Payout Strategy.
  • Always Fair Multicurrency minimum bet constraints are now configurable for Percentage Based Jackpots.
  • Empty string idempotency keys in contribution requests are now treated as nil
  • Added support for payload signature on contribution outcome webhook callback

ThrillGate

  • Improved transaction handling on retry exhaustion
  • Improved pending transaciton monitoring
  • Added the ability to settle witheld transactions via batch transaction api

ThrillConnect

  • Optimized jackpot update events - updates are broadcasted only if the pot values had changed
  • Improved handling for failed tokens during WS authentication. The new system holds a cache of failed tokens and ignores re-attempts of authentication using failed tokens. This is expected to prevent unintended flooding of failed token authentication requests from flooding deeper into the system.
  • Get Jackpot For Source now accepts game_code query parameter to enforce exclusion rules
  • Deduped allowed_sources on jackpot update events
  • HTTP request body size limited to 100kb;
  • Added support for custom CORS headers

ThrillOffice

  • Dashboard: top players cards now display the brand
  • New optimized reporting APIs for dashboard use:
  • API audit now enabled in limited proxy mode
  • Improved organisation scoped filtering

Bug Fixes

ThrillOffice

  • File export - filename length limited to fit OSs constraints
  • User modal - fixing incorrect default state being org bound

ThrillGate

  • If the operator platform exchanges the token passed in SWAuthRequest with another token to be used, the new token is now honoured and used.