> For the complete documentation index, see [llms.txt](https://cordnode.gitbook.io/cordnode/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cordnode.gitbook.io/cordnode/overview/what-we-solve.md).

# What we Solve!

## MARKET OVERVIEW AND PROBLEM STATEMENT

**The Rise of DePIN**

DePIN is a fast-growing category in Web3, enabling community powered infrastructure projects such as Helium (wireless), Filecoin (storage), and Akash (compute). However, most DePIN projects still rely on technically skilled users and significant hardware investments.

Despite rapid innovation in DePIN ecosystems, most projects suffer from:

* **High onboarding friction**: Contributors often need complex CLI tools, manual configurations, or expensive hardware.
* **Poor coordination**: Fragmented communication leads to inefficiencies in real-world deployment.
* **Lack of contribution visibility**: It’s hard to audit and reward community members beyond raw infrastructure metrics.
* **Centralized reward logic**: Many reward schemes depend on opaque and centralized systems.

{% hint style="info" %}
These challenges prevent DePIN from reaching its full potential, especially among non-technical participants and grassroots communities.
{% endhint %}

## <mark style="color:green;">CordNode Solution Overview</mark>

<mark style="color:purple;">**CordNode**</mark> creates a **Discord-native DePIN interface** where node tasks, participation, and rewards are integrated directly within Discord communities.

#### KEY COMPONENTS OF CORDNODE

#### Key Components

* **CordBot**: A Discord bot that coordinates task distribution, monitors node status, and manages contributor activity.
* **Node Modules**: Dockerized infrastructure packages that can be deployed easily with CordBot guidance.
* **TaskLayer**: A system for distributing decentralized compute/storage/network tasks to participants.
* **CordNode Token (CORD)**: The native token used to reward node operators and participants for infrastructure provisioning and governance.

#### **CordNode Protocol Layer**

* Handles:
  * Proof-of-Participation (PoP)
  * Proof-of-Resource (PoR)
  * On-chain reward mapping
  * Contributor reputation
* Operates on Solana (L1) for low-cost transactions.


---

# 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://cordnode.gitbook.io/cordnode/overview/what-we-solve.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.