Hardware & Rig
Your rig is a physical machine with real constraints, and the same operator status that governs it is written to disk every second so you can drive your own hardware off it. This page covers both: the rig you run on, and the companions you can wire up around it.
Hardware & rig
Section titled “Hardware & rig”Your rig is a physical machine with real constraints. Open the Hardware Monitor to see live thermals, power draw, and component status.
Components
Section titled “Components”| Component | Role |
|---|---|
| GPU | Graphics card, used for cracking (hydra, john, wifi_crack) |
| CHASSIS | Case, determines cooling capacity and noise |
| COOLING | Fans or liquid cooling, manages heat dissipation |
| PSU | Power supply, sets your wattage ceiling |
| NETWORK | NIC, affects download and upload speeds |
Thermal physics
Section titled “Thermal physics”Components generate heat during operation. GPU-heavy tasks (cracking, mining) push thermals up fast.
| Zone | Range | State |
|---|---|---|
| Green | Below 70C | Safe operation |
| Amber | 70-85C | Elevated, cooling working hard |
| Red | Above 85C | Critical, risk of component failure |
Upgrades
Section titled “Upgrades”Visit node://darkmarket.onion in the web browser to buy hardware upgrades. Better components enable:
- Faster password cracking
- More simultaneous operations
- Greater power headroom
Your rig generates noise proportional to fan speed and component load. Some properties have noise limits, and exceeding them draws attention.
Hardware Companions
Section titled “Hardware Companions”Hardware Companions let you drive external hardware off your live operator status: a Pi, an ESP32, a browser overlay, whatever you can wire up.
What it is
Section titled “What it is”Every second, NODE writes a snapshot of your operator status to a JSON file on disk. External scripts and microcontrollers poll that file and turn it into anything you want: heat-aware LED rings, OLED displays on your desk, a Discord bot that screams when feds raid your safehouse, an OBS overlay for streams. The game writes; you decide what listens.
What you can build
Section titled “What you can build”Three reference shapes. None are mandatory, they are starting points.
| Build | Cost | What it is |
|---|---|---|
| Cheap ambient dashboard | ~$15 | Raspberry Pi Zero W plus a 0.96” I2C OLED screen. Shows heat, trust and connected IP in retro green text, powered off USB. Sits next to the monitor. |
| RGB raid alarm | ~$10 | ESP32 plus a WS2812 NeoPixel ring (8 or 16 LEDs). Idle dim cyan, heat 0-5 green, 5-7 amber, 7+ red strobe. Fed raid: full red blink with an optional buzzer. |
| Browser dashboard | free | A local HTML page that polls the JSON with fetch(). Doubles as an OBS browser source if you stream. No hardware needed. |
The file
Section titled “The file”The status file lives in your Godot user data directory:
| Platform | Path |
|---|---|
| Linux / Steam Deck | ~/.local/share/godot/app_userdata/NODE Protocol/node_status.json |
| Windows | %APPDATA%\Godot\app_userdata\NODE Protocol\node_status.json |
- Update cadence: every 1 second on a heartbeat timer, plus an instant rewrite on critical events (fed raid start and end).
- Atomic writes: the game writes to a temp file then renames it, so readers never see partial JSON. It is race-free, so poll as fast as you like.
- Disable: System tab, Hardware Companions, toggle off. When disabled the file is not updated and the timer does not tick.
JSON schema (v1)
Section titled “JSON schema (v1)”{ "schema": 1, // schema version (increment = breaking change) "ts": 1714398234, // unix timestamp of this snapshot "heat": 4.2, // 0.0-10.0 federal pressure "trust": 12, // operator reputation "investigations": 2, // active investigations against you "closest_hops": 3, // hops to your IP from nearest trace (-1 if none) "monitored": false, // true during post-raid monitoring window "btc_hot": 0.234, // spendable BTC "btc_cold": 1.450, // cold-storage BTC (raid-immune) "btc_total": 1.684, // sum of hot + cold "btc_taint": 0.42, // 0.0-1.0 taint level "btc_price_usd": 65000.0, // current BTC market price "rig_temp_c": 73.4, // CPU/GPU temp in celsius "rig_power_w": 412.0, // total wattage draw "rig_throttling": false, // thermal throttle active "rig_shutdown": false, // rig offline "connected_ip": "107.168.22.34" // current target shell ("" if not connected)}Reference Python build
Section titled “Reference Python build”A minimal Pi sketch. It polls every second and prints to stdout. Replace the print with whatever output you want: an OLED draw, an MQTT publish, a NeoPixel update. The polling loop is the only piece you keep.
#!/usr/bin/env python3import json, time, os
# Adjust to your platform. See THE FILE section above.STATUS = os.path.expanduser("~/.local/share/godot/app_userdata/NODE Protocol/node_status.json")
while True: try: with open(STATUS) as f: s = json.load(f) heat = s.get("heat", 0.0) trust = s.get("trust", 0) ip = s.get("connected_ip", "") if s.get("monitored"): tag = "[MONITORED]" elif heat >= 7: tag = "[!!!]" elif heat >= 5: tag = "[!]" else: tag = "" print(f"heat={heat:.1f} trust={trust} ip={ip or '-'} {tag}") except (FileNotFoundError, json.JSONDecodeError): # File rotates atomically; transient errors are harmless. Skip. pass time.sleep(1)