Smart Contract Execution in Secure Enclaves
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current decentralized systems, such as those using blockchain, face challenges in scalability, security, and efficiency due to reliance on centralized data structures and the need for trusted third parties, particularly in implementing smart contracts and mitigating Sybil attacks.
Innovation Solution
The implementation of secure execution environments like Intel's SGX enclaves allows for decentralized identification and secure execution of smart contracts without relying on blockchain, using hardware nodes with secure execution units to enable secure transactions and mitigate Sybil attacks, while also allowing direct access to external data sources and improving confidentiality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain is used for decentralized smart contract execution, then security and decentralization are improved, but scalability and transaction efficiency deteriorate
Solution Approach 1:
The system segments the decentralized network into multiple types of nodes with different functions: enclave nodes that execute smart contracts in secure hardware environments, and non-enclave nodes that provide network participation and validation. This segmentation allows the system to maintain decentralization while improving transaction processing efficiency, as enclave nodes can execute contracts faster without requiring all nodes to perform full validation.
Solution Approach 2:
The patent introduces enclave nodes as intermediary entities that bridge the gap between centralized performance and decentralized trust. These nodes use trusted hardware (enclaves) to provide verifiable secure execution, acting as mediators that enable other nodes to trust contract execution without needing to replicate the full computational power and validation processes of traditional blockchain systems.
2Adaptability or versatility
If traditional blockchain consensus protocols are used, then decentralization is maintained, but transaction costs and processing time increase
Solution Approach 1:
The system changes the fundamental parameter of how consensus is achieved by moving from computational consensus (proof-of-work) or stake-based consensus to verification-based consensus. Enclave nodes produce verifiable proofs of secure execution that other nodes can quickly validate, dramatically reducing processing time while maintaining decentralization. The consensus mechanism shifts from requiring extensive computational work to requiring verification of cryptographic proofs.
3Stability of the object's composition
If centralized data structures are used in blockchain, then consistency is maintained, but scalability and flexibility deteriorate
Solution Approach 1:
The patent introduces a new dimension to blockchain architecture by adding hardware-based trust (enclaves) as a vertical layer above the traditional horizontal peer-to-peer network structure. This allows the system to maintain data consistency through cryptographic verification while enabling vertical scaling through hardware acceleration and horizontal scaling through network participation, overcoming the scalability limitations of traditional centralized data structures.
Data Source
AI summary
Method for the secure execution of programs (smart contracts) implemented between a first wallet node (WN) (WN1) and a second wallet node (WN2), at least the second WN being implemented in an enclave of a processor, and the WNs being capable of executing programs designated in the messages that reach them, the method comprising the following steps: a) sending by WN1 to WN2 of a pre-message; b1) in response to this pre-message, execution in the enclave of a first program (WNRoT); b2) generation by the enclave of a certificate of authenticity of said first program and of the integrity of its execution; b3) sending said certificate to WN1; c) verification by WN1 of said certificate; d) in the event of successful verification, sending by WN1 to WN2 of a message intended to trigger the execution of a given program in WN2, and e) execution of said program in WN2.