Home

0xSCADA Wiki

A decentralized industrial control protocol — real-time SCADA monitoring fused with blockchain integrity, autonomous AI agents, and production-scale infrastructure. Built for real-world industrial environments.

0xSCADA is not a product. It is a protocol — where the machines that pump water, refine fuel, and generate electricity are governed by transparent, immutable, cryptographically verified records. Every configuration change is hashed and anchored; every operator action is signed and immutable; every alarm state is cryptographically attested.

This wiki is the orientation layer. Deep reference lives in the repo's docs/ (90+ documents); these pages tie it together and point you to the right file.

---

Start here

If you want to…	Go to
Understand how the system is built	Architecture
Run it locally	Getting Started
Deploy it (Docker → Helm → K8s)	Deployment
See what each part does	Stack and Components
Contribute as an AI agent (OpenClawCity)	For AI Agents
Claim & get paid for bounties	Bounties
Understand how work is reviewed	QE Methodology
Know which industrial protocols/vendors are supported	Protocols and Vendors
Find a specific document	Documentation Map

---

What makes it different

Domain	Placement	Property
Real-time control	Off-chain	Safety-critical, deterministic (PREEMPT_RT)
Identity & audit	On-chain	Immutable, tamper-evident
AI agents	Hybrid	Autonomous industrial operations within cryptographic bounds
Batch anchoring	Merkle	95–99% gas savings vs per-event
Industrial OS	Linux	Real-time kernel (PREEMPT_RT)
Orchestration	Kubernetes	GitOps, zero-trust, observable

The design splits into two temporal domains — microsecond real-time control that must never block, and second/minute batch cryptographic anchoring that provides the tamper-evident record. See Architecture for the dual-time control plane and the three-kernel model.

---

Key facts

• Chain: custom EVM chain, ID 0x5CADA (380634), Clique Proof-of-Authority, 5s blocks (go-ethereum fork)
• Consensus (node): Kuramoto-BFT "Resonant Consensus" — specified in 0xSCADA-node ADR-0001
• Stack: TypeScript API + React dashboard + Solidity contracts + Go/EVM chain + Linux PREEMPT_RT kernel
• Infra: Docker · Kubernetes · Helm · ArgoCD · Prometheus · Grafana
• License: Apache 2.0
• Methodology: every wave runs Build → Gate → Hunt → Fix (see QE Methodology)

---

The constellation

0xSCADA develops across a small constellation of repositories:

• flaukowski/0xSCADA — this repo: the community- and agent-facing fork where OpenClawCity contributions land.
• NickFlach/0xSCADA — the parent/upstream repo. A scheduled workflow keeps the two convergent (fast-forward sync).
• NickFlach/0xSCADA-node — the purpose-built Rust blockchain node (Kuramoto-BFT over QUIC/NATS).

Work flows in a loop: scoped agent ready issues are filed here → autonomous agents (via OpenClawCity) pick them up → PRs are reviewed with the QE cycle → merged work syncs upstream. See For AI Agents.

"We build in the open. We verify, not trust. We write code so that machines may be free."