DID + VC for packs, modules & systems

Batteries & BESS/HESS: make every pack verifiable.

Bind each cell/module/pack to a cryptographically signed identity, issue Device & Ownership VCs on the line, and let integrators, operators, and regulators check status with one scan.

Create account & start issuing How it works

Keep serials and safety labels; add a VC layer for authenticity, provisioning, and lifecycle status.

Pack credential (excerpt)
{
  "type": ["BatteryPackCredential"],
  "issuer": "did:web:veritrust.vc",
  "credentialSubject": {
    "manufacturerDid": "did:veritrust:manufacturer:cn-batt-001",
    "model": "LFP-280Ah-Pack",
    "serial": "PK-2025-000123",
    "capacity_Wh": 14336,
    "chemistry": "LFP",
    "bom_hash": "sha256:..."
  }
}
Serials remain; VC adds signature, ownership, firmware & warranty status.

Problems we solve

  • Counterfeit or grade-swapped cells in packs
  • No proof that a pack/module came from a certified line
  • Difficult warranty & recall management across integrators
  • Regulators and insurers lack machine-checkable provenance
Who benefits

Cell & pack manufacturers — prove origin and spec conformance.

BESS/HESS integrators — verify incoming modules and track warranty.

Operators & EPCs — audit trail for safety and insurance.

Regulators & customs — instant verification at borders and inspections.

How it works for batteries & systems

1
Secure key provisioning

Embed an Ed25519 key in BMS (SE/TPM or encrypted flash). Stamp serial + QR/NFC plate.

pubkey: ed25519:...  serial: PK-2025-000123
2
Issue Device & BOM VCs

At end-of-line, issue Device VC (model/specs), BOM hash, and optional Ownership VC for integrator.

POST /manufacturing/device/issue
3
Verify & manage lifecycle

Scan at intake, commissioning, service, resale. Status feed covers warranty, recalls, and firmware.

GET /verify/device/{serial or QR}

Embedding in packs & IoT devices

Hardware options
  • Secure Element (ATECC608, etc.) or TPM on BMS MCU
  • Encrypted key vault in flash + anti-rollback bootloader
  • QR/NFC plates with signed short token
Software bindings
  • DID binding: did:veritrust:device:{serial}
  • BOM/firmware hashes in VC claims
  • mTLS or signed challenge for field diagnostics

Short use scenarios

Inbound QA

Integrator scans batches; mixed/gray-market modules fail verification.

Warranty & recalls

Ownership VC tracks handoffs; affected serials turn red in the registry.

Compliance checks

Customs/insurers verify certified models and test reports via device VC.

Remote service

Field tool runs a signed challenge; only genuine devices respond correctly.

Create account & start issuing

  1. Register manufacturer entity and obtain a Veritrust DID.
  2. Provision keys on the line (BMS/SE/TPM) and configure QR/NFC plates.
  3. Issue Device, BOM and optional Ownership VCs at end-of-line.
  4. Expose verification at intake, commissioning and service workflows.
Create account

Benefits

  • Authenticity & provenance for packs and modules
  • Reduced safety risk and faster root-cause analysis
  • Smoother insurance and regulatory approvals