Verified IoT Production • DID + VC

Make IoT devices verifiable — from factory to field.

Embed cryptographic identity (DID) at production, issue Verifiable Credentials (VCs), and let any partner in Europe or the US verify authenticity, ownership, and firmware with one scan.

Join the Verified Manufacturing Partnership How it works

Keep your existing production lines — add a tiny secure key and a QR badge.

At a glance
  • Factory embeds device key → device gets a DID
  • Veritrust issues Device, Ownership, and Firmware VCs
  • QR/URL verification pages show green/yellow/red status
veritrust://dev/did:veritrust:device:abc123#JWS
https://verify.veritrust.vc/dev/did:veritrust:device:abc123
Dual offline/online verification payloads for field checks and audits.

Why IoT needs to be verified

Global trade moves fast. Without cryptographic identity and verifiable metadata, smart meters, BESS/HESS, and connected devices are hard to trust, onboard, and control across borders. Counterfeits, cloned serials, and unverifiable PDFs slow deployments and increase risk.

  • Prove device authenticity at delivery
  • Bind device → owner/installer/aggregator
  • Attest firmware & compliance
  • Sign telemetry; prevent spoofing
  • Revoke/transfer cleanly on resale
  • Human-friendly QR checks

How Veritrust works for manufacturing

1
Embed DID at production

Install a secure element (or encrypted storage). Generate device keypair → publish DID.

2
Issue VCs

Device Identity VC, Ownership VC (OEM → buyer/aggregator), Firmware VC (version/hash, compliance).

3
Verify & control

Partners scan QR or call API. Check signature, status, and perform challenge–response for live control.

Short use scenarios

BESS / HESS

Battery ships with DID. Installer scans QR; Ownership VC issued to buyer; aggregator verifies signed telemetry.

Smart meters

Utility validates Device VC at warehouse; field tech proves device identity via nonce signature before activation.

Smart devices

Home router/IoT hub presents VC at first boot; app shows “Verified by Veritrust” with firmware and warranty status.

Smart cars

Vehicle modules carry DIDs; service center checks module VC and firmware VC before updates or recalls.

Factory embed: minimal recipe

  1. Mount secure element (I²C/SPI) or provision encrypted flash.
  2. Generate keypair on-device; export public key only.
  3. Register DID with Veritrust; print chassis QR.
  4. Request Device VC (+ Firmware VC) via API.
  5. Ship device with QR + PDF CoC linking to verify page.
Issuance API (example)
POST /manufacturing/device/issue
{
  "pubkey":"ed25519:...",
  "serial":"SN-2025-000123",
  "model":"BESS-4680-13kWh",
  "firmware_hash":"sha256:..."
}

Returns Device VC (JWT), Firmware VC, and verification URLs/QR payloads.

Ready to ship verifiable devices?

Create an account and join the Verified Manufacturing Partnership.

Create account
We provide EU/US verification endpoints and Chinese-language onboarding.