Skip to main content
When launching an Arx node, specific metadata details about the node must be provided, along with an association to a Node Operator. Node Operators are metadata entities that represent the party operating an Arx node, and may represent multiple Arx nodes.
Arx Node Operators & Clusters

​
Node Operators

Node Operators have a one-to-many relationship with Arx nodes, meaning that Node Operators may run multiple nodes. The following metadata fields are associated with a Node Operator:
  • Jurisdiction: follows the ISO 3166-1 alpha-2 code standard for jurisdictions (e.g. DE for Germany, FR for France, etc.).
  • URL: a URL to a webpage representing the Node Operator (e.g. social media or a webpage detailing the services and reputation of the operator).
Given that these metadata fields are self-declared, the actual hardware location relative to the provided jurisdiction field is not verified by the Arcium Network, however location claims will be independently evaluated by the Arcium Network’s community (along with an operator’s team, security approach, transparency, cross-network reputation, etc.).

​
Metadata

An Arx node’s metadata is unique to that specific node and may vary from an associated Node Operator’s metadata since a single operator may run multiple nodes in, for example, different jurisdictions. This node-specific metadata consists of the following fields:
  • IP & Port: These fields correspond directly to the deployment of the node, specifying the details for RPC access to the Arx node.
  • Jurisdiction: The same ISO 3166-1 alpha-2 code standard that Node Operators follow.
As with the Node Operator jurisdiction field, an Arx node’s jurisdiction field isn’t verified and, therefore, will also be independently evaluated by the Arcium Network’s community.