# Nodes ## What is a Node? A node is a trusted participant running Circular Protocol's node software. Nodes work together to maintain a synchronized, tamper-proof record of certified data across a given chain/deployment. Unlike traditional systems that rely on a single centralized database, Circular distributes responsibility across multiple independent nodes, enhancing resilience, transparency, and control. Each node processes certifications, validates incoming data, and participates in reaching consensus across a given chain/deployment. This enables organizations to build workflows that are both collaborative and independently verifiable. ## Why Nodes Matter Most enterprise systems rely on centralized infrastructure, which introduces risk: a single point of failure, limited transparency, and potential regulatory bottlenecks. Circular’s architecture distributes trust across a global network of nodes, allowing institutions to certify and verify data without relying on intermediaries. ### This distributed model brings several advantages: * No single point of failure * Independent verification of all actions * Greater data integrity and auditability * Reduced risk of tampering or hidden changes ## Jurisdictional Flexibility Circular supports jurisdictional node deployment, meaning nodes can be hosted in specific regions or by specific organizations to meet local compliance requirements. ### This allows enterprises and governments to: * Operate within national data laws (HIPAA, GDPR, etc.) * Retain sovereignty over infrastructure * Participate in decentralized workflows without exposing data to external jurisdictions * Validate and certify data using trusted, regionally-hosted nodes ## Types of Nodes All nodes on Circular perform the same core functions but may be deployed in different roles based on context: #### Institutional Nodes Operated by hospitals, CROs, research organizations, or governments. These nodes participate in certification workflows and may be required for regulatory compliance. #### Partner Nodes Hosted by trusted partners or collaborators, used to validate certificates or contribute to multi-party processes. #### Public Nodes Part of Circular’s open infrastructure. Used to verify certificates, anchor proofs from private chains, and ensure network-wide integrity. ## Security and Trust Each node runs identical, open-source code and is cryptographically verified to prevent manipulation or misbehavior. All interactions between nodes are signed, timestamped, and independently auditable. Organizations can choose to trust only specific nodes for their workflows, or opt into broader public verification depending on the level of transparency required. ## Benefits of Circular’s Node Model * Resilience If one node goes offline, the network remains operational. * Scalability New nodes can be added to support growing demand or extend regional coverage. * Compliance Control Nodes can be deployed within specific jurisdictions to comply with local regulations. * Transparency Every certification is independently verifiable, even without relying on the original issuer. * Interoperability Nodes communicate across public and private chains, enabling seamless data flows without centralized bottlenecks. ## Summary Nodes are the foundation of Circular’s decentralized infrastructure. They offer the operational reliability of cloud-grade architecture, the regulatory flexibility of jurisdictional deployment, and the trust of cryptographic verification, all without exposing sensitive data or requiring specialized blockchain knowledge. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://circular-protocol.gitbook.io/circular-protocol-documentation/nodes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.