# FAQ #### Do we have to follow the miner/validator role architecture? No, Hypertensor is role agnostic. Subnets are not required to form any hardcoded roles. We believe each subnet should be free to design the best consensus mechanism for its subnet. Because the Subnet Template is decentralized, this allows for fully secure and decentralized communication, allowing for designs you usually only see on blockchains, such as decentralized storage, commit-reveal schemes, etc. When building a subnet, design the consensus that makes the subnet the most secure and fair. #### How do nodes communicate? Nodes are in a Distributed Hash Table (DHT) and communicate by discovering and routing to each other using a Kademlia-based algorithm. For more information, see our [Kademlia Visualizer](https://hypertensor-blockchain.github.io/kademlia_vis/basics/1/). #### Is there a standard on how to store nodes in the DHT? Yes. To store nodes, each node should be stored under the "nodes" key. Each node should update itself by utilizing the built-in [heartbeat](/subnet-template/server/heartbeat-thread.md) mechanism. The **reason for this standardization** is that **Overwatch Nodes** will expect this format when looking up nodes. --- # 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.hypertensor.org/build-a-subnet/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.