Workflows

DPP Minting API

The central, atomic gateway orchestrating decentralized identity generation, IPFS metadata persistence, and smart contract anchoring in a single, verified transaction.

Canonical Truth Confirmed

POST /v1/dpp/mint is the active canonical endpoint powering the V-Ledger Dashboard. Unlike legacy factory separation flows, this modern routine captures metadata and hardware dynamic proofs simultaneously to execute an immutable mint.

POST/v1/dpp/mint

Environment: test

API Request Payload

{
  "name": "Classic Chronograph V3",
  "description": "Platinum edition luxury...",
  "image": "ipfs://QmXyz123AbC456...",
  "chipUid": "04A1B2C3D4E5F6",
  "nfcData": "c=42&sv=1A2B3C4D5E...", // 🔑 Dynamic Proof
  "custom_dpp_data": {
    "gtin": "4012345678901",
    "manufacturer_name": "V-Ledger GmbH",
    "conformity_url": "https://brand.com/docs/cert.pdf", // Required
    "svhc_exists": false
  }
}

Atomic Response (201 CREATED)

{
  "success": true,
  "message": "DPP successfully created",
  "blockchain": {
    "tokenId": "1048293002",
    "transactionHash": "0x84e9a2c3...",
    "ipfsUrl": "ipfs://QmP8y7z..."
  },
  "data": {
    "dbId": 142,
    "status": "ACTIVE"
  }
}

The WebSocket Signal Bridge

How does the desktop application acquire the hardware signature? During interactive UI flows, the Dashboard opens a peer-to-peer bridge. The Toolbox App scans the tag physically and transmits the encrypted nfcData signature payload transparently to the desktop. The API call then submits this single combined package atomically to the ledger.

ESPR Compliance Failure

Modern EU-mandates enforce valid legal linkage. Omitting the mandatory conformity_url immediately locks the validation gate.

400: "ESPR Compliance Fehler: declarationOfConformity ist zwingend erforderlich."

Immutability Constraint

The hardware identity is logically unique. Once a chip possesses a minted token balance, re-submitting prevents accidental overwrites.

409: "Conflict: Chip already registered."