# FAQ ## MAINNET ### What are the hardware requirements for participating in NodeSet? Currently the requirements for operating a NodeSet node are the same as [those of Ethereum solo staking](https://docs.ethstaker.cc/ethstaker-knowledge-base/hardware/hardware-requirements). This is because the only NodeSet opportunities available at the moment are for Ethereum staking, but in the future, as opportunities expand, hardware requirements for those will be listed separately. If you're looking for low-cost hardware with minimum power draw, we recommend taking a look at [the Proteus, a project developed by our Lead Client Engineer, Joe Clapis](https://github.com/mercadian/proteus/wiki). ### Where can I get support for my node operation? The [NodeSet community Discord server](https://discord.gg/dNshadxVkg) is the best place for discussing your operation with others. If you have general questions around operations, this community is kind, welcoming, and highly technical.\ \ If you notice an opportunity for improvement with with any of our technical implementations, please open an issue on the relevant repository [on the NodeSet GitHub](https://github.com/nodeset-org). ## TESTNET ### How long do operators need to have a validator active on testnet before gaining access to mainnet? There is no minimum time. You can exit it immediately and still have access to mainnet. However, we always recommend keeping a test environment online if possible so you can test changes to your configuration, new Hyperdrive versions, etc. --- # Agent Instructions: 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: ``` GET https://docs.nodeset.io/node-operators/faq.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.