DPP: Steel & Textile
SCAN
RESOLVE
SEARCH DID.JSON
Product DID JSON
https://did.4therecord.io/products/steel00001/did.json
1.Cryptographical Controller (Company DID JSON)
"controller": "did:web:did.4therecord.io"
Resolve and opens https://did.4therecord.io/.well-known/did.json
also see Legal Entity Credential below
2.Search Redirect
contains of "serviceEndpoint": "https://4therecord.io/products/steel00001"
Resolver redirects to serviceEndpoint
DISPLAY DPP
Product DPP HTML
https://www.4therecord.io/products/steel00001
GET CONTET FOR DPP
Product DPP JSON
https://did.4therecord.io/products/steel00001/dpp.json
Product DID JSON
https://did.4therecord.io/products/textile00001/did.json
1.Cryptographical Controller (Company DID JSON)
"controller": "did:web:did.4therecord.io"
Resolve and opens https://did.4therecord.io/.well-known/did.json
also see Legal Entity Credential below
2.Search Redirect
contains of "serviceEndpoint": "https://4therecord.io/products/textile00001"
Resolver redirects to serviceEndpoint
Product DPP HTML
https://www.4therecord.io/products/textile00001
Product DPP JSON
https://did.4therecord.io/products/textile00001/dpp.json
Legal Entity Credential
The main did.json in .well-known:
https://did.4therecord.io/.well-known/did.json
which will be resolved and forwarded to
The content is retrieved from the associated json-file (verifiable credential):
Examples: Steel and Textile DPP
Our Digital Product Passport is built upon the global standards set by the W3C (World Wide Web Consortium) for Decentralized Identifiers (DIDs). Instead of hiding information in a centralized, alterable database, every single one of our products has its own unique, cryptographically secured identity. Below you will find the exact technical workflow that happens in milliseconds when scanning the QR code on a product.
#1 Scanning the QR Code (Entry Point)
Every product is equipped with a unique QR code. Instead of containing a standard website URL, it holds a standardized link directed to a universal DID resolver.
Example QR Codes with resolved Links on the Physical Product:
#2 The Universal Resolver (Neutral Intermediary)
The link on the physical product points directly to a Universal Resolver gateway (did.re), which utilizes the robust GoDiddy API. Instead of acting as a traditional web server that simply hosts data, a resolver acts like a decentralized DNS or phone book. It translates a raw cryptographic identity string into an actual server location.
Let’s break down exactly what happens when this URL is requested:
The Gatekeeper https://did.re
This is the proxy frontend for the GoDiddy API resolver. It accepts standard web requests from mobile browsers or auditing applications and translates them into decentralized infrastructure lookups.The Method did:web:
This indicates the specific W3C standard used to resolve the identity. The did:web method tells the resolver that the identity is bound to a trusted web domain, using standard web security (HTTPS) to discover the underlying cryptographic passport.The Domain & Path Separators did.4therecord.io:products:steel00001
In the world of Decentralized Identifiers, standard URL slashes (/) cannot be used inside the core identifier string. Instead, the W3C standard uses colons (:) to separate the domain from the internal folder paths. When the GoDiddy API sees did.4therecord.io:products:steel00001, it automatically converts those colons back into a secure web path layout behind the scenes to fetch the file: https://did.4therecord.io/products/steel00001/did.jsonThe Target Parameter ?service=dpp
A single decentralized identity can have multiple associated endpoints (for example: one endpoint for an auditing report, one for a supply chain log, and one for a customer dashboard). By passing the query parameter ?service=dpp, we explicitly instruct the GoDiddy resolver to look into the product's identity file, select the service entry with the ID #dpp, and execute a seamless HTTP redirect directly to that specific URL.
#3 The Decentralized Product Identity (did.json)
The resolver automatically queries our secure server to read the product's core identity document - the did.json. This file is immutable and serves as the product's digital ID card. It contains two crucial pieces of information:
The Controller: Who manufactured the product? (A cryptographic reference to our Company DID).
The ServiceEndpoint: Where is the visual interface hosted for the end-user?
Live Raw File on the Web: https://did.4therecord.io/products/steel00001/did.json
{
"@context": [
"https://www.w3.org/ns/did/v1"
],
"id": "did:web:did.4therecord.io:products:steel00001",
"controller": "did:web:did.4therecord.io",
"service": [
{
"id": "did:web:did.4therecord.io:products:steel00001#dpp",
"type": "DigitalProductPassportWeb",
"serviceEndpoint": "https://4therecord.io/products/steel00001"
}
]
}
#4 Automatic Redirect to a readable Page (Visual Interface)
As soon as the resolver extracts the serviceEndpoint from the JSON file, it instantly triggers an HTTP redirect. The user is seamlessly forwarded to our secure product page:
Target Interface URL: https://4therecord.io/products/steel00001
Here, the customer can view a beautifully designed frontend featuring all verified product and sustainability data.
The content is retrieved from the associated JSON. To guarantee ultimate technical flexibility and data integrity, we strictly separate identity from content data. On the Squarespace page, we provide developers, auditors, and customs authorities with the option to access the raw, machine-readable verification payload (the Verifiable Credential) directly.
This data is stored as a separate dpp.json file on our server. It can be easily updated in the future (e.g., following new carbon footprint recalculations) without breaking the product's core identity link.
Live Payload File on the Web: https://did.4therecord.io/products/steel00001/dpp.json
#5 Transparency via Decoupled Data (dpp.json)
{
"@context": [
"https://www.w3.org/2018/credentials/v1"
],
"type": ["VerifiableCredential", "DigitalProductPassport"],
"id": "did:web:did.4therecord.io:products:steel00001",
"issuer": "did:web:did.4therecord.io",
"credentialSubject": {
"productDescription": {
"productName": "Steel Beam HEB 300",
"description": "High-strength structural steel beam optimized for modern, sustainable construction frameworks.",
"batchNumber": "BATCH-STL-2026-998"
},
"sustainability": {
"carbonFootprintGWP": "450 kg CO2e / Ton",
"humanRights": "Fully compliant with international labour rights and union standards.",
"childLabour": "Verified zero-risk supply chain for raw materials."
},
"manufacturer": {
"companyName": "4therecord.io",
"location": "Duisburg, Germany"
}
}
}
Because the dpp.json contains the field "issuer": "did:web:did.4therecord.io", any modern auditing software can independently verify that this product legitimately originates from 4TheRecord GmbH. Our Company DID, in turn, hosts our official corporate credential, mapping out our verifiable location and trade registry details.
Verify Corporate Credential via Resolver: https://did.re/did:web:did.4therecord.io?service=company-credential