> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/security/security-and-risks/node-operator-compliance.md).

# Node Operator Compliance

### About this document

This page summarizes the publicly stated security and compliance posture of the node operators in ether.fi's operator landscape.

* **ISO/IEC 27001:** information-security management system certification.
* **SOC 2:** AICPA Trust Services report. *Type I* attests controls are

  designed correctly at a point in time; *Type II* attests they operated

  effectively over a period (the stronger of the two).
* **Data-center certifications:** whether the underlying hosting providers /

  data centers hold ISO 27001 and SOC 2 attestations.

#### Methodology & disclaimer

Entries are compiled from operators' public disclosures and self-reported information as of the data cutoff above.

## Summary

<table><thead><tr><th>Operator</th><th width="164.990478515625">HQ</th><th width="154.4166259765625">ISO 27001</th><th>SOC 2</th></tr></thead><tbody><tr><td>Galaxy Digital</td><td>USA</td><td>No</td><td>Yes</td></tr><tr><td>Luganodes</td><td>Switzerland</td><td>Yes</td><td>Yes (Type II)</td></tr><tr><td>Stakefish</td><td>BVI</td><td>No</td><td>Yes (Type II)</td></tr><tr><td>Validation Cloud</td><td>Switzerland</td><td>No</td><td>Yes (Type I + II)</td></tr><tr><td>InfStones</td><td>USA</td><td>No</td><td>Yes (Type I + II)</td></tr><tr><td>Node Monster</td><td>Israel</td><td>In progress</td><td>In progress</td></tr><tr><td>Allnodes</td><td>USA</td><td>No</td><td>No</td></tr><tr><td>HashKey Cloud</td><td>Hong Kong</td><td>Yes</td><td>Expected Aug 2026</td></tr><tr><td>P2P.org</td><td>Cayman Islands</td><td>In progress</td><td>Yes (Type I + II)</td></tr><tr><td>Chainnodes</td><td>UK</td><td>No</td><td>No</td></tr><tr><td>eBunker</td><td>Hong Kong</td><td>No</td><td>In progress (Type I)</td></tr><tr><td>DSRV</td><td>South Korea</td><td>Yes</td><td>SOC 1 Type I (SOC 2 in progress)</td></tr><tr><td>Nethermind / Twinstake</td><td>UK</td><td>No</td><td>Yes</td></tr><tr><td>Finoa</td><td>Germany</td><td>No</td><td>No</td></tr><tr><td>Cosmostation</td><td>South Korea</td><td>(renewal pending)</td><td>No</td></tr><tr><td>MAVAN (Pier Two)</td><td>Australia → USA</td><td>Yes</td><td>Yes (Type I + II)</td></tr><tr><td>Stakin</td><td>Estonia</td><td>Yes</td><td>In Progress</td></tr><tr><td>Blockdaemon</td><td>USA</td><td>Yes</td><td>Yes (Type II)</td></tr></tbody></table>


---

# 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://etherfi.gitbook.io/etherfi/security/security-and-risks/node-operator-compliance.md?ask=<question>&goal=<user_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.
