Every organization with authority over the veri5 Network is named. This registry is the public face of the Network's accountability model — Operating Charter, Article 8.1.
Operating organization and country of operation are disclosed for every node. Region is shown only with the operator's consent. One further node is onboarding and will be marked Active once it joins consensus on production-grade hosting.
| Node | Operating organization | Country | Region | Role | Joined | Status |
|---|---|---|---|---|---|---|
| veri5-node-01 | Hefes LLC | 🇩🇪Germany | — | Operator | 2026-06 | Active |
| veri5-node-02 | Hefes LLC | 🇩🇪Germany | — | Operator | 2026-06 | Active |
| veri5-node-03 | Hefes LLC | 🇲🇾Malaysia | — | Operator | 2026-06 | Active |
| veri5-node-04 | Hefes LLC | 🇲🇾Malaysia | — | Operator | — | Onboarding |
Objective: no fewer than 7 validator nodes across at least 3 countries, with a share operated by independent node operators, such that the failure of any single party — including the Operator — cannot halt the Network. Operator-led is not a single point of failure: a springing continuity license + escrow let node operators keep it running (Art. 10–11).