> For the complete documentation index, see [llms.txt](https://docs.swanchain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swanchain.io/swan-chain-campaign/swan-chain-mainnet/swan-provider-campaign.md).

# Swan Provider Campaign

## Introduction

The Swan Provider Campaign is designed to incentivize participants to contribute computing resources and workloads to the Swan Chain network. By participating, individuals and organizations can compete to earn their share of the 800,000 SWAN tokens prize pool.

### Duration

July 15, 00:00 (EST) - September 29, 23:59 (EST)

### Prize Pool Distribution

* **Total Prize Pool:** 100,000 SWAN tokens
  * **Edge Computing Provider (ECP):**
    * 420,000 SWAN, July 29 - Sep 29
  * **Fog Computing Provider (FCP):**
    * 500,000 SWAN, July 15 - Sep 29
  * **Market Provider (MP):**
    * 80,000 SWAN, July 29 - Sep 15

## Role of the Challenge

Participants will contribute computing resources to the Swan Chain network in the following capacities:

### Fog Computing Provider (FCP)

Fog Computing Providers (FCPs) extend cloud capabilities to the edge of the network, providing scalable and distributed computing services. They play a crucial role in handling AI model training and deployment, leveraging infrastructure like Kubernetes (K8S).

{% hint style="info" %}
**Hardware Requirements:**

* Public IP
* Domain name (\*.example.com)
* SSL certificate
* At least one GPU
* Minimum 8 vCPUs
* Minimum 100GB SSD storage
* Minimum 64GB memory
* Minimum 50MB bandwidth
  {% endhint %}

**Links:**

* [FCP Deployment Guide](/bulders/computing-provider/fog-computing-provider-fcp/computing-provider-setup.md)
* [FCP Token Operations Guide](/bulders/computing-provider/fog-computing-provider-fcp/fcp-token-operations-guide.md)
* [FCP Event Details](/bulders/computing-provider/fog-computing-provider-fcp.md)

### Edge Computing Provider (ECP)

Edge Computing Providers (ECPs) are integral to the Swan Chain ecosystem, specializing in processing data at the source of data generation with minimal latency. They are essential for real-time applications, handling localized tasks directly on devices at the network’s edge, such as IoT devices.

{% hint style="info" %}
**Hardware Requirements:**

* Public IP
* At least one GPU
* Minimum 4 vCPUs
* Minimum 300GB HDD storage
* Minimum 32GB memory
* Minimum 20MB bandwidth
  {% endhint %}

**Links:**

* [ECP Deployment Guide](/bulders/computing-provider/edge-computing-provider-ecp/ecp-setup.md)
* [ECP Event Details](/swan-chain-campaign/swan-chain-mainnet/swan-provider-campaign/edge-computing-provider-ecp.md)

### Market Provider (MP)

Market Providers (MPs) are vital for the distribution and allocation of computing tasks. They facilitate an efficient marketplace where job requesters and computing providers can connect. MPs use an auction engine for job distribution and a payment engine for financial transactions.

**Links:**

* [MP Event Details](https://docs.swanchain.io/~/changes/ydmkfe2iqCT7phfcbKsl/swan-chain/swan-chain-mainnet/swan-provider-campaign/market-provider-mp)


---

# 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.swanchain.io/swan-chain-campaign/swan-chain-mainnet/swan-provider-campaign.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.