# Device growth, workload mix, and Rewards profile

* We begin with approximately 25,000 devices focused on VPN workloads, where per-active-device rewards  are in the low-teens USD per month.
* The fleet grows each quarter, and we introduce blockchain full nodes next year. Full nodes earn rewards in the “tens of USD” per active device per month (roughly 2-3× VPN).
* By the end of next year, we target approximately 200,000 devices globally. As the full-node share increases, the blended per-device earnings trend from low-teens toward higher-teens.
* Most devices are active monthly (internally modeled at 80–90%, subject to region, network, and scheduling).

### Quarterly roadmap and workload mix

| Period  | Devices | Workload Mix                    | Per active Device earning |
| ------- | ------- | ------------------------------- | ------------------------- |
| Q4 2025 | 25000   | <p>VPN 100%<br>Full node 0%</p> | Low- teens USD            |
| Q1 2026 | 60000   | <p>VPN 90%<br>Full node 10%</p> | Low to mid teens USD      |
| Q2 2026 | 110000  | <p>VPN 85%<br>Full node 15%</p> | Mid teens USD             |
| Q3 2026 | 150000  | <p>VPN 75%<br>Full node 25%</p> | Mid to high teens USD     |
| Q4 2026 | 200000+ | <p>VPN 70%<br>Full node 30%</p> | High teens USD            |

### Ecosystem Growth and Roadmap

LayerK's growth focuses on node expansion and workload diversification. Starting with VPN, we aim for 200,000+ devices by end-2026, blending in higher-yield jobs like blockchain nodes.

<figure><img src="/files/OXOgzqCLuLKPCrYNfs9S" alt=""><figcaption></figcaption></figure>

<br>


---

# 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://docs.layerk.com/layer-3-iop-and-hardware/device-growth-workload-mix-and-rewards-profile.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.