Blockchain Public Key Revocation Using Certification Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing public key infrastructure (PKI) systems face delays and inefficiencies in revoking compromised digital certificates due to the reliance on certificate revocation lists, which can take hours to update, compromising the security of key authentication.
Innovation Solution
Utilizing a blockchain network to manage public key infrastructure by recording digital certificates and revocation transactions, enabling instantaneous verification and revocation through unspent transaction outputs (UTXO) and certification transaction identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If certificate revocation lists are used to manage compromised digital certificates, then digital certificates can be revoked, but the revocation information is not immediately available to entities that need to validate public keys, causing security delays
Solution Approach 1:
The patent replaces the traditional mechanical system of certificate revocation lists with a blockchain-based distributed ledger system. The blockchain network provides immutable, real-time recording of certificate status changes, eliminating the delay inherent in centralized CRL updates and distribution. Smart contracts automatically execute revocation logic, providing immediate propagation of revocation information across the network.
Solution Approach 2:
The patent introduces a blockchain network as an intermediary between the certificate authority and validating entities. This intermediary provides a decentralized, trustless mechanism for publishing and verifying certificate status, where the blockchain's consensus mechanism ensures that revocation information is immediately available to all network participants without relying on periodic CRL publications.
2Ease of operation
If certification authorities maintain centralized revocation lists, then digital certificates can be managed, but the system complexity and update propagation overhead increase
Solution Approach 1:
The patent makes the blockchain network serve multiple functions: it acts as the certificate authority, the revocation list, the distribution network, and the verification mechanism simultaneously. This multi-functionality eliminates the need for separate CRL maintenance infrastructure, reducing overall system complexity while maintaining full certificate management capabilities.
Solution Approach 2:
The patent implements self-service through smart contracts that automatically handle certificate issuance, revocation, and validation logic. The blockchain network itself maintains the state of all certificates through its immutable ledger, eliminating the need for centralized authorities to manually maintain and distribute revocation lists. The system serves itself through automated consensus and smart contract execution.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods and devices for enabling a third party to verify that a first public key associated with a first entity is valid and has not been revoked. The first public key is recorded on a blockchain in a certification transaction having a first output to an address based on a second public key and a second output with an information field containing the first public key. The third party that receives the first public key and an identifier for the certification transaction may obtain a copy of the certification transaction, determine that the first output is unspent and determine that the information field contains the first public key, and, based on those determinations, determine that the first public key is valid.