Everything you need to know.

chainNode is a real-time asset intelligence and compliance platform. Its automated discovery agent, Calibrant, finds every networked device in your facility — PLCs, sensors, cameras, servers, switches — fingerprints their configuration, and writes that fingerprint to the Polygon blockchain.

This gives you a tamper-proof, independently verifiable record of what's on your network and when it changed. Auditors can verify your records without needing a chainNode account — just a browser and Polygonscan.

Under 5 minutes from signup to seeing your first assets:

• Step 1: Subscribe at chainnode.pro and set your password from the welcome email
• Step 2: Log into the dashboard at dash.chainnode.pro and create an API key
• Step 3: Run the installer on any machine on your network:
  Linux/macOS: curl -fsSL https://chainnode.pro/install.sh | sudo bash
  Windows (PowerShell as Admin): irm https://chainnode.pro/install.ps1 | iex

Assets appear in your dashboard within minutes of the first scan.

The chainNode agent runs on Linux (Ubuntu 20.04+, Debian 11+, RHEL 8+, CentOS 8+), macOS (Ventura or later), and Windows (10/11, Server 2019+). It requires:

• Python 3.11+
• nmap (installed automatically on Linux/macOS; download from nmap.org on Windows)
• Outbound HTTPS access to Supabase (port 443)
• Network access to the subnets you want scanned

The agent is lightweight — it uses minimal CPU and memory. It runs best with elevated privileges (root/sudo on Linux/macOS, Administrator on Windows) for OS detection.

No inbound ports. The agent only makes outbound HTTPS connections to the chainNode API. No firewall changes, no port forwarding, no DMZ configuration. It works from behind NATs and corporate firewalls.

Polygon (formerly MATIC) — a public, Ethereum-compatible blockchain. Polygon is used by major enterprises (Stripe, Reddit, Starbucks) and offers low-cost, fast transactions while maintaining the security guarantees of a public ledger.

Every chainNode transaction is publicly visible on Polygonscan.

Each asset event writes a transaction containing:

• Config hash — a SHA-256 fingerprint of the device's full configuration (hostname, IP, MAC, OS, firmware, ports, etc.)
• Metadata envelope — asset ID, hostname, IP, asset type, change type, and timestamp
• Description — human-readable label visible on Polygonscan

The full asset data stays in your chainNode database. Only the cryptographic fingerprint goes on-chain — this is enough to prove tampering without exposing sensitive network details publicly.

Yes. That's the point. Every compliance report includes Polygonscan links for every record. An auditor can click any link, see the transaction on the public blockchain, decode the metadata, and confirm the config hash matches — all without logging into chainNode, contacting us, or trusting anyone.

We provide an Auditor Verification Guide in the Welcome Package that walks third parties through this process step by step.

No. Blockchain writes happen asynchronously after the asset is recorded in your database. The dashboard reflects new assets immediately — the on-chain confirmation follows within seconds. Polygon block times are approximately 2 seconds.

Your asset data is always saved locally first — a blockchain failure never causes data loss. Failed transactions are automatically placed in a retry queue with exponential backoff (up to 5 attempts). Once the blockchain is available again, the transaction is retried and your records are updated with the on-chain proof. The dashboard shows a "pending" indicator until the TX confirms.

When Calibrant discovers a device, it sends the configuration fingerprint to chainNode's server-side AI. The AI analyzes open ports, protocols, OS signatures, and firmware to determine:

• Asset type — server, PLC, HMI, sensor, camera, network device, etc.
• Risk level — critical, elevated, standard, or low
• Confidence score — 0–100% certainty
• Risk notes — plain-English explanation of the assessment

All AI processing happens on chainNode's servers. No AI API keys or third-party credentials are needed on the agent.

Yes. On the Asset Detail page, you can change the classification dropdown to any asset type. Your override becomes the source of truth. The AI's original classification and confidence score are preserved for reference.

When a device's configuration changes between scans, the AI analyzes the change to determine if it's expected (scheduled firmware update) or suspicious (unauthorized port opened, OS changed). Anomalous changes are flagged with an amber badge in the dashboard and can trigger alert rules.

Information security & general:

• SOC 2 — Service Organization Control 2 (incl. Type II)
• ISO 27001 — Information Security Management
• HIPAA — Health Insurance Portability and Accountability
• PCI-DSS — Payment Card Industry Data Security Standard
• NIST — Cybersecurity Framework & SP 800-53
• FDA — 21 CFR Part 11 (pharmaceutical/life sciences)

Utility, energy & nuclear:

• NERC CIP — Critical Infrastructure Protection for the bulk electric system
• NRC 10 CFR 50 — Nuclear facility operations records
• TSA Pipeline Security — natural gas & oil pipeline cybersecurity

Cybersecurity & federal:

• FedRAMP — cloud services for federal agencies
• CMMC — Cybersecurity Maturity Model Certification (defense contractors)

Software asset management:

• ISO/IEC 19770 — IT asset management
• BSA — software audit compliance

Each report (PDF or CSV) includes:

• Asset inventory — every device with hostname, IP, type, risk, status, and blockchain TX hash
• Change log — every configuration change with anomaly flags and on-chain proof
• Alert history — every alert fired, with severity, acknowledgment status, and ACK TX hash
• Report hash — the report itself is hashed and written to the blockchain as an attestation

Every row has a clickable Polygonscan link so auditors can independently verify each record.

Yes. NERC CIP requires utilities to maintain tamper-proof records of every change to bulk electric system cyber assets. Calibrant automatically discovers and classifies utility infrastructure — substation RTUs, distribution-automation controllers, SCADA servers, smart meters, and pipeline SCADA — and chainNode anchors every configuration change permanently to the Polygon blockchain. The NERC CIP compliance report highlights each monitored asset and its on-chain configuration state, providing independently verifiable evidence for audits.

Yes. NRC 10 CFR 50 requires complete, unalterable records for nuclear facility computer systems. chainNode classifies and monitors reactor protection systems, safety parameter display systems, plant computer systems, radiation monitors, and emergency core cooling controllers — recording a permanent blockchain state before and after every configuration change. Because records live on a public blockchain, they can be independently verified for license renewal and regulatory review without a chainNode account.

Yes. chainNode's Software License Registry tracks every software deployment against its license entitlement. License purchase documents are hashed and anchored on the Polygon blockchain, creating an audit-ready, unalterable record of what you bought and deployed. Over-deployed licenses — a deployment count exceeding your entitlement — are flagged in red so you can resolve compliance risk before an Oracle, SAP, or Microsoft auditor arrives. It maps directly to ISO/IEC 19770 and BSA software-audit requirements.

Yes. SOC 2 Type II audits require evidence that security controls were in place and operating over a reporting period. chainNode continuously monitors security-control infrastructure — vulnerability scanners, SIEM servers, privileged access workstations, HSMs, and code signing servers — and anchors their configuration state on-chain. These blockchain-anchored, point-in-time records are exactly the kind of independently verifiable evidence SOC 2 (and FedRAMP and CMMC) auditors trust.

The default scan interval is every hour — faster than IBM TADDM (daily/weekly), ServiceNow (daily), Device42 (daily), and Qualys (daily/weekly). You can tune it down to every 5 minutes for critical infrastructure or up to daily for quiet environments.

Change the scan_interval value in the agent's config.yaml (in seconds) and restart the agent.

Calibrant uses lightweight fingerprint-based discovery, not heavy credentialed deep scans. The nmap probes are non-intrusive — they identify open ports and service banners without authenticating to devices. Network impact is negligible, even on sensitive OT/ICS environments.

Yes. In the agent's config.yaml, add IPs or CIDRs to the exclude_hosts list. The agent will skip them entirely.

Yes — every plan includes a 14-day free trial. Your blockchain records persist even if you cancel.

Your blockchain records are permanent — they exist on Polygon and cannot be deleted by anyone, including us. Your database records (asset details, change history, reports) are retained for 90 days after cancellation. You can export everything as CSV before canceling.

Yes. Go to the Subscription page in your dashboard and click "Manage Billing." This opens the Stripe billing portal where you can change plans, update payment methods, or view invoices.

No. The agent scans for device fingerprints (open ports, OS, services) — it does not capture or transmit network traffic, packet contents, or credentials. Only configuration metadata and hashes leave your network.

Asset data is stored in Supabase (PostgreSQL, hosted on AWS). Blockchain proofs are on Polygon mainnet (public, immutable). Compliance reports are stored in Supabase Storage (encrypted at rest). All API communication is TLS-encrypted.

API keys are shown exactly once at creation. Only a SHA-256 hash is stored in the database — the plaintext key cannot be retrieved, even by chainNode staff. If a key is compromised, deactivate it immediately from the API Keys page and generate a new one.

Each agent generates a SHA-256 fingerprint from the host machine's hostname and machine ID. This fingerprint is sent with every API request. On first connect, the agent is auto-registered. After that, only agents with matching fingerprints can use that API key — preventing unauthorized use of a stolen key from a different machine.

Yes — the chainNode companion app is available for iPhone and iPad (via TestFlight during beta, App Store coming soon). Android is supported via Flutter — same codebase, same features.

The app includes: Dashboard overview, asset search, Network Canvas (zoomable floor plan), alerts with acknowledgment, and full asset detail with blockchain verification.

Generate a Dashboard type API key from the web dashboard. Enter it in the app's login screen. The app connects instantly and auto-loads on every subsequent launch.