> For the complete documentation index, see [llms.txt](https://frigghome.gitbook.io/frigghome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frigghome.gitbook.io/frigghome/earn/friggbox-depin/earn-eth.md).

# Earn ETH

### Earn ETH by Hosting ETH Validators

Frigg Validator on ETH take 8% of fees and redistribute 50% of revenues to FriggBox.

FriggBox allows you to earn ETH passively by hosting FriggHome's Ethereum validators on your device, without needing to stake your own ETH. As part of our Decentralized Physical Infrastructure Network (DePIN), your FriggBox runs validators at the edge, contributing to Ethereum's decentralization and security. Simply plug it in, and it handles the technical setup, no expertise required.&#x20;

This plug-and-earn model turns your home into a decentralized node, sharing in validator fees while supporting a censorship-resistant infrastructure.


---

# 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://frigghome.gitbook.io/frigghome/earn/friggbox-depin/earn-eth.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.
