> For the complete documentation index, see [llms.txt](https://docs.unich.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unich.com/unich-network/core-principles/the-user-node-model-vs.-the-user-only-model.md).

# The User-Node Model vs. the User-Only Model

In the **User-only model** (most Web2 and most current Web3), the platform interacts directly with the User. Users work, Users receive rewards. This creates two problems: virtual machines can fake "working" at near-zero cost, and the User-platform relationship is a one-way transaction — the User accumulates no productive asset beyond a coin balance that may go to zero.

In **Unich Network's User-Node model**, Users own Nodes, and Nodes are the units that participate in the network. When a User performs an activity, the Node is upgraded, and the Node mines FC according to its upgraded Mining Rate. Three consequences: virtual machines cannot upgrade Nodes (because they cannot perform Peer Meet), Users have a genuine accumulated asset, and the User-network relationship is symmetric and two-directional.


---

# 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://docs.unich.com/unich-network/core-principles/the-user-node-model-vs.-the-user-only-model.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.