> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/faq/hardware-and-node.md). # Hardware and Node ### Q1: Can I participate with Cloud Node without buying hardware? Yes. Cloud Node is a zero-hardware participation method. Through the five-level upgrade system from L1 to L5, users can continuously accumulate Hash Power and rewards. It is suitable for users who do not want to manage physical hardware. ### Q2: Does the device need to stay powered on all the time? What happens if it goes offline? It is recommended to keep the device online 24/7 as much as possible. Device uptime and task completion quality directly affect mining rewards and node reputation. Long periods of offline status may significantly reduce rewards and may even affect node level. ### Q3: How long does it take to recover the cost after purchasing MiuroBox? The payback period depends on the device model, participation timing and market conditions. Early participants usually have a faster payback period. For reference, users can check the ROI estimates in the Appendix. These estimates are for reference only and do not constitute a commitment. ### Q4: Can multiple devices run at the same time? Yes. Multiple MiuroBox devices can run at the same time, but users should consider network bandwidth, power supply and cooling conditions. It is recommended to start with 1–2 devices, then add more after becoming familiar with the system. ### Q5: What should I do if the device breaks or needs repair? The device comes with a 1-year standard warranty. If any issue occurs, contact official support at and follow the instructions for after-sales service. --- # 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.miuro.ai/faq/hardware-and-node.md?ask=&goal= ``` `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.