Sealed Distributed Ledger System for Privacy and Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems require significant computational resources to maintain redundant replicas of transaction data, leading to inefficiencies and high costs, especially when handling complex transactions and large volumes of data.
Innovation Solution
A sealed distributed ledger (SDL) system that encrypts transactions and stores them in a 'sealed' manner, allowing only authorized nodes to access and validate transactions, reducing the need for all nodes to store and process redundant data by using secure enclaves for encryption and decryption, and employing a Java Virtual Machine (JVM) to obscure memory access patterns and message sizes, thereby enhancing privacy and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all nodes store and process redundant replicas of transaction data, then transaction verification reliability is improved, but computational resource consumption increases
Solution Approach 1:
The patent segments the distributed ledger system into two distinct components: a sealed ledger containing encrypted transaction data that only authorized nodes can access, and a public ledger containing only transaction hashes and metadata visible to all nodes. This segmentation allows verification nodes to work with smaller, less computationally intensive data structures while maintaining security through the sealed portion.
Solution Approach 2:
The patent introduces sealed enclaves as intermediary components that hold encrypted transaction data and provide controlled access to verification nodes. These enclaves act as mediators between the need for data privacy and the need for verification, allowing nodes to verify transactions without directly accessing or processing the full transaction data, thereby reducing computational overhead.
2Manufacturing precision
If all nodes store complete transaction data, then transaction validation accuracy is improved, but storage requirements increase
Solution Approach 1:
The patent divides ledger data into sealed portions (encrypted, stored in secure enclaves) and public portions (hashes, metadata, and verification data stored by all nodes). This segmentation enables nodes to store only the public portion locally, significantly reducing storage requirements while maintaining validation accuracy through access to the sealed portion when needed.
Solution Approach 2:
The patent uses cryptographic hashing to create compact representations (copies) of transaction data that can be stored and verified by all nodes. Instead of storing complete transaction data, nodes store and verify transaction hashes, which are much smaller in size but sufficient for validation purposes.
3Loss of information
If encrypted transactions are stored in sealed ledgers, then transaction privacy is improved, but access complexity increases
Solution Approach 1:
The patent introduces sealed enclaves as intermediary components that manage encrypted transaction data. These enclaves provide a standardized interface for accessing encrypted data, handling decryption and re-encryption operations automatically. This intermediary layer shields users from the underlying cryptographic complexity while maintaining strong privacy protections.
Solution Approach 2:
The patent implements a feedback mechanism where verification nodes can request access to sealed transaction data through standardized protocols. The sealed enclaves respond to these requests by providing necessary decryption capabilities and verification data, creating a feedback loop that maintains privacy while enabling verification without requiring users to understand complex cryptographic operations.
Data Source
AI summary
A system for ensuring privacy of transactions is provided. The system may be performed by a computing system during execution of trusted code within a secure enclave of the computing system. The system receives an indication of a transaction. The system validates the transaction. The system encrypts the validated transaction using an encryption key of the trusted code. The system requests untrusted code of the computing system to store the encrypted validated transaction in a portion of a data store. The untrusted code cannot decrypt the encrypted validated transaction that is stored in the data store. Rather, only the trusted code can decrypt the encrypted validated transaction.