# Becoming a Provider

This guide walks you through setting up your machine as an OpenGPU provider.

## Prerequisites

* Hardware meeting [suggested requirements](/opengpu-network/for-providers/overview.md#hardware)
* Docker Desktop installed and running
* CPU virtualization enabled in BIOS (Intel VT-x, AMD-V, or equivalent)
* At least 11 $OGPU in your master wallet (10 for staking + gas fees)

## Key Terms

**Master Wallet**: Your non-custodial wallet that interacts with the protocol and Vault. All stakes and reward earnings are associated with this self-custodial wallet. You have full control and responsibility for all economic transactions.

**Provider Wallet**: A separate identity used by the Provider Suite to sign task and response transactions. Only needs a small amount of $OGPU for gas fees.

### Wallet Pairing

Master and provider wallets must be paired through bilateral on-chain announcements:

1. Master wallet announces the provider wallet address (via Management dApp)
2. Provider wallet announces the master wallet address (via Provider Suite)

Once both announcements are recorded on-chain, the wallets are paired. This two-way confirmation ensures neither wallet can be linked without the other's consent.

## Setup Steps

### 1. Install Provider Suite

Download from [opengpu.network/provider-suite](https://opengpu.network/provider-suite)

Available for:

* Windows 10/11 Pro
* Linux (Ubuntu 20.04+, CentOS 8+)
* macOS

### 2. Create Provider Wallet

In the Provider Suite:

1. Click Continue and follow the setup steps
2. Choose to generate a new wallet (recommended) or import existing
3. Create a password for the app
4. **Securely save your mnemonic phrase and private key**

### 3. Announce Provider from Master Wallet

1. Go to [management.opengpu.network](https://management.opengpu.network)
2. Connect with your **master wallet**
3. Click **Add Provider**
4. Paste your provider wallet address
5. Click **Announce Provider** and confirm the transaction

This requires at least 10 $OGPU in your master wallet.

### 4. Complete Pairing in Provider Suite

1. Return to the Provider Suite
2. Enter your master wallet address
3. Complete the wallet setup

Once both announcements are recorded, your wallets are paired.

### 5. Start Your Provider

1. Ensure Docker Desktop is running (Docker icon in app should be green)
2. Toggle the switch to activate your provider
3. Status changes from **Inactive** to **Active**

### 6. Register for Sources

1. Go to [management.opengpu.network/sources](https://management.opengpu.network/sources)
2. Click **Register** next to sources you want to support
3. Select your hardware type (CPU Only, NVIDIA, or AMD)
4. Confirm the transaction

The source container downloads automatically and appears in the Provider Suite Monitor tab.

## Verifying Your Setup

1. Go to the Tasks tab on the Management dApp
2. Look for tasks where your provider is attempting or responding
3. Click **Show** on a task to see your Provider Address and Response Address

Tasks are attempted automatically. No manual interaction needed.

## Rewards

Rewards are sent to your master wallet's Vault:

* **Vault Balance**: Current available earnings
* **Total Earnings**: Lifetime earnings

You earn $OGPU for each task your provider completes and confirms.

## Multi-Provider Operations

One master wallet can control multiple provider wallets. This enables:

* Centralized management of stakes and rewards
* Distributed task execution across machines
* Enhanced security (cold storage for master wallet)
* Professional operations at scale

## Monitoring

Track your provider via:

* Provider Suite dashboard (Home, Monitor, System, Controls tabs)
* [Management dApp](https://management.opengpu.network)


---

# 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/becoming-a-provider.md?ask=<question>
```

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.