Decentralized Remote Attestation via Oracle Challenge-Response
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing decentralized peer-to-peer networks face challenges in efficiently and scalably verifying the authenticity and integrity of peers without relying on centralized systems, smart contracts, or device manufacturers, leading to inefficiencies and scalability issues.
Innovation Solution
A decentralized remote attestation method using an 'oracle' device with a secure enclave and random number generator, combined with a peer's asymmetric key pair and a shared ledger, allows peers to verify authenticity through a challenge-response mechanism without requiring blockchain synchronization or device manufacturer involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional pairwise remote attestation is implemented in a decentralized peer-to-peer network, then security verification is achieved, but computing resources and time consumption increase significantly
Solution Approach 1:
The patent combines multiple individual attestation challenges into a single aggregated challenge that can be verified by multiple peers simultaneously. Instead of each peer independently verifying every other peer through separate challenge-response protocols, the system merges these verification tasks into a unified process where one attestation can serve multiple verifiers, dramatically reducing redundant computing operations.
Solution Approach 2:
The attestation mechanism is designed to be universally applicable across multiple peers. A single attestation proof generated by one peer can be verified by any number of other peers in the network without requiring separate attestation processes. This multi-functional design allows the same attestation infrastructure to serve numerous verification purposes simultaneously.
2Productivity
If centralized verification systems are used to manage peer attestation, then verification efficiency improves, but single points of failure and security risks increase
Solution Approach 1:
The verification system is segmented into distributed peer nodes rather than centralized authorities. Each peer in the network can independently generate and verify attestation challenges, eliminating the need for a central verification server. This segmentation distributes the verification workload and removes single points of failure while maintaining efficient verification through the aggregated challenge mechanism.
Solution Approach 2:
Peers in the network perform self-verification through the attestation mechanism. Each peer can autonomously generate attestation proofs and verify other peers without requiring external centralized authority. The system enables peers to service their own verification needs while contributing to the overall network security, eliminating dependence on centralized verification infrastructure.
3Measurement precision
If device manufacturers are involved in the attestation process, then device authenticity is improved, but device complexity and operational dependency increase
Solution Approach 1:
The attestation verification function is extracted from device manufacturers and embedded directly into the peer nodes of the decentralized network. Instead of relying on manufacturer-provided attestation services, each peer independently performs verification using the cryptographic challenge-response mechanism. This extraction eliminates the need for ongoing manufacturer involvement while maintaining strong authenticity verification through cryptographic proofs.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
A decentralized remote attestation method for attesting the authenticity of an Attester peer (20) within a network of peers sharing a ledger (50) involves a Verifier peer (30) and an Oracle device (40) having a secure enclave and a random number generator. The Attester (30) publishes a public key to the ledger (50). The Oracle (40) generates a unique random number and an encryption key, then encrypts the random number and sends it via a secure channel to the Verifier. The Oracle (40) publishes the encrypted random number to the ledger (50). The Verifier (30) generates a challenge using the random number and the public key and publishes the challenge to the ledger. The Attester (20) solves the challenge using the private key and publishes a proof to the ledger (50). After publishing the proof to the ledger (50), the Oracle (40) publishes the encryption key.