Enclave Pools for Secure Off-Chain Smart Contract Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems for secure transactions face inefficiencies in executing smart contracts, as they often require running logic directly on the blockchain, which can be resource-intensive and prone to external interference, lacking secure and tamper-resistant execution environments.
Innovation Solution
The formation of an enclave pool that provides secure execution environments (enclaves) for cryptlet code, allowing it to execute off the blockchain, with enclaves being allocated on demand and verified through digital signatures, enabling secure and efficient execution of smart contracts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If smart contract logic is executed directly on the blockchain, then security and decentralization are maintained, but resource consumption and execution time increase significantly
Solution Approach 1:
The patent extracts the smart contract execution logic from the blockchain environment and places it in off-chain enclave environments. The blockchain retains only the critical functions of state tracking and output verification, while the computationally intensive logic execution is performed in isolated enclave pools that can be provisioned on-demand. This extraction reduces blockchain resource consumption while maintaining security through cryptographic verification of enclave execution.
Solution Approach 2:
The patent introduces enclave pools as intermediary components between the blockchain and smart contract logic execution. These enclaves act as trusted mediators that execute logic in tamper-proof environments and provide cryptographic attestation of their execution. The intermediary enclave layer offloads computational work from the blockchain while maintaining verifiable trust through digital signatures and attestation mechanisms.
2Productivity
If smart contract logic is executed directly on the blockchain, then decentralization is maintained, but execution speed and efficiency decrease
Solution Approach 1:
The patent segments the smart contract execution system into multiple independent components: the blockchain layer for state management and verification, and off-chain enclave pools for logic execution. This segmentation allows parallel execution of multiple smart contracts in separate enclave instances, significantly improving throughput and execution speed while maintaining decentralization through cryptographic verification of each enclave's execution integrity.
Solution Approach 2:
The patent implements dynamic enclave provisioning where enclave instances are created on-demand based on smart contract execution requirements and deallocated after completion. This dynamic allocation optimizes resource utilization and execution speed by providing dedicated enclave environments for each execution task, while the blockchain maintains decentralized oversight through verification of enclave attestation and state transitions.
3Use of energy by moving object
If enclave pools are introduced for off-chain execution, then resource efficiency improves, but system complexity increases
Solution Approach 1:
The patent designs the enclave pool as a universal infrastructure that can service multiple smart contracts and diverse computation workloads. A single enclave pool manages the lifecycle of multiple enclave instances, handling provisioning, execution, and deallocation across different contracts. This universal approach improves resource efficiency by consolidating management functions while the modular architecture manages complexity through standardized interfaces between the blockchain and enclave layer.
Data Source
AI summary
The disclosed technology is generally directed to secure transactions. In one example of the technology, an enclave pool is formed. The enclave pool may include a plurality of enclaves that are secure execution environments. In some examples, forming the enclave pool includes registering the enclaves of the enclave pool. A request to allocate an enclave from the enclave pool may be received. An enclave may be fetched from the enclave pool responsive to the request to assign the enclave. Cryptlet code is executed in the fetched enclave such that a payload is generated in the enclave. The payload can be digitally signed and/or encrypted by the cryptlet, and can also be digitally signed by the enclave. The fetched enclave may be deallocated.