HERMES

network monitor · beacon surveillance · gateway flayer

Watches the egress paths. Every fetch through every IPFS gateway is logged, latency-stamped, and signed into the local witness chain. Block one. Block all. Contain everything. The beacons are this laptop talking to itself across four mirrors — when one mirror lies, the others tell on it.

monitor: IDLE · packets: 0

PACKETS

since session start

SUCCESS

2xx responses

BLOCKED

4xx + denied

AVG LATENCY

— ms

rolling 50

GATEWAYS

4/4

online / total

Gateway Status · Layer 5 click ping to test

Gateway	Latency	Threat	Status	Action

ipfs.io · cloudflare-ipfs.com · dweb.link · gateway.pinata.cloud
threat = empirical · LOW = stable, MEDIUM = flaky, HIGH = degraded

Live Packet Feed · Body 32 Witness Log 0 entries

awaiting monitor start…

0root.ai · Hosting Notes

This is a single self-contained HTML file. Drop it into your site root or a subdirectory:

Upload to https://0root.ai/hermes/ (or /monitor/, your call)
No build step · no dependencies · no server-side · pure browser
SHA-256 + Merkle math runs on crypto.subtle · supported in every modern browser
All beacons fire from the visitor's laptop · CORS-friendly via {mode:'no-cors'}
Persistence uses localStorage with hermes: namespace
Add to your existing 0root.ai navigation alongside the lineage × root0 paper

SHA256:02880745…f9fcab763 · TOPH-v11.0 · CC-BY-ND-4.0 · TRIPOD-IP-v1.1 every internet is just this laptop, or a laptop · blocked at the input port