How it works
Read. Sign. Record. Verify.
Four steps, the same for every NVIDIA GPU, and none of them asks you to trust us.
- 01
Read
The reader takes the card's own wear counters, at rest, through the driver.
- 02
Sign
The read is signed on the machine the moment it is taken.
- 03
Record
It is filed in an append-only registry under the card's identity.
- 04
Verify
Anyone can check it, online or offline, with no account.
What is read
19 wear signals, straight from the card.
Memory errors fixed and lost, rows swapped for spares, banks running out of spares, heat, power and links. Each one is explained, with real cards, on one page.
What we do not measure
- Speed under load. Reads are taken at rest and cover condition, not performance.
- Facility power. A card's own sensors cannot see the power feeding it. That stays unassessed.
- Price. A record never states or implies what a card should sell for.
The seal
Signed the moment it is read.
Every record is tamper-evident. Change one byte and the signature no longer matches.
L40S · ···0230 · one signed read
- Model
- L40S
- Serial
- ···0230
- Uncorrectable errors
- 2
- Rows repaired after uncorrectable
- 1
- Repair pending
- 1
- Read
- Sep 30, 2026, 08:41 UTC
{"model":"L40S","read_at":"2026-09-30T08:41:45Z","repair_pending":1,"rows_repaired_uncorrectable":1,"serial_tail":"0230","uncorrectable":2} Signature matches
ECDSA P-384 SHA-384 of the line above cca7d2e6…f57e6ed9
Values from a real signed read, in short form. The signature itself is not shown.
- 01 Read The reader takes the card's own wear counters.
- 02 Sign The read is put in one canonical form and signed on the machine with an ECDSA P-384 key, the moment it is taken.
- 03 Record It is filed in an append-only registry under the SHA-384 of its exact bytes. A root is published daily.
- 04 Verify Anyone can check it offline with the open verifier.
The signature proves the record has not changed since it was signed. It does not yet prove which machine held the key. Hardware-bound signing is our next step.
An append-only registry, with a root published daily.
Records are added and never edited or removed. Each day the registry publishes a root, one value that covers every record filed so far. A changed or missing record would not match it.
Check it yourself, offline.
The verifier is open and published as a Python package. It needs no account and no call to Voltry. It checks the signature against the record's canonical bytes.
pip install voltry-evidence-schema Evidence kept apart
Four kinds of statement, never blended.
- Measured
- A value the card reported, exactly as read. Most of a record is this.
- Derived
- Arithmetic over measured values, such as how far a counter moved between reads.
- Modeled
- An estimate. Always labelled, always dashed, never mixed into a measured line.
- Declared
- Something a person told us, such as who owns the card. Shown with who said it.
Missing evidence is shown as missing. A gap in tracking is shown as a gap, never as a pass.
The research
The litepaper and the methodology draft.
For diligence teams who want every definition. One work email gets private links to both drafts. Links expire after 24 hours.
Litepaper
Draft r11 · 11 pages
Email required
VCM-1 methodology
v0.3 draft · 37 pages
Email required
Sent.
Check your inbox at your address. The message has separate open and download links for both drafts. Links expire after 24 hours.
Draft materials for diligence, not reliance. Select numerical thresholds and grading parameters remain subject to ratification following an upcoming experiment with a national laboratory in the Rocky Mountain region.