Genesis Block Verification Using Trusted Certificates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In permissioned blockchain networks, the generation of a genesis block lacks secure verification mechanisms, leading to potential spoofing or falsification of certificates and identities, which can compromise the integrity of the blockchain network.
Innovation Solution
The implementation of a certification mechanism using TLS certificates from a trusted third party, combined with self-signed certificates, ensures the authenticity of participating entities by verifying the ownership of domain names and public keys, and utilizes a distributed version control system to agree on the genesis block contents among entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a certification mechanism using TLS certificates and self-signed certificates is implemented, then the authenticity and security of participating entities is improved, but the device complexity and verification process become more complex
Solution Approach 1:
The patent applies preliminary action by having entities obtain TLS certificates from a trusted third party (certificate authority) before participating in the blockchain network. The certificate authority verifies entity identities in advance and issues certificates that are then stored in a distributed repository. This pre-verification eliminates the need for complex runtime identity verification, as the authenticity is established beforehand through the trusted certificate authority.
Solution Approach 2:
The patent uses a trusted third party (certificate authority) as an intermediary to issue and verify TLS certificates. This intermediary simplifies the verification process by providing a centralized trust anchor that all entities can rely on. Instead of entities directly verifying each other's identities through complex cryptographic protocols, they all trust the certificate authority's verification, reducing the overall system complexity while maintaining high security.
2Reliability
If distributed version control system is used to agree on genesis block contents, then the security and integrity of genesis block is improved, but the time required for consensus and coordination increases
Solution Approach 1:
The patent segments the genesis block creation process into independent components: entity certificates, domain name verifications, and public key validations. Each entity contributes their own segmented information (TLS certificate, self-signed certificate, domain proof) to the distributed repository. This segmentation allows parallel verification of multiple entities simultaneously, reducing the overall consensus time while maintaining the integrity of the complete genesis block through distributed agreement.
3Object-affected harmful factors
If TLS certificates from trusted third party are used, then the prevention of spoofing is improved, but the ease of operation and setup becomes more difficult
Solution Approach 1:
The patent implements self-service by enabling entities to automatically obtain TLS certificates from a trusted third party and self-sign their own certificates using their private keys. Each entity independently manages their own certificate lifecycle - obtaining the TLS certificate, generating the self-signed certificate, and storing it in the distributed repository. This automated self-service approach reduces manual intervention requirements while maintaining strong spoofing prevention through cryptographic verification.
Data Source
AI summary
In some examples, a first computing device of a first entity receives a first digital certificate from a certificate authority computing device and generates a first self-signed certificate associated with the first digital certificate. The first computing device may store the first self-signed certificate associated with the first digital certificate in a repository associated with a repository computing device. Further, the first computing device may receive a notification indicating an update by a computing device of a second entity to contents of the repository. The first computing device receives a copy of the contents of the repository including at least a second digital certificate and a second self-signed certificate associated with the second entity. The first computing device may verify the contents of the repository and generate a genesis block of a blockchain based on a result of the verifying.