# Activity Rewarder The Activity Rewarder is a live network incentive system that automatically rewards active providers in the OpenGPU ecosystem. As our first production client running on mainnet and part of our beta protocol (v0.2.x), the Activity Rewarder also serves as a crucial data collection tool. The real-world usage patterns, performance metrics, and provider behavior data gathered from this client directly inform our ongoing protocol improvements and optimization efforts. The network currently has 240+ active providers contributing compute resources. ## How It Works The system distributes $OGPU rewards exclusively to providers demonstrating consistent activity and availability. Rewards are based on actual network participation rather than passive staking. ## Benefits * **Automatic rewards**: Continuous earnings while your provider remains operational * **No minimum requirements**: All providers qualify regardless of system specs or vault amounts * **Enhanced earnings**: Locked vault amounts boost reward multipliers * **Fair distribution**: Rewards based on availability, lockup amounts, and uptime ## Getting Started 1. Install Provider Suite and set up master and provider wallets 2. Lock $OGPU in vault (optional but increases earnings) 3. Register your provider to the Activity Rewarder source via Management dApp 4. Keep your provider running and connected > See [Becoming a Provider](/opengpu-network/for-providers/becoming-a-provider.md) for setup details. --- # Agent Instructions: 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: ``` GET https://opengpu-network.gitbook.io/opengpu-network/for-providers/activity-rewarder.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.