> For the complete documentation index, see [llms.txt](https://spaceagri.gitbook.io/spaceagridocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spaceagri.gitbook.io/spaceagridocs/protocol-mechanics/1.-protocol-mechanics-and-yield-framework.md).

# 1. Protocol Mechanics & Yield Framework

### Blind Box Mechanics, Probability & Yield Model

#### Core Mechanism

Users purchase Blind Boxes using **USDC** and receive **Agri NFTs** with embedded computing power.\
These NFTs are directly connected to SpaceAgri’s **cloud mining pool**, producing **PTS**.

* Blind Box purchases are **cumulative**
* Total purchase amount determines the **matched device tier**
* Yield is calculated based on the corresponding **AgriPod hardware class**

#### Blind Box Pricing & Rarity Distribution

| Blind Box Type | Price (USDC) | N (Common) | A (Rare) | S (Epic) | SS (Legendary) |
| -------------- | ------------ | ---------- | -------- | -------- | -------------- |
| SeedBox        | 9.9          | 94.55%     | 5%       | 0.3%     | 0.15%          |
| SproutBox      | 99           | 38%        | 56%      | 5%       | 1%             |
| PrimeBox       | 299          | 0%         | 55%      | 40%      | 5%             |

#### Yield Estimation & Reference Model

**Computing Power Matching Rule**

During the campaign period, users’ **total Blind Box spending** is matched against the price tiers of official **AgriPod hardware devices**.

Once the cumulative amount reaches a specific tier, the user is considered to participate in yield generation at that tier.

**PTS Valuation Assumption**

* Blind Box output is calculated using a reference price of\
  **1 PTS = 0.1 USDC**

**Estimated Daily Yield Rate**

Based on real hardware production benchmarks, the estimated **static daily return** after reaching each tier is approximately:

* **0.5% – 1.0% per day**

| Cumulative Spend (Reference) | Device Tier | Daily PTS Output | Daily Value (0.1 USDC / PTS) | Estimated Daily Yield |
| ---------------------------- | ----------- | ---------------- | ---------------------------- | --------------------- |
| $750                         | AgriPod     | 37.5 PTS         | $3.75                        | \~0.5%                |
| $1,500                       | AgriPod Pro | 112.5 PTS        | $11.25                       | \~0.75%               |
| $3,000                       | AgriPod Max | 300 PTS          | $30                          | \~1.0%                |

> Note: These figures are **reference estimates** based on hardware benchmarks and do not represent guaranteed returns.

### AgriPod Hardware Yield & Delivery Process

#### Yield During Bonus Acceleration Season

During the **SPAG & PTS Bonus Acceleration Season**\
\&#xNAN;**(2026-01-05 00:00 – 2026-01-26 00:00 UTC)**:

* **AgriPod ($750):** 37.5 PTS / day
* **AgriPod Pro ($1,500):** 112.5 PTS / day
* **AgriPod Max ($3,000):** 300 PTS / day

> Device computing power is included in the **global network hash rate**, which affects post-event settlement weight.

#### Device Architecture

* **AgriPod is a DePIN physical node**
  * Sensors, control system, AI growth models
  * Collects temperature, humidity, lighting, nutrient solution, growth metrics
  * Data is recorded on-chain
* **Dual-Pod Architecture**
  * **Physical pod at user location**
  * **Cloud cultivation pod cluster**
    * Local data accumulation
    * Cloud-side participation in scaled validation and commercial farming
    * Shared RWA revenue distribution and protocol incentives

#### Hardware Delivery Process

1. **Order & Information Confirmation**\
   Select device model → Submit shipping information
2. **Production Scheduling & Dispatch**\
   Order enters production / inventory queue → Shipping label generated
3. **Logistics & Delivery**\
   International or local shipping → User receives device
4. **Device Binding & Node Activation**\
   Bind wallet and device via App / Website → Device goes online as a node\
   (data upload + on-chain recording)
5. **Dual-Pod Activation**\
   Physical pod begins cultivation and data contribution\
   Cloud pod joins cluster tasks, validation, and rights allocation

### PTS → SPAG Conversion Mechanism

#### Conversion Rules

* **Conversion window:** 180 days
* **PTS can only be converted to SPAG within the window**
* Each conversion **burns the corresponding amount of PTS**, forming a deflationary loop

#### Time-Based Conversion Multiplier (Example Curve)

| Holding Duration | Conversion Multiplier |
| ---------------- | --------------------- |
| Day 1            | 0                     |
| Day 7            | 0.5x                  |
| Day 15           | 1.0x                  |
| Day 30           | 2.0×                  |
| Day 60           | 3.0×                  |
| Day 90           | 4.0×                  |
| Day 120          | 6.0×                  |
| Day 150          | 8.0×                  |
| Day 180          | 10× (Cap)             |

> The longer PTS is held, the more SPAG each unit can be converted into.\
> Participants may freely choose between **early liquidity** or **time-amplified conversion**, depending on individual strategy.


---

# 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://spaceagri.gitbook.io/spaceagridocs/protocol-mechanics/1.-protocol-mechanics-and-yield-framework.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.