7.8 Node Naming

Go To Top

Return to Naming and File Conventions

Node names should identify the runtime participant and its role in the Phase 0 Node network. A Node name should help the team understand what the Node represents, which logical role it supports, and how it participates in Control Plane and Data Plane interactions.

Node names should use stable logical or demonstration role names rather than local process names, developer initials, or container names. The implementation may map a Node to a process, executable, service, or container, but the Node name should preserve the architectural role.

Representative Node names may include:

• fx-reference-data-node
• fx-contract-ingestion-node
• fx-validation-node
• fx-calculation-node
• fx-attestation-node
• fx-release-node
• control-plane-observer-node

For Phase 0 Hello World Nodes, the team may use simplified names, but those names should still point toward the future demonstration role rather than remaining generic placeholders. For example, fx-validation-node is more useful than hello-node-3.

The team should document every Phase 0 Node in the Node Catalogue. The catalogue should identify the Node name, Node type, purpose, implementation language, Configuration file, published topics, subscribed topics, Lifecycle behaviour, and Control Plane status behaviour.