# User Journeys & Benefits For Each Stakeholder

The user journeys and benefits for each stakeholder are as follows:

**Step 1:** Buy $PIN tokens.

**Step 2:** Pay Service User Rental Fee to rent hashrate and compute capacity, vetted to be enterprise grade, and performance-optimized by our PinAI suite of machine learning tools.

**Step 3:** Receive rebates on pricing as yields from Service User Rebate Fund accumulates

**Key Benefit:** Discounted pricing on enterprise-grade, performance-optimized compute power due to capital efficiencies of PinLink’s unique RWA-tokenized DePIN marketplace mechanics.

2. **DePIN Asset Owner**

**Goal:** Monetize DePIN asset with maximum flexibility over dynamic revenue generation goals.

**Step 1:** Connect DePIN asset to PinLink

**Step 2:** Mint RWA ERC-1155 representing the asset’s profit streams.

**Step 3:** Receive profits from Service User Rental Fee to secure ongoing gradual income.

**Step 4:** Sell fractions of the RWA whenever they want an accelerated up-front capital injection.

**Key Benefit:** Can dynamically optimize for short-term capital realization or long-term rental profits over time as needed.

3. **RWA revenue output Share** **Buyer**

**Goal:** Secure a source of passive income without having to purchase an entire DePIN asset.

**Step 1:** Buy a fraction of a PinLink RWA representing a DePIN asset’s profit stream.

**Step 2:** Receive passive income from the asset in perpetuity.

**Key Benefit:** Able to tap into DePIN profit streams without having to purchase an entire DePIN asset.


---

# 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://pinlink.gitbook.io/pinlink/why-use-pinlink/user-journeys-and-benefits-for-each-stakeholder.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.