Revenue Distribution Protocol
The ORDP defines the deterministic mathematical implementation of the operator revenue split — 70% to the team, 30% to Oxiverse Systems LLP, computed on Net Revenue.
The Operator model defines the principles of revenue sharing: guaranteed base pay, performance rewards, and equal treatment. This protocol defines the math. By separating the two, the protocol can be upgraded via governance without amending the foundational structure. Architecture: 4-layer modular design — adaptive consensus, anti-toxic governance, and perfect meritocratic correlation.
Scope
This protocol applies exclusively to the Oxiverse Operator Team consisting of 2 to 5 Operators, as defined by the Oxiverse Constitution. It is not intended for larger teams without formal protocol revision.
The Voting Layer
Anti-Mob Floor
This layer ingests peer evaluations and enforces strict mathematical constraints to prevent manipulation and ensure fairness.
- →Every operator distributes exactly 100 points.
- →Self-voting is strictly prohibited.
- →Maximum 30 points may be given to any single peer.
- →All 100 points must be allocated.
The Anti-Mob Floor (for n=5): if 4 operators coordinate a "mob attack" to starve a target of all points, they can only distribute 30 × 3 = 90 points to the 3 non-target peers. The remaining 10 points are mathematically forced onto the target. Across 4 attackers, the target is guaranteed a minimum of 40 points — preventing financial starvation before the revenue formula even executes.
Adaptive Consensus Layer
Dispersion & Easing
This layer measures the team's polarization and dynamically calculates the Base Ratio (b).
Dispersion uses Mean Absolute Deviation (MAD) from the perfect consensus mean (100):
- →Normalize Variance: V = min(1.0, MAD / POLARIZATION_CAP) — a variance ratio between 0.0 and 1.0.
- →Apply Quadratic Easing: b = B_min + ((B_max − B_min) × V²) — the base ratio stays stable at B_min until polarization becomes genuinely extreme.
The Pool Allocation Layer
Two Buckets
This layer slices the total Net Revenue Team Pool (R) into two distinct buckets based on the dynamic Base Ratio (b).
- →Base Pool (R_base): b × R — distributed equally to ensure income security.
- →Performance Pool (R_perf): (1 − b) × R — distributed proportionally to reward merit.
The Distribution Layer
Final Payout
This layer calculates the final payout for each operator i:
Invariant Check: the sum of all payouts always exactly equals R.
Protocol Constants
These parameters were locked following a 750,000-iteration Monte Carlo stress test across 5 adversarial scenarios (Honest, Cartel, Mob Attack, Apathy, Superstar) and 5 team sizes.
A cap of 10 over-reacts to normal variance. A cap of 40 keeps honest voting at a 52.1% base while smoothly raising the base to 57.2% during a verified Mob Attack.
In a state of perfect consensus, 50% of the revenue is distributed equally as a guaranteed base distribution.
Even in maximum polarization, 30% of the revenue remains in the Performance Pool to reward top contributors.
Across all 5 scenarios, the Point-to-Payout Correlation remained exactly 1.0000. The protocol perfectly rewards merit without mathematical distortion. In a Mob Attack (n=5), the target receives ~74% of the top earner's payout (financially secure), while top earners still receive a 1.43x multiplier (merit rewarded).
Implementation Notes
- →Gas Efficiency: MAD and Quadratic Easing require only basic arithmetic. No square roots or complex floating-point math.
- →Precision: All internal calculations should use fixed-point math (e.g., multiplying by 10¹⁸ in Solidity) to prevent rounding errors before the final payout distribution.
- →Integer Rounding: Any remainder produced by integer division is distributed per deterministic rules so total distributed revenue equals R exactly, no operator receives negative adjustment, and every execution produces identical results.
- →Modularity: The 4 layers should be implemented as separate interfaces/contracts to allow future upgrades to the Consensus Layer without altering the Voting or Distribution logic. The protocol MUST remain deterministic — identical inputs always produce identical outputs regardless of language or environment.
Protocol Invariants
- ✓Total payout equals total revenue pool.
- ✓Equal points produce equal payouts.
- ✓More points can never produce less payout.
- ✓Base ratio always satisfies: B_min ≤ b ≤ B_max.
- ✓Every eligible operator receives at least their Base payout.
- ✓Calculations are deterministic and publicly verifiable.