Market clusters

(Section: Ecosystem and Network)

1) Definition and purpose

• managed localization (jurisdiction/residency/taxes),
• predictable capacity and liquidity (deposits, disbursements, pools),
• sustainable economy (CTS, Take Rate, ARPPU/LTV),
• transparent SLO/compliance contours.

2) Cluster taxonomy

1. Geo-regulatory: EU, UK, TR, LA, APAC, NA; sub-clusters by license/tax.
2. Payment: card/local AWP/crypto; on-ramp/off-ramp corridors.
3. Product verticals: casino/live, betting (sports/cyber), mini-games, lotteries.
4. Traffic/Affiliates: Lead Sources, Storefronts, Streaming/Influencers.
5. Liquidity/liquid pools: tournaments/jackpots, provider pools, inter-cluster bridges.
6. Operating: support for languages, opening hours, SLA providers KYC/PSP.
7. Risk/compliance: sanctions lists, KYC/KYB levels, anti-fraud profiles.

3) Cluster topologies and connectivity

Hub-and-Cluster: regional hubs (network layer) serve several market clusters with shared caches and storefronts.
Cluster Mesh: Cluster peers are bridged (liquidity/data) with managed finalization.
Ring/Spoke: one "nuclear" cluster (reference directories) and peripherals for local markets.
Isolated-Mode: the cluster operates autonomously under channel isolation (finalized-only).

4) Roles and members within the cluster

B2C/B2B2C operators: brands/white-label.
Content and providers: studios, tournaments, sports feeds.
PSP/APM/On-Off Ramp: local methods, crypto processing.
KYC/KYB/AML: verification, sanctions, scoring.
Affiliates/traffic aggregators: storefronts, DSPs, CRM partners.
Infrastructure/Bridges: Nodes, Rereliers, DA.
Governance/audit: cluster rules, budgets, grants, reporting.

5) Liquidity model and routing

Local pools: deposits/payments within the cluster, reporting currency, P0 reserves.
Inter-cluster bridges: limited corridors with K-confirmations/dispute window.
SOR (Smart Order Routing): directs traffic/payments/liquidity to SLA/value/risk.
Pricing and commissions: Based on CTS (Cost-to-Serve), commission volatility and PSP/DA waivers.

6) Catalogs and data contracts

Unified directories for clusters: networks, assets, PSP/methods, languages ​ ​/locales, regulatory, SDK versions.

yaml cluster:
id: "eu.gaming.core"
region: "EU"
products: ["casino","sports","live"]
payments:
methods: ["SEPA","cards","USDC"]
limits_daily: { deposit: 1000000, payout: 1000000 }
compliance:
kyc_levels: ["basic","enhanced"]
residency: "EU-only"
slo:
api_p95_ms: 400 payout_finality_p95_min: 10

7) Cluster SLI/SLO and QoS

• p95 API latency (P0/P1), Success Rate, Queue-Lag p95;
• Freshness showcases (min), Finality p95 for payouts/bridges;
• Geo-Hit Ratio (locally serviced requests,%);
• PSP Success%, KYC p95 (мин), Dispute/Chargeback Rate;
• Liquidity Utilization%, Proof-Coverage%.

• P0 p95 ≤ 400 мс, Availability ≥ 99. 95%;
• Payout Finality p95 ≤ 10 min; KYC p95 ≤ 15 min;
• Geo-Hit ≥ 85%; PSP Success ≥ 98. 5%; Proof-Coverage ≥ 99%.

QoS: P0 (payments/bridge/finalization), P1 (product), P2 (bulk/archive).

8) Data and schemas (pseudo-SQL)

Cluster and link registers

sql
CREATE TABLE market_clusters (
cluster_id TEXT PRIMARY KEY,
region TEXT, currency TEXT, residency TEXT,
products JSONB, created_at TIMESTAMPTZ
);

CREATE TABLE cluster_links (
src_cluster TEXT, dst_cluster TEXT,
link_type TEXT,      -- liquidity    data    traffic k_conf INT, challenge_min INT,
capacity NUMERIC,     -- дневные лимиты ликвидности cost_per_tx NUMERIC,
status TEXT,
PRIMARY KEY (src_cluster, dst_cluster, link_type)
);

PSP profiles and success

sql
CREATE TABLE psp_stats (
ts TIMESTAMPTZ, cluster_id TEXT, psp TEXT, method TEXT,
success_pct NUMERIC, fee_p95 NUMERIC, latency_p95_ms INT, volume NUMERIC
);

Geo-Hit и Freshness

sql
SELECT cluster_id,
100.0 SUM(CASE WHEN served_local THEN 1 END)/COUNT() AS geo_hit_pct,
PERCENTILE_CONT(0.95) WITHIN GROUP (ORDER BY freshness_s) AS freshness_p95
FROM cluster_requests
WHERE ts >= now() - INTERVAL '24 hours'
GROUP BY cluster_id;

9) Routing and limits (policies)

yaml routing:
order:
- prefer_local_cluster
- min_fee_p95
- max_success_pct guards:
p0_queue_lag_p95_ms: 2000 k_confirmations_min: 12 payouts:
corridor_limits:
"eu.gaming.core -> la.gaming.core": { daily_usd: 500000, k: 20 }
traffic:
throttle:
debug_sampling_pct: 5 heavy_queries_deny: ["logs>5000blocks"]

10) Observability and dashboards

Cluster Ops (hour/real time): latency/error/queue-lag, p95 finalization, PSP success/fees.
Economy: CTS/1k ops, Take Rate, Liquidity Utilization%, ARPPU/LTV (без PII).
Compliance: residency, sanctions, KYC SLA, Proof-Coverage.
Routing: Geo-Hit, corridor loading, bridge/DA failures.
Risk: chargebacks/disputes, traffic/payment anomalies.

11) Cluster economics

CTS per 1k ops = channels + calculations + storage + licenses/providers.
TPS_per_$ - sustainable bandwidth per dollar.
Partner contribution: Net Contribution (GTV − Cost − Rebates).
Cross-subsidization: margin transfer through inter-cluster corridors according to Governance rules.

12) Governance and the evolution of clusters

Proposal process: creation/merging/splitting of clusters, changing limits/corridors, admission of new PSP/KYC.
Timelock and auditing: signed resolutions, reportable storefronts, post-mortem incidents.
Version catalogs: LTS SDK/events, deprecate window ≥ 90 days.
Antitrust and risk constraints: PSP/content/traffic diversification.

13) Incident playbooks

A. PSP Success% drawdown in cluster

1. Switch SOR to alternative methods, 2) increase in K-confirmations/waiting limits,

2. notification of participants, 4) fee/latency analysis, 5) post-mortem.

B. Liquidity corridor overload

1. Introduction of rate-limit/quotas, 2) temporary premium fee, 3) redistribution to neighboring clusters, 4) report.

C. Disruption of residence/export

1. Block of inter-cluster exports, 2) redaction, 3) Compliance notification, 4) policy update.

D. DA/bridge failure spike

1. Mode "finalized-only," 2) enlarging the dispute/Q window, 3) compensating operations, 4) analyzing the reasons.

E. Traffic anomalies (bot injections)

1. Throttle/deny rules, 2) KUS/behavioral filter enhancement, 3) payout quarantine, 4) attribution recalculation.

14) Implementation: checklist

1. Segment markets by geo/regulatory/payments/verticals and lock in a cluster map.
2. Define SLO/QoS and economic metrics (CTS, TPS_per_$, Take Rate).
3. Set up directories/contracts and SOR routing, corridor limits.
4. Include observability: Cluster Ops/Economy/Compliance/Risk.
5. Perform DR/chaos tests of inter-cluster connectivity and DA.
6. Start the Governance change process (timelock, reports, deprecates).
7. Review cluster structure and ROI monthly.

15) Glossary

A market cluster is a domain with general rules for demand, payments and compliance.
Corridor - managed communication between clusters (liquidity/data/traffic).
SOR - smart routing of operations at price/SLA/risk.
CTS per 1k ops - the cost of servicing 1000 operations.
Geo-Hit Ratio - the proportion of requests served locally.
Proof-Coverage - the share of records with crypto evidence/anchors.

Bottom line: market clusters turn "one big network" into a set of managed domains with their own SLOs, economies and risk policies. Clear catalogs, SOR routing, liquidity measurability, and rigorous Governance allow the ecosystem to scale, maintain compliance, and optimize value with a stable user experience.