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

# FAQ

### Q: How long does it take for my node to sync?

**A:** Initial sync can take anywhere from a few hours to several days depending on your hardware and network connection.<br>

### Q: When will I start earning rewards?

**A:** You will start earning rewards after:

1. Your node is fully synced
2. You've deposited your stake
3. Your validator has been activated (which can take several days)<br>

### Q: How can I check if my validator is active?

**A:** Visit the BLOCX Explorer at <https://beacon.blocxscan.com/validators> and search for your validator index or public key.<br>

### Q: What should I do if I need to move my validator to a different machine?

**A:**

1. Back up your validator keys
2. Stop the validator on the old machine
3. Set up the new machine
4. Copy your keys to the new machine
5. Start the validator on the new machine<br>

### Q: What happens if my node goes offline?

**A:** You will incur small penalties while offline. These penalties are designed to be approximately equal to the rewards you would have earned, so you'll stop earning but not lose your principal as long as you get back online in a reasonable timeframe.<br>

### Support

If you encounter issues not covered in this guide:

1. Check the BLOCX. community Discord for help
2. Open an issue on the GitHub repository

***

Remember that running a validator comes with responsibility. Keep your node updated, secure, and online to maximize your rewards and contribute to the BLOCX network.


---

# 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://blocx.gitbook.io/blocx./validator-node/faq.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.