# architecture

<figure><img src="/files/RPw3LXcB11t3htqr5MXe" alt=""><figcaption><p>diagram</p></figcaption></figure>

## DePINs.io Architecture Overview

This page provides a detailed breakdown of the DePINs.io system architecture, explaining how we seamlessly convert idle infrastructure into auto-compounding yield through fully automated orchestration across DePIN and DeFi layers.

***

### 🎯 High-Level Goal

**Turn unused digital infrastructure into yield-bearing stTokens without requiring user intervention.**

***

### 🧩 Core Layers

DePINs.io is designed with three primary layers:

#### 1. **Intelligence Layer**

Handles scoring, matching, and deployment decisions using DUVI.

* **DUVI Scoring Engine (DePIN Utility Value Index):**
  * Takes a call from the controller.
  * Scans the user's available digital resources: bandwidth, compute, GPU, storage, etc.
  * Scores each resource by projected yield potential, security, protocol health, and compatibility.
  * Deploys each resource to its optimal DePIN protocol (e.g., bandwidth → Grass, GPU → Render).

***

#### 2. **Adapter Layer**

Handles connectivity to DePIN and staking protocols.

* **DePIN Protocols:**
  * Grass (bandwidth sharing)
  * Render (GPU rendering)
  * Hivemapper (mapping via dashcams)
  * Helium (wireless infra)
* **Staking Protocols:**
  * Marinade (SOL to mSOL)
  * Jito (SOL staking with MEV)
  * Blaze (liquid staking alternative)

These are abstracted via adapters to standardize interaction across protocols.

***

#### 3. **DeFi Layer**

Manages conversion, staking, and compounding of rewards.

* **Controller**
  * Central orchestrator
  * Accepts user resources (bandwidth, compute, etc.)
  * Coordinates between Intelligence → DePIN → DeFi
  * Operates both **on-chain and off-chain**
* **DEX (Decentralized Exchange):**
  * Performs **real-time swaps** of earned DePIN tokens into SOL or compatible assets.
* **Meta-Vault:**
  * Receives SOL or compatible tokens from the DEX.
  * Stakes into liquid staking protocols.
  * Auto-compounds rewards.
  * Issues receipt tokens (e.g., stSOL, stGRASS) representing yield.

***

### 🔄 Full Flow Walkthrough

#### Step 1: **User Provides Resources**

Users provide access to idle infrastructure (e.g. network, compute).

#### Step 2: **Scan + Score + Deploy**

* Controller calls DUVI → DUVI scores available resources
* High-yield assets are matched to DePIN protocols via the adapter layer

#### Step 3: **DePIN Protocols Generate Rewards**

* Grass, Render, etc., begin earning tokens for the user

#### Step 4: **Rewards Are Swapped in Real-Time**

* Controller triggers swaps via DEX to convert DePIN tokens to SOL

#### Step 5: **Meta-Vault Stakes and Compounds**

* Converted tokens go to the Meta-Vault
* Vault selects protocol (e.g., Marinade, Jito)
* Stakes, compounds, and tracks yield

#### Step 6: **User Receives stTokens**

* Users receive stTokens (e.g., stSOL, stGRASS)
* These represent yield and can be used in DeFi or held for compounding

***

### ✅ Summary

This architecture allows DePINs.io to:

* Fully automate the path from **idle infra → yield-bearing token**
* Maintain **non-custodial control**
* Optimize across both **DePIN and staking ecosystems**
* Deliver **daily compounding returns** with no user setup required


---

# 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://depins-1.gitbook.io/depins-docs/basics/architecture.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.