> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/tokenomics/npx-revenue-sharing.md).

# $NPX Revenue Sharing

Primary Revenue Streams

* **Subscription Revenue**: Monthly/annual platform subscriptions paid in $NPX or fiat (converted to ETH)
* **Revenue Distribution Pool**: Distributed in ETH from subscription revenue

#### Revenue Collection Smart Contract

```solidity
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 ETH, 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

```python
def calculate_eth_rewards(user_weight, total_weight, monthly_revenue_eth):
    annual_revenue_eth = monthly_revenue_eth * 12
    user_share = user_weight / total_weight
    monthly_reward_eth = (user_share * annual_revenue_eth) / 12
    return monthly_reward_eth
```

### Technical Implementation

#### Distribution Frequency

* **Monthly Distribution**: Revenue shared monthly based on subscription payments
* **ETH Rewards**: Users receive ETH directly from subscription revenue
* **Direct Claims**: Users claim ETH 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerve-protocol.com/tokenomics/npx-revenue-sharing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.