Chained-Hash Logs for Trustworthy Timestamps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Decentralized systems, such as peer-to-peer networks and decentralized version-control systems, face challenges in maintaining trustworthy timestamps and certifiable clocks due to inaccurate device clocks, disconnection from networks, and the inability to rely on centralized digital notary services.

Innovation Solution

A method involving the use of chained-hash logs where devices entangle their time logs by adding time-stamped synchronization entries, creating a 'web of trust' that allows for the synchronization of log entries and the establishment of causal ordering, even when devices are disconnected, by tracing back to trustworthy sources like GPS or NTP tier-1 time servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If decentralized systems use separate device clocks and logs, then device autonomy and offline operation are improved, but timestamp reliability and clock accuracy deteriorate

Engineering Contradiction:
Improvedevice autonomyVSAvoidtimestamp reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the centralized timestamp authority into distributed peer nodes, where each node maintains its own log and clock independently. This segmentation allows devices to operate autonomously offline while still contributing to the overall trust framework through cryptographic hash linking of their local logs.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Cryptographic hash functions serve as intermediaries between decentralized device clocks and trust. Instead of direct clock synchronization, devices use hash-linked logs as mediators that bind timestamps to verifiable evidence, allowing timestamp reliability to be established without centralized mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If devices operate disconnected from networks, then offline capability and resilience are improved, but ability to verify timestamp accuracy deteriorates

Engineering Contradiction:
Improveoffline capabilityVSAvoidtimestamp accuracy verification
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

Devices perform preliminary actions by maintaining and updating their local logs with cryptographic hash links even when offline. This preliminary logging creates a verifiable chain of custody for timestamps that can be validated later when connectivity is restored, without requiring real-time network verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback through hash-linked logs that provide verifiable evidence of timestamp accuracy. When devices reconnect, they can verify their offline timestamps against the hash chain, receiving feedback on their clock accuracy without requiring continuous network connection.

Inventive Principle:
Principle #23Feedback

3Reliability

If centralized digital notary services are used, then timestamp trustworthiness is improved, but system centralization and single points of failure worsen

Engineering Contradiction:
Improvetimestamp trustworthinessVSAvoidsystem centralization
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The centralized notary function is segmented into distributed peer nodes that each maintain hash-linked logs. Trustworthiness is achieved through the cryptographic chain rather than centralized authority, eliminating single points of failure while maintaining timestamp reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each device serves its own timestamp verification needs through its local hash-linked log, rather than relying on centralized notary services. The system is self-verified through cryptographic proof, allowing devices to autonomously validate their own timestamps against the hash chain.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If devices have separate independent logs, then device independence is improved, but ability to establish causal ordering and synchronize deteriorates

Engineering Contradiction:
Improvedevice independenceVSAvoidcausal ordering information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

While maintaining separate independent logs, devices merge their logs through cryptographic hash linking. Each log incorporates hashes of other logs, creating a combined web of trust that preserves device independence while establishing causal ordering through the hash relationships between independent log sources.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8412946B2Trustworthy timestamps and certifiable clocks using logs linked by cryptographic hashes
Publication Date: 2013.04.02 RICOH CO LTD
  • US8412946B2 patent drawing
  • US8412946B2 patent drawing
  • US8412946B2 patent drawing

AI summary

A method and apparatus for creating and/or using trustworthy timestamps and certifiable clocks using logs linked by cryptographic hashes. In one embodiment, the method comprises maintaining a first, chained-hash log; associating a first clock with the chained-hash log, and entangling the first log; with a second by adding a time-stamped synchronization entry to the chained-hash log, where the synchronization entry has a second time indication associated with the second log and a hash of one or more entries in the first log.