Blockchain Smart Contract References for Lower Processing Load
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain technologies face inefficiencies in executing digital contracts due to the need to store and process extensive programming code, which burdens the blockchain network and increases processing requirements.
Innovation Solution
The approach involves referencing a digital contract identifier and contractual parameters within the blockchain, rather than storing the actual code, allowing the contract server or network resource to retrieve and execute the contract independently, thus simplifying the blockchain and reducing its size and processing demands.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If extensive programming code is stored within the blockchain for digital contract execution, then contract execution capability is improved, but blockchain size and processing requirements increase
Solution Approach 1:
The patent extracts the programming code from the blockchain and stores it externally at network resources. The blockchain only contains references (identifiers and parameters) to the code, separating the code storage function from the blockchain itself. This resolves the contradiction by maintaining contract execution capability while significantly reducing blockchain size.
Solution Approach 2:
The patent introduces an intermediary layer between the blockchain and the programming code. This intermediary consists of references stored in the blockchain that point to external network resources where the actual code is hosted. This mediator enables contract execution without embedding the code directly in the blockchain, thus reducing blockchain volume.
2Adaptability or versatility
If extensive programming code is stored within the blockchain, then contract execution capability is improved, but processing requirements and computational burden increase
Solution Approach 1:
The programming code is extracted from the blockchain and stored externally. The blockchain only stores lightweight references (identifiers and parameters), which dramatically reduces the computational burden on the blockchain for processing and validation operations.
Solution Approach 2:
The system segments the contract execution function into two parts: (1) reference storage in the blockchain, and (2) actual code execution at external network resources. This segmentation allows the blockchain to remain computationally lightweight while maintaining full contract execution capability through external resources.
3Adaptability or versatility
If programming code is stored within the blockchain, then digital contract execution is enabled, but scalability is limited
Solution Approach 1:
By extracting code from the blockchain and storing it externally, the system enables unlimited scalability. The blockchain only needs to store small references, allowing it to handle a vast number of contracts without the constraints of embedded code storage capacity.
Solution Approach 2:
The patent moves code storage from the blockchain's internal dimension to an external network resource dimension. This dimensional shift allows the blockchain to scale independently of code size, as the external resources can accommodate arbitrary amounts of code without affecting blockchain capacity.
Data Source
AI summary
Digital or “smart” contracts execute in a blockchain environment. Any entity (whether public or private) may specify a digital contract via a contract identifier in a blockchain. Because there may be many digital contracts offered as virtual services, the contract identifier uniquely identifies a particular digital contract offered by a virtual machine, vendor or supplier. The blockchain is thus not burdened with the programming code that is required to execute the digital contract. The blockchain need only include or specify the contract identifier (and perhaps one or more contractual parameters), thus greatly simplifying the blockchain and reducing its size (in bytes) and processing requirements.