Joint liquidity

1) The concept and why it is needed

Joint liquidity is the combination of players, bets, banks and prize funds of several participants (operators, studios/RGS, aggregators) into a common pool with uniform rules for participation, calculation and distribution of winnings.
The goal is to accelerate the launch of "scale games," reduce the waiting time (matchmaking), increase the stability of coefficients and the amount of prize money, reduce volatility and the cost of risk for each individual participant.

• More tables/events "always online" and higher conversion from the lobby.
• More predictable ratios and margins thanks to the depth of the pot.
• Savings on risk (diversification, offsetting) and on infrastructure (shared bus/PoR).
• Quick access to new regions due to existing network pools.

2) Joint liquidity models

1. P2P Pools/Multiplayer

Poker, crash/aviator, bingo, PvP arcades.
Joint matchmaking, rake/fee model, anti-exclusion and fair headquarters.

2. Online progressive jackpots

A common "piggy bank" from many operators/skins.
Contributions (contribution%) and drop rules (trigger RNG, cap, must-drop).

3. Common live tables

The studio broadcasts one table, to which the windows of different operators are connected.
Split flows, common bank rates, single limits and latency SLOs.

4. Exchange/pool rate model

Players stand "against each other," the provider is a matchker/clearing center.
Market making, application books, cross-matching markets.

5. Net Tournaments/Leaderboards

Common missions and ratings on several brands, single prize pool, anti-duplicates.

3) Network topology and node roles

Liquidity Hub (Clearing & Liquidity Hub): central orchestration body, accounting for incoming bets/buy-ins, matchmaking, calculation, final distribution.
Operators (Skins): front window, KYC/RG, payments, localization and customer experience.
Studios/RGS: game engine, RNG, live video, round/table rules.
Payment perimeter: deposits/withdrawals, tax withholdings, chargebacks and disputed transactions.
Observability/Trust nodes: audit of events, independent verification of RNG/rules, logging.

• Hub-and-Spoke for connecting multiple operators to one/more hubs.
• Active-Active hubs by region with GSLB/Anycast, low p95 and fast feilover.
• Service Mesh for L7 policies: mTLS, retries, circuit-breaker, outlier-ejection.

4) Protocols and events (canonical bus)

• `player_join`, `buy_in`, `bet_placed`, `match_found`, `round_start`, `round_result`, `jackpot_contribution`, `jackpot_hit`, `payout_settled`, `fraud_signal`, `kyc_status`, `rg_limit_hit`.
• Party keys: 'poolId', 'tableId', 'playerId', 'operatorId'.

• Schema Registry, idempotency, deduplication.
• Delayed/repeated deliveries without double charges (saga/txn-outbox).
• End-to-end 'trace-id' from click to pay.

5) Clearing, Netting and Settlement

Netting T + 0/T + 1: netting operator positions by pools/games, cut-off report.
Escrow/reserves: minimum participation balance (margin), "contribution discipline" and automatic margin-call.
Fee model: rake, jackpot commission, tech collection, fines/SLA loans.
Taxes and deductions: regional rules, per-jurisdiction reports, exchange rates and FX differences.

6) Traffic orchestration and matchmaking

MM algorithms: ELO/skill-banding, stake-banding, latency-aware, collusion protection.
Capacity-aware routing: accounting for hub/studio SLI, avoiding overloaded desks.
Sticky by table/round only when needed; fast transfers between pools.
Smart Lobby: ranking of tables/events by probability of beginning in ≤X seconds.

7) Risk management and game integrity

Anticollection and behavioral scoring: network graph, IP/ASN/devices, synthetic "honey traps."

RNG/rules: certification, periodical draws, cryptographic signature of results/sids.
Exposure limits: caps per operator/region/game; dynamic steak rebuilding.
Fraud/chargebacks: orchestrator of payment routes, freezing payments before verification.
RG policies: deposit/time limits, self-exclusion, country-based participation rules.

8) Security and legal circuit

Zero Trust: mutual authentication (mTLS), S2S signature (JWS/HMAC), short certificates.
Segmentation: dedicated vendor zones, financial circuit isolation and personal data.
Data Minimization: PII tokenization, separate storages, strict DPA/DPIA.
Juridics: roles (controller/processor), brand/stream rights, cross-border data streams, whitelist jurisdictions.
Audit and retroactive verification: immutable logs (WORM), external auditors, SLA for the provision of tracing.

9) Observability, SLO and DR

SLO pool: matchmaking time (p95), round start, calculation delay, payout accuracy (0 miss).
SLO integrations: uptime and latency operator↔khab, studiya↔khab, platezhi↔khab.
War-room and error budget alert: stop button for a specific pool/operator.
DR scenarios: asset hubs, state replication, black start (minimum pool launch path), regular chaos exercises.
RCA hygiene: pool trace map, auto-generating incident reports.

10) Economics and pricing

Margin and distribution: rake/fee, jackpot share, boosts for weak-regions, co-funding.
Risk pricing: rate/ratio limits based on pool depth and volatility.
Cost-to-Serve: rps/table/round price, GB traffic/video price, clearing price T + 0/T + 1.
Quality incentives: uptime/latency bonuses, SLO violation penalties.

11) Success Metrics (KPIs)

Liquidity: average pool depth, time to start (TTM-round), average bank size.
Conversion: table/event entry, round completion, repeat sessions, D1/D7/D30.
Finance: GGR/net by pool, rake/fee, share of jackpots, cost-to-serve, CAC/LTV.
Risk/Trust: fraud-rate, chargeback-rate, false-positive, incidents RG/1k active.
Reliability: p95 matchmaking/layout/payments, uptime hub and integrations, cut-over time.
Compliance: the share of correctly worked KYC, 0 leaks PII, SLA for the provision of audit.

12) Antipatterns

SPOF hub: a single non-scalable loop without N + 1 and an asset-asset.
"Pool without rules": no exposure, anti-exclusion and RNG certification limits.
State blending: common caches/databases for different pools/regions without segmentation.
No idempotency: Payout/buy-in doubles at retreats.
Lack of escrow/margin: "other people's money" in circulation without reserves and blocks.
PII walks between participants: lack of tokenization/DPIA and egress control.
Attribution "by eye": disputes over P&L and partner motivation.

13) Implementation checklist

1. Select the liquidity model (P2P/jackpot/live/exchange) and define the legal markets.
2. Design hubs (asset-asset), PoP/edge, GSLB/Anycast and mesh policies.
3. Enter events/schemas, idempotency, sagas and unchangeable logs.
4. Set up matchmaking, exposure limits, anti-exclusion and fraud signals.
5. Define clearing/netting, escrow, margin requirements and T + 0/T + 1 schedules.
6. Pin DPA/DPIA, RG policies, SLO/penalty/credits.
7. Expand observability, war-room, DR exercises and black start.
8. Agree on the economy: rake/fee, contribution%, co-funding, SLI bonuses.
9. Conduct synthetics/load, canary-launch by region, retro by T + 7/T + 30.

14) Evolution Roadmap

v1 (Foundation): single hub + base pools, escrow and clearing, event standard.
v2 (Scale): asset-to-asset by region, flexible limits, real-time storefronts and Smart Lobby.
v3 (Optimization): ML matchmaking, predictive exposure limits, dynamic pricing.
v4 (Networked): portfolio of pools between multiple hubs, inter-network liquidity roaming, general governance and independent trust audit.

Brief Summary

Joint liquidity is a network discipline: common pools, standardized events and settlements, asset hubs with low latency, a strict risk contour and a transparent economy. With this approach, the ecosystem receives scalable games and funds, predictable SLO/margin, reliable clearing, and sustained value growth for all network participants.