> For the complete documentation index, see [llms.txt](https://whitepaper.assetchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.assetchain.org/3.0-xend-browser/3.2-nodeos.md).

# 3.2 NodeOs

Installing the Xend Browser on any device also entails the installation of NodeOs, which the device's owner can freely activate or deactivate. NodeOs offers several capabilities:

* The ability to set up and operate a **MicroNode**, which
  * Allows to use the device as one AssetChain validation device
  * Requires linking with a Xend ID.
* Setting up a **rotating uptime or backup procedures** 
  * Users with multiple devices linked to the same Xend ID, all running NodeOS, can implement a 'rotating uptime' strategy for validation. This approach involves programming the devices to alternate their active periods, such as switching every 8 hours. This ensures continuous validation activities without overburdening any single device, maintaining optimal network participation and device longevity.
  * For users with multiple devices, employing them as backup validators offers a resilient solution. Should one device become unavailable, a secondary device can automatically assume the role, stepping in to continue the validation process as a backup MicroNode. This seamless transition helps maintain the required uptime rate for the associated Xend ID, ensuring uninterrupted network participation.
* Transforming the device into a comprehensive hardware ledger that includes:
  * **A Xend ID**,
  * **NodePay**, a feature enabling the device to facilitate both physical and virtual transactions,
  * A Hybrid Wallet, which provides seamless access to the user's Xend Exchange and OAE wallets associated with their Xend ID.

<figure><img src="/files/qW2jaF2IBuTxZQbnuxcZ" alt=""><figcaption><p>- Example of NodeOs setup with single device and multiple devices</p></figcaption></figure>


---

# 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://whitepaper.assetchain.org/3.0-xend-browser/3.2-nodeos.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.