DIMO: public Sybil-risk read

As of 2026-08-20

Public source: https://identity-api.dimo.zone/query · no auth, no internal data

Of 158,553 DIMO vehicle identities, 40,622 (25.6%) are backed by physical hardware; 31,452 (19.8%) connect via software/synthetic devices, and 86,479 (54.5%) show no connected device on the public registry.

This is an independent read of DIMO's own public data by the GETKINETIK bureau. We publish what the public endpoint returns — covering duplicate GPS coordinates and stacked devices — so anyone can reproduce it. We hold no token in any network we read and take no equity in graded networks.

The numbers

Metric	Value
Units observed (with coordinates)	158,553
Aftermarket Devices	40,622
Synthetic Devices	31,452
Backed Devices	72,074
Unbacked Vehicles	86,479
Hardware Pct	0.256
Synthetic Pct	0.198
Backed Pct	0.455
Unbacked Pct	0.545

What this means — and what it doesn't

Worth a look

Multiple devices reporting the exact same GPS coordinate. At small counts this is normal — dense buildings, shared rooftops, and H3-hex snapping all produce shared coordinates legitimately. Large single-coordinate stacks are the documented stacking pattern that warrants a registry cross-check.

Not an accusation

This is not proof of fraud. Honest dense deployments can share a coordinate, and the bureau makes no accusation. The list is a review queue, not a verdict.

How to confirm it

Sanity-check (not a test request): the public Identity API shows more vehicle identities than connected devices. Ask whether the unbacked identities are expected (pre-onboarding, churn, deregistered) or whether they count as active for rewards. verify-device only becomes relevant if confirmation establishes real per-device activity to ground-truth.

For an authoritative per-device grade — hardware-rooted signature, chain age, tamper flags — a network or operator can POST a Proof of Origin to the verify-device API.

Go deeper

Full methodology & row-level table → Verify a device → Request the full table →