intelligence_src_7832fd302ddcf52920
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Jun 30, 2026 12:00 UTC
- Retrieved
- Oct 14, 2026 11:44 UTC
Verifiable Digital Credential Presentment
This blog post is #4 in our series on Verifiable Digital Credentials (VDCs). Our other posts can be found via Post #1, Post #2, and Post #3. In earlier posts, we discussed how verifiable digital credentials (VDCs) are issued and compared the underlying credential formats (ISO/IEC “mdoc” vs. W3C Verifiable Credentials). In this post, we turn to the other side of the story: presentation; that is, how a holder shows their VDC to a verifier at runtime in both in-person and online contexts. We’ll again explore the mobile driver’s license (mDL) use case, consider the differences between ISO/IEC
Reference details
- Source category
- research-report
- First reported
- Jun 30, 2026 12:00 UTC
- Last reported
- Jun 30, 2026 12:00 UTC
- Catalog updated
- Oct 14, 2026 11:44 UTC
- Record ID
bd391b2da65e19ebd3e46fe2b8babe3c7ea4a041ce8a4a74ad087eaea57502d0
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Review source update dates and status
- intelligence_src_7832fd302ddcf52920Recent successful batchLast successful batch: Last attempt:
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.