Exact identity
Bind hardware, revision, firmware, driver, phone or Windows platform, app build, vehicle application, module, function, and profile.
Verified compatibility.
No asterisks.
ScanWrench support is earned one exact read function at a time from signed field evidence, independent review, and a current runtime grant. The code never exposes a function outside its installed capability, and no simulated session or paid placement can publish a supported state.
No raw VINsFailures stay visibleNo paid outcomeNo “universal” shortcuts
THE PROTOCOL
What “verified” actually means.
Signed field evidence
Record the actual protocol, responder, read function, result, timing, and evidence integrity on the user’s real configuration.
Independent aggregation
Keep failures visible, separate installations, and require multiple exact vehicles before one observation can become a support decision.
Time-bounded support
A human-reviewed exact read cell receives a signed runtime grant that expires, revalidates, and regresses when contrary evidence arrives.
LIVE PUBLIC LEDGER
Loading registry…Field-verified configurations
Reading the evidence ledger…
Only aggregated, privacy-safe, field-verified reports are returned.
A verified connection proves this adapter/phone/vehicle configuration completed the published protocol. It never means every manufacturer-specific module or feature is supported.