$NPX Revenue Sharing

Primary Revenue Streams

  • Subscription Revenue: Monthly/annual platform subscriptions paid in $NPX or fiat (converted to SOL)

  • Revenue Distribution Pool: Distributed in SOL from subscription revenue

Revenue Collection Smart Contract

contract SubscriptionRevenueCollector {
    struct Subscription {
        uint256 monthlyFee;
        uint256 startTime;
        uint256 duration;
        bool isActive;
        uint8 tier;
    }
    
    mapping(address => Subscription) public subscriptions;
    uint256 public totalMonthlyRevenue;
    
    function processSubscriptionPayment(address user) external {
        require(subscriptions[user].isActive, "Inactive subscription");
        uint256 fee = subscriptions[user].monthlyFee;
        totalMonthlyRevenue += fee;
        emit SubscriptionPaymentProcessed(user, fee, block.timestamp);
    }
}

Distribution Mechanism

Revenue Distribution Context

  • Revenue Distributions: Paid in SOL, not from token allocation

  • Mission Hashing: Each payout references mission hashes on the coordination ledger for provable but private auditing.

Revenue Share Method

  • Proportional Distribution: Revenue distributed based on user activity weight

  • Example Formula: userShare = (userActivityWeight / totalActivityWeight) * distributableRevenue

Revenue Calculation

def calculate_sol_rewards(user_weight, total_weight, monthly_revenue_sol):
    annual_revenue_sol = monthly_revenue_sol * 12
    user_share = user_weight / total_weight
    monthly_reward_sol = (user_share * annual_revenue_sol) / 12
    return monthly_reward_sol

Technical Implementation

Distribution Frequency

  • Monthly Distribution: Revenue shared monthly based on subscription payments

  • SOL Rewards: Users receive SOL directly from subscription revenue

  • Direct Claims: Users claim SOL rewards directly from the contract

  • Zero-Knowledge Claim Proofs: Claims emit zk receipts so finance teams can verify payouts without seeing wallet histories.

Security Features

Basic Protection Mechanisms

  • Anti-Gaming Period: Prevents frequent join/leave manipulation

  • Individual Allocation Caps: Maximum individual caps to prevent centralization

  • Contract Pausability: Emergency pause functionality for security incidents

Transparency Features

  • On-Chain Tracking: All revenue and distributions recorded on blockchain

  • Real-Time Metrics: Live revenue and distribution data available to participants

  • Audit Trail: Complete transaction history for all revenue sharing activities

  • Matrix Monitor Dashboard: Console widgets stream encrypted revenue analytics without exposing treasury internals.

This technical framework ensures transparent revenue distribution while maintaining platform security and encouraging participation in the Nerve Protocol ecosystem.

Last updated