The reader
The reader. Read only, offline, signs on the host.
The reader takes a GPU's own wear counters and signs them on the machine. It is the same software behind every Voltry record.
Install the reader
pipx install "voltry-probe[hardware]" Read every GPU, sign the read
voltry scan --signing-key operator.pem --out bundle.json Turn it into a page you can open offline
voltry cert bundle.json --out record.html Voltry reader 0.3.3 (package voltry-probe). Python 3.10 or newer.
Posture
Four promises to the person running the host.
- Reads, never writes
- A read never writes to the card, resets it, changes its settings or puts load on it.
- Works offline
- Reading and checking need no network. Sending a record to the registry is a separate step you choose.
- Small
- One Python package. No kernel module, no service left running, nothing to uninstall but the package.
- Scope stated
- NVIDIA GPUs, read through the driver's own interface (NVML). Nothing else yet.
What leaves the host
The signed record, and only when you send it.
Raw readings stay on your machine. Submitting to the registry is its own command, with a consent flag.
Your host
- IdentityModel, serial, board part, VBIOS, InfoROM, driver.
- MemoryErrors fixed and lost, rows swapped for spares, spare rows left per bank, repairs waiting.
- Heat and powerIdle temperature against its limit, power limit against the default, slowdowns.
- LinksPCIe width and speed, retransmissions, NVLink errors where present.
The reader reads, then signs
Signed record leaves, when you submit it
Append-only registry, root published daily
Anyone can check it, online or offline
For tracking
Keeps reading, on a timer.
Tracking runs the same read on a schedule and submits each signed read with a receipt. A resident service comes later. Reads are taken at rest and cover condition, not speed under load.