# Infrastructure & Network

#### Connectivity

EtheLock relies on decentralized and distributed infrastructure to ensure uptime and censorship resistance.

**RPC Nodes**\
We aggregate connections to multiple Remote Procedure Call (RPC) providers to ensure the dashboard always loads, even if one provider goes down.

* **Primary:** Alchemy, Infura.
* **Failover:** QuickNode, Public RPC endpoints.

**WebRTC (Peer-to-Peer)**

* **STUN Servers:** Used to resolve public IP addresses behind NATs (Google STUN).
* **TURN Servers:** Encrypted relays used only if a direct P2P connection fails (e.g., strict corporate firewalls).

**Data Persistence**

* **Settings:** Browser LocalStorage (AES encrypted).
* **Backups:** IPFS (InterPlanetary File System) for decentralized storage of encrypted recovery files (optional).

#### Open Source

The core logic of EtheLock is open source. We believe security through obscurity is a fallacy.

* **Repository:** github.com/ethelock
* **License:** MIT / Apache 2.0
* **Verifiable Builds:** We provide checksums for our mobile application binaries to ensure the code on GitHub matches the app in the store.


---

# 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.ethelock.xyz/5-technical-specifications/infrastructure-and-network.md?ask=<question>
```

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.