NUMBERING · UNIFIED GPU IDENTITY
Is there a global unified GPU numbering (unified coding) system or company?
No — no institution on earth issues unified GPU numbers the way SAE issues automotive VINs, and none ever had the authority. The reason is structural: a GPU is chip, board and full machine in three layers, with no single legal subject and no statutory stamping duty. What does exist is an open provenance layer: CVIN (Compute-asset Verification & Identification Number) gives every registered compute device a globally unique, machine-verifiable identity on an append-only public record — The registry currently holds 92,527 real observations across 16,617 devices (as of 2026-11-13); lookups are free and serials are hashed locally, never uploaded.
01
First, disambiguate: which layer do you mean
| Instruction-set / compiler-layer "coding" | Device-identity "numbering" | |
|---|---|---|
| What | Intermediate representations and open standards: SPIR-V, MLIR, StableHLO, SYCL | A globally unique "who is this exact device" number, like an automotive VIN |
| Solves | Running one codebase/model across many vendors' GPUs | Checking THIS card's history before a used purchase, loan, or insurance quote |
| Unified authority | Yes：Khronos Group, Google (MLIR) and other standards bodies | No：No statutory issuer; only voluntary open registries |
| This page | Compiler layer already has standards | ← missing layer; this page |
Both readings of "unified coding" can be valid — it depends which layer you mean. One codebase across vendors: compiler layer, standards already exist (SPIR-V / MLIR), nothing to do with device identity. Who owns THIS used card, what it ran, whether it is pledged: device-identity layer — no statutory issuer exists there; CVIN is the open provenance layer for exactly that.
02
Why GPUs will never have an SAE-style statutory VIN issuer
- Three layers, no single legal subject：Chip (NVIDIA/AMD/Intel serial systems), board (AIC partners stamp their own SNs), full machine (server OEMs stamp yet another) — a "device" has three owners of numbering; none can issue for the other two layers.
- No statutory stamping duty：The automotive VIN derives its force from law — mandatory stamping plus title registration. GPUs have no equivalent "road legality" gate, hence no equivalent mandatory registration.
- OEM serials don't interoperate：Every OEM has internal serials, but they neither cross-recognize nor expose public lookups — you can confirm a number exists, never what the device has been through.
Hard boundary: CVIN does not issue — and has no authority to issue — "global unified numbers". Issuing numbers is not the business; provenance is. OEM serials already exist; what is missing is a public, append-only, cross-platform history layer. CVIN's value is hashing existing serials onto that public chain, not inventing a new numbering scheme.
03
Automotive VIN vs GPU: the gap in one table
| Automotive VIN | GPU today | |
|---|---|---|
| Issuer | SAE standard + statutory stamping | No statutory issuer; OEMs each issue their own, non-interoperable |
| Uniqueness | Mandatory 17-char format, globally unique | OEM serials near-unique, formats mutually incompatible |
| How to check history | Carfax-style reports sit on statutory registration | No mandatory registry → only voluntary open provenance (CVIN, free) |
| Use in a deal | Check the VIN before buying | Check the serial's provenance before buying: mining history, operators, liens |