> For the complete documentation index, see [llms.txt](https://docs.gridlock.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridlock.network/guardians/all-about-guardians/can-a-hacker-combine-the-devices-in-my-network.md). # Can a hacker combine the devices in my network? Gridlock's design ensures that only the user's device can access their crypto, providing robust protection against potential hackers. Even if a hacker somehow managed to guess your account credentials, the security measures in place would limit their access to a 'Read Only' mode. This means they would be unable to perform any transactions or make unauthorized changes. To successfully steal your crypto, a hacker would need to gain access to your device, your Guardian's devices, and other secure devices within your network. The distributed nature of Gridlock's security infrastructure makes it highly unlikely for all these devices to be compromised simultaneously. Therefore your crypto assets remain secure as only your device has the capability to initiate transactions. The decentralized and protective nature of Gridlock's ecosystem ensures that your assets are well-guarded against potential theft. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gridlock.network/guardians/all-about-guardians/can-a-hacker-combine-the-devices-in-my-network.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.