NODE REQUEST · DUAL USE · FAIL-CLOSED

Open an HBCE Node

HBCE nodes are deployed as a federated European network. Node activation is controlled, audited and fail-closed. If identity, license or integrity requirements do not match, node activation is blocked.

Node types

Regional node
Operational verification and coordination for a region. Suitable for early deployment and industrial pilots.
National node
Cross-border continuity and national-level operational infrastructure. Supports institutional scope.
Institutional node
High-responsibility deployment for critical systems and defense-digital environments (dual-use track).

Minimum requirements

VALID operator
At least one operator with VALID IPR and issued operator license.
Node integrity
Node must comply with identity + event + security posture. If integrity cannot be verified, activation blocks.
Manual append-only
Node activation is recorded in the node registry via controlled manual append-only updates.
Fail-closed conditions:

• Operator not VALID → BLOCK • License missing → BLOCK • Node hash invalid → BLOCK • Timestamp invalid → BLOCK • Registry inconsistency → BLOCK

Request payload (what to send)

Send a node request via PEC including:
  • Requested node type (regional / national / institutional)
  • Country (ISO-2), region, city
  • Operator public label + IPR proof reference
  • Proposed node_hash (HBCE- or ORIGIN- prefix)
  • Requested status (PILOT or PLANNED)
  • Short operational note (scope, domain, purpose)
Example (format)
NODE REQUEST — HBCE

type: REGIONAL | NATIONAL | INSTITUTIONAL
country: IT
region: PIEMONTE
city: TORINO

operator_label: <PUBLIC LABEL>
ipr_proof: <payload_sha256 or registry reference>

node_hash: HBCE-IT-PIEMONTE-TORINO-PILOT-0002
requested_status: PILOT

note: <scope + domain + purpose>

Operational contact (PEC)

Node requests and institutional onboarding:
  • PEC: hermeticum@pec.it
  • Operational: manuelcoletta@domiciliodigitale.com