Blockchain Integrity via Periodic Digital Certificate Signing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain systems face challenges in efficiently and reliably determining which chain of hash-linked blocks constitutes the canonical chain, leading to conflicts in data block validation.
Innovation Solution
The use of digital certificates for regularly signing blocks in a specific chain, where validators publish public keys, generate and publish signatures, and include hashes and further signatures in blocks to ensure chain integrity, allowing participants to validate sequences of blocks and reject invalid sequences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If digital certificates are used to sign blocks regularly, then chain integrity is improved, but device complexity increases
Solution Approach 1:
A digital certificate authority acts as an intermediary to issue and manage digital certificates for blockchain validators. The certificate includes a public key and is signed by the authority, providing a trusted mechanism for identity verification without requiring complex peer-to-peer authentication protocols. This intermediary system simplifies the overall complexity while enhancing reliability.
Solution Approach 2:
Digital certificates are issued and public keys are published on the blockchain in advance before validation conflicts occur. This preliminary establishment of trusted identities allows validators to be automatically recognized and their blocks validated without real-time complexity, resolving the contradiction by preparing the authentication mechanism beforehand.
2Reliability
If digital signatures are generated for every predetermined number of blocks, then validation reliability is improved, but computing effort increases
Solution Approach 1:
Instead of requiring digital signatures for every single block, the system implements periodic signing where a validator generates a digital signature every predetermined number of blocks (e.g., every 10 or 100 blocks). This periodic action maintains validation reliability through regular authentication while significantly reducing the computing effort and energy consumption compared to continuous signing.
Solution Approach 2:
The system uses partial action by signing only a hash of selected blocks rather than every block, and only by designated validators rather than all validators. This partial approach provides sufficient validation reliability to prevent chain conflicts while avoiding the excessive computing effort of universal continuous signing.
3Ease of operation
If public keys are published on the blockchain, then identity management is improved, but data storage requirements increase
Solution Approach 1:
The system extracts only the essential public key from the full digital certificate and publishes it on the blockchain, while the complete certificate details are stored off-chain or in a separate registry. This extraction approach simplifies identity management by making public keys easily accessible for validation while minimizing the data storage burden on the blockchain.
Solution Approach 2:
Instead of storing complete digital certificates on every node, the system uses copies of just the public key portion on the blockchain, with full certificate verification done through lighter-weight cryptographic checks. This copying strategy enables efficient identity management with minimal storage requirements.
Data Source
AI summary
A system and method for ensuring digital integrity of a blockchain is presented. The blockchain is initiated with one or more digital certificates presented in one of an initial set of blocks of the blockchain. One or more of the digital certificates may subsequently be used to sign a hash of a sequence of blocks in the blockchain at regular or semi-regular intervals. If a sequence of consecutive blocks is longer than a predetermined number and does not contain a signature from one or more of the digital certificates of a hash or one or more of the blocks in the sequence, the sequence may be considered not to comprise a part of the blockchain. In other embodiments side blocks may be signed and added to the blockchain.