Embedded Device Authentication With Derivative Ledger Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cryptocurrencies face issues with governance flexibility, scalability, high energy consumption, and economic inefficiencies in mining, along with challenges in securely authenticating embedded devices.
Innovation Solution
Embedded devices are cryptographically identified and authenticated through interaction with a distributed ledger using a manufacturer root key and a globally unique identifier, generating a derivative key for secure transaction signing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proof-of-work mining is used to secure the distributed ledger, then security and decentralization are improved, but energy consumption and computational requirements increase significantly
Solution Approach 1:
The patent changes the security parameter from proof-of-work computational difficulty to proof-of-ownership verification. Instead of requiring miners to solve complex mathematical puzzles that consume vast energy, the system verifies ownership of cryptographic keys and device identities, dramatically reducing energy consumption while maintaining security through cryptographic proof rather than computational brute force.
Solution Approach 2:
The patent replaces the mechanical computational system of proof-of-work (physical mining hardware performing repeated calculations) with a cryptographic verification system. The security mechanism shifts from mechanical computation to mathematical proof of ownership, where devices prove their identity through digital signatures and cryptographic challenges rather than through energy-intensive mining operations.
2Speed
If embedded devices are authenticated using traditional centralized methods, then authentication speed is improved, but security against impersonation and tampering deteriorates
Solution Approach 1:
The patent introduces a distributed ledger as an intermediary that enables direct peer-to-peer authentication between embedded devices. The ledger stores verified device identities and ownership proofs, allowing devices to authenticate each other directly without centralized intermediaries. This maintains fast authentication speeds while improving security through decentralized verification and cryptographic proof of ownership.
Solution Approach 2:
The patent performs preliminary authentication and identity verification during device registration before the device is deployed. Ownership proofs and cryptographic identities are established in advance and stored on the distributed ledger, enabling rapid subsequent authentication operations without requiring real-time centralized verification, thus maintaining speed while enhancing security.
3Stability of the object's composition
If cryptocurrency systems are designed with fixed governance models at creation, then system stability is improved, but adaptability to new laws and regulations deteriorates
Solution Approach 1:
The patent implements dynamic governance mechanisms that allow the distributed ledger system to adapt its rules and parameters over time. Governance decisions can be made through on-chain voting and consensus mechanisms, enabling the system to modify its own governance structure in response to new laws, regulations, or user needs while maintaining system stability through decentralized consensus rather than centralized control.
Data Source
AI summary
Some embodiments of the present invention provide a method of cryptographically identifying and authenticating embedded devices through interaction with a distributed ledger. The device begins with a manufacturer root key and a globally unique identifier. It registers by signing a registration transaction that includes its identifier using its private root key with a digital signature algorithm and sending the resultant transaction to the distributed ledger. The ledger generates a registration root key and responds by sending this second root key back to the device. The device then uses the manufacturer root key and the registration root key to generate a child key that it uses to sign its response to the challenge proving that it possesses both the manufacturer key and the registration key. Thereafter, the device can non-interactively identify and authenticate itself to the distributed ledger by signing transactions with the derivative key.
