Smart Contract Ownership Verification via Digital Certificate Embedding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain technologies face challenges in verifying and authenticating the ownership of smart contracts, particularly on public blockchains, leading to issues with fraud and counterfeit digital assets.
Innovation Solution
A computer-implemented method for authenticating smart contracts involves using an existing key pair from a website digital certificate, signing a message with the private key, and storing the signature, message, public key, and website address in a smart contract, which is then deployed on a blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If smart contracts are deployed on public blockchains with open-source code, then accessibility and decentralization are improved, but the ability to verify ownership and prevent fraud deteriorates
Solution Approach 1:
The patent introduces a certificate authority (CA) as an intermediary that issues digital certificates to smart contract deployers. The CA verifies the identity and ownership of the smart contract creator and embeds this verification information in a digital certificate. This certificate is then stored within the smart contract itself, providing a trusted intermediary mechanism that resolves the contradiction between open accessibility and reliable ownership verification.
Solution Approach 2:
The patent implements preliminary verification by requiring smart contract deployers to obtain digital certificates from a certificate authority before deployment. The ownership and identity information is verified and embedded in the smart contract during the deployment phase, rather than attempting to verify it later. This preliminary action ensures that ownership verification is built into the contract from the start, preventing fraud before it can occur.
2Ease of operation
If anyone can create and deploy smart contracts on the blockchain, then decentralization is improved, but the ability to distinguish genuine contracts from forged copies deteriorates
Solution Approach 1:
The patent uses visual indicators to indicate the authenticity of smart contracts. Verified smart contracts display a blue checkmark icon next to their contract address, while unverified contracts do not show this indicator. This visual differentiation makes it easy for users to distinguish between genuine and potentially forged contracts without requiring technical expertise to analyze the underlying code or verification mechanisms.
Solution Approach 2:
The patent introduces a certificate authority (CA) as an intermediary that issues digital certificates to smart contract deployers. The CA verifies the identity and ownership of the smart contract creator and embeds this verification information in a digital certificate. This certificate is then stored within the smart contract itself, providing a trusted intermediary mechanism that resolves the contradiction between open accessibility and reliable ownership verification.
3Reliability
If digital certificates are used to verify smart contract ownership, then security is improved, but the complexity of the authentication process increases
Solution Approach 1:
The patent implements self-service authentication where the smart contract automatically contains and manages its own ownership verification information. The digital certificate is embedded directly within the smart contract code, and the contract itself performs the verification of its owner's identity. This eliminates the need for external authentication systems or complex verification processes, as the smart contract serves its own authentication needs internally.
4Adaptability or versatility
If third-party blockchain explorers are used to verify contracts, then accessibility is improved, but the ability to provide clear authenticity indicators deteriorates
Solution Approach 1:
The patent uses visual indicators to indicate the authenticity of smart contracts. Verified smart contracts display a blue checkmark icon next to their contract address, while unverified contracts do not show this indicator. This visual differentiation makes it easy for users to distinguish between genuine and potentially forged contracts without requiring technical expertise to analyze the underlying code or verification mechanisms.
Data Source
AI summary
Methods and systems for authenticating and verifying smart contracts. One of the methods of authentication includes an entity: obtaining a digital certificate and a key pair; performing a key pair and a digital certificate ownership verification process; upon confirming that the entity owns the key pair and digital certificate, deploying a smart contract on a blockchain and storing the digital certificate and the public key on the smart contract. One of the methods of verification includes: reading a smart contract address, a public key and a digital certificate on a smart contract; reading a public key and/or private key entered by an entity; verifying that the entity is associated with the public key and/or private key; verifying the public key in the smart contract, the public key in the digital certificate, and the public key entered by entity are all identical.


