Verifiable Credential Dynamic Claims via Remote Value Pointers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing verifiable credential systems are inefficient in managing and tracking the usage of credentials, especially when multiple devices are involved, as they lack mechanisms for portability and dynamic claims that change over time without reissuing the credential.

Innovation Solution

Implementing verifiable credentials with dynamic claims where the value is a location or pointer to a network location that stores a remote value, allowing the relying party to access and update the value without changing the credential, and using decentralized identifiers for enhanced portability and management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If verifiable credentials store static values directly, then verification is simple and direct, but the credential cannot adapt to changing information without reissuance

Engineering Contradiction:
Improvecredential adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The credential system is segmented into two parts: the credential itself (containing the pointer) and the remote value storage (containing the actual dynamic data). This allows the credential to remain static while the referenced data can change, resolving the contradiction between adaptability and simplicity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A pointer or reference acts as an intermediary between the credential and the actual value. The credential contains this pointer that references remote storage, allowing indirect access to dynamic values without changing the credential structure itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If credentials are reissued to update changing information, then data accuracy is maintained, but issuance frequency increases and efficiency decreases

Engineering Contradiction:
Improvedata accuracyVSAvoidcredential issuance efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The credential is issued with a pointer to remote storage in advance. This preliminary setup allows future updates to be made by simply changing the remote data, not by reissuing the credential, thus maintaining accuracy while improving efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of copying the entire credential with updated values, the system copies only the relevant data to remote storage and updates that separately. The original credential remains valid but now points to updated data.

Inventive Principle:
Principle #26Copying

3Ease of operation

If credentials are designed for single-device use, then security and control are simplified, but portability across multiple devices is limited

Engineering Contradiction:
Improvemulti-device portabilityVSAvoidcredential control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The credential is designed to be universally usable across multiple devices by containing a pointer to remotely stored data rather than embedding the actual data. This allows any device with access to the remote storage to verify the credential, improving portability while maintaining control through the centralized pointer.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12368707B2Verifiable credential with dynamic claim
Publication Date: 2025.07.22 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12368707B2 patent drawing
  • US12368707B2 patent drawing
  • US12368707B2 patent drawing

AI summary

Permitting a claims holder to get a limited verifiable credential leveraging off of a previously-issued verifiable credential. This is done by having the limited verifiable credential include only a selected subset of the verifiable claims present within the previously-issued verifiable credential. The limited verifiable credential may then be exposed to a relying entity computing system so that the relying entity computing system can verify any of the selected subset of verifiable claims, but not verifiable claims that are outside of the selected subset of verifiable claims.