GH GambleHub

Profit distribution models

1) Why formalize allocation

There are many participants in the ecosystem (operators, studios, affiliates, infrastructure providers, DA/bridges, validators, auditors). Formalized models:
  • reduce transaction costs and disputes;
  • make incentives consistent (quality ↔ profit share);
  • simplify scaling and cross-chain expansion.

2) Taxonomy of models

1. Classic RevShare (revenue share): fast start, easy reporting; risk - weak link to costs/quality.
2. Net Profit Share (NPS): share net income after direct costs; need reliable cost accounting.
3. Profit Pools: total pool by domain/product → distribution by key.
4. Hybrid (CPA/CPL + RevShare/NPS): fix + percentage; risk and cache balance.
5. Performance-Indexed (QF model): share × quality multiplier (SLO/Retention/ARPPU/finality).
6. Risk-Adjusted (RAROC/S-collateral weights): accounting for economic collateral and exposure to risks/incidents.
7. Vesting/Cliff models: deferred payments until quality verification and returns/chargebacks.
8. Co-Ownership (RNFT): Relationship contract with shares, limits, quorums, and distributions.

3) Revenue, cost, profit: terminology

Gross Revenue (GR): Gross revenue of the event/stream.
Adjustments: sales taxes, returns, chargeback/bonus burn.
Net Revenue (NR) = GR − Adjustments.
Direct Costs: DA/bridge/gas/egress/compute/licenses/payment fees.
Contribution Margin (CM) = NR − Direct Costs.
Shared Overhead: amortized general expenses (support, observability).
Net Profit (NP) = CM − Shared Overhead.

4) Basic distribution formulas

4. 1 RevShare / NPS

[
\text{Payout}_i = \alpha_i \cdot \text{NR}
\ quad\text {or }\quad
\text{Payout}_i = \beta_i \cdot \text{NP}
]

where (\alpha _ i ,\beta _ i) are fixed fractions.

4. 2 Profit Pool

[
\text{Pool} = \sum_{e\in \mathcal{E}} \text{NP}_e,\qquad
\text{Payout}_i = \omega_i \cdot \text{Pool},
]

(\omega _ i) is defined by distribution keys (shares, contribution, QF, risk).

4. 3 QF-multiplier (quality)

[
\text{QF}_i = f\big(\text{success},,p95,,\text{DLQ},,\text{finality},,\text{Retention},,\text{ARPPU}\big)\in[\underline{q},\overline{q}]
]
[
\text{Payout}_i = \omega_i \cdot \text{Pool} \cdot \text{QF}_i
]

4. 4 Risk and collateral (S)

[
\text{RiskAdj}_i = g(\text{IncidentRate},,\text{Exposure},,S_i)
\quad\Rightarrow\quad
\text{Payout}_i = \omega_i \cdot \text{Pool} \cdot \text{QF}_i \cdot \text{RiskAdj}_i
]

5) Distribution keys (ω)

Combine 3 vectors:
  • Equity/Share: shares/cap-table, licenses.
  • Contribution: traffic/time/resources (vCPU, GPU-min, GB-egress, DA-byte), verified value-events.
  • Reputation/Quality (R/QF): reputation R (soulbound), QF-quality.
Example:
[
\omega_i = \lambda_1\cdot \text{Share}_i + \lambda_2\cdot \text{Contribution}_i + \lambda_3\cdot h(R_i),\ \sum\omega_i=1
]

6) Allocating costs

1. Pro-rata by shares: simple but insensitive to load.
2. Usage-based: resource counters (compute/egress/DA).
3. Activity-based Costing (ABC): cost drivers (requests, moderations, payments).
4. Risk-surcharge: "expensive" routes/wristbands of finality receive a premium.

Formula:
[
\text{Cost}i = \sum_r u{i,r}\cdot \text{Rate}r + \text{RiskSurcharge}{i}
]

7) Hybrids and reservations

Floor/Cap: lower and upper payout limit.
Clawback: adjustment after chargeback/retract window.
Waterfall: priorities (taxes/returns → costs → S-insurance fund → pools → bonuses).
Sunset windows: time coefficients that auto-collapse.
Stabilizers: smoothing (EWMA) and "corridors" ([\underline {q} ,\overline {q}]) for QF.

8) RNFT contracts

RNFT records:
  • parties (DID/VC), roles (Operator/Provider/Studio/Affiliate/Auditor/Treasury);
  • model ((\alpha ,\beta ,\omega,) QF, RiskAdj), windows (returns, finality), limits and quotas;
  • S-pledges, slashing/escrow rules;
  • compliance (regions, taxes/withholdings), reporting and auditing;
  • 治理: quorums, vetoes, appeals, formula version, sunset.

9) Anti-gaming and justice

Dedup: idempotent events, outbox/inbox, seen-tables.
Anti-arb: ban/fine for "internal overflows" for the sake of QF/attribution window.
Golden-set checks: hidden quality control samples.
Graph analysis: mutual review/pseudo-affiliation rings.
Fairness (Jain): ((\sum x) ^ 2/( n\sum x ^ 2)) by share and budget.

10) Cross-chain aspects

Finality-aware: payments after reaching the target finality/challenge windows.
State proofs/bridges: transfer of aggregates, not "raw" logs.

Badge portability: we publish quality evidence badges (for example, SLA≥99. 9 %/90d) rather than "reputation as a number."

Policy precedence: There is a more stringent policy when rules conflict.

11) Taxes and compliance

Tax deductions on the payout route (withholding).
Regional restrictions for shares and payments (sanctions/age/licenses).
Audit trails: immutable logs, signed reports.
Privacy: selective reporting, ZK threshold confirmations.

12) Observability and reporting

End-to-end tracing: 'x _ msg _ id', 'rev _ event _ id', 'rnft _ id', 'route _ id'.

Panels:
  • P&L Live: GR/NR/CM/NP, deviations from plans.
  • QF & Risk: contribution of quality and penalties, finality map.
  • Cost Drivers: Resources/bets, expensive routes.
  • Disputes: frequency, MTTR, adjustment sums.
  • Governance: turn of proposals, effect of sunset edits.

13) KPI of distribution programs

Economics: margin/message ↑, Cost-to-Serve ↓, volatility payments ↓.
Quality: QF median/percentile ↑, the share of providers in the "green" zone ↑.
Justice: Jain in the hallway; reduced risk/income concentration.
Robustness: MTTR by ↓ disputes; clawback rate after the ↓ window.
Compliance: zero critical violations, accuracy of tax deductions.
Predictability: payout pool forecast error ≤ target.

14) Implementation playbook (in steps)

1. Inventory of value streams: where is GR/NR, what are the cost/risk drivers.
2. Model choice: RevShare/NPS/Pool/Hybrid + QF/RiskAdj, keys (\omega).
3. Cost accounting: include usage/ABC, resource rates, finality/bridges.
4. RNFT templates: shares, windows, clawback, S-pledges, eskrou,治理.
5. Calculation and simulations: retrospective for 3-6 months, stress tests (chaos/finality/chargeback).
6. Observability: tracing, P&L panels, QF, Risk, Disputes.
7. Pilot: restricted domain, A/B coefficients, sunset windows.
8. 治理: approval of weights/limits, publication of methodology.
9. Activities: automatic reports, closing period, audit trail.
10. Scaling: connecting new roles/regions/chains.

15) Reference parameters (landmarks)

QF corridor: ([0. 8; 1. 2]) for the sustainability of incentives.
RiskAdj corridor: ([0. 9; 1. 1]) (unless there are class S incidents).
Clawback window: 14-90 days (vertical/geo).
Window finality: ≥ 3 × (T_{block}) or by bridge/chain.
Fairness (Jain): ≥ 0. 85 for key pools.
Payout lag: (T_{close }\le 7) days after the period.

16) Delivery checklist

  • Defined GR/NR events and overhead drivers (usage/ABC)
  • Model (RevShare/NPS/Pool/Hybrid) and keys (\omega) selected
  • QF and RiskAdj configured, corridors and anti-aliasing
  • RNFT contracts: windows, clawback, S- eskrou,治理 and veto
  • Tax deductions and geo/sanctions built in
  • Trace and P&L panels, reports and audit logs
  • Simulations/retro calculations and stress tests passed
  • Pilot, sunset edits and public methodology
  • Dispute and MTTR-SLO procedures are set
  • Scaling plan by domain/chain/region

17) Glossary

RevShare/NPS: share of revenue/net income.
Profit Pool: aggregated profit pool by domain/period.
QF: quality multiplier by SLO and value.
RiskAdj: Risk/Incident/Collateral Adjustment.
RNFT: contract of relationships, shares, limits and procedures.

ABC - Activity Driver Costing

Clawback: reverse adjustment of payouts after the risk window.

18) The bottom line

A good profit-sharing model is an incentive algorithm, where quality, risk and contribution are directly reflected in the payout share. The combination of pools/hybrids, QF and RiskAdj, strict cost allocation, RNFT contracts and transparent reporting create a sustainable economy: participants see fair pravila,治理 gets manageable leverage, and the ecosystem gets predictable margins and scalable growth.

Contact

Get in Touch

Reach out with any questions or support needs.We are always ready to help!

Telegram
@Gamble_GC
Start Integration

Email is required. Telegram or WhatsApp — optional.

Your Name optional
Email optional
Subject optional
Message optional
Telegram optional
@
If you include Telegram — we will reply there as well, in addition to Email.
WhatsApp optional
Format: +country code and number (e.g., +380XXXXXXXXX).

By clicking this button, you agree to data processing.