Decentralized Transactional Object Management with Off-Ledger Bodies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In decentralized systems using a distributed ledger, large objects slow down operations due to increased computational demands for verification, affecting responsiveness, decentralization, and security.
Innovation Solution
Implement decentralized policy-based transactional object management by storing only object metadata on the distributed ledger and replicating object body data across multiple nodes, managed by replicators that enforce storage policies and maintain global consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If objects are stored on the distributed ledger, then decentralization and security are preserved, but system operation speed decreases due to increased computational demands for verification
Solution Approach 1:
The patent segments the object into two distinct parts: object metadata and object body. The metadata (containing identification information and storage location) is stored on the distributed ledger to maintain decentralization and security, while the large object body is stored off-ledger in a decentralized file system. This segmentation allows the ledger to remain lightweight and fast while preserving the integrity and traceability of object references through cryptographic hashing.
Solution Approach 2:
The patent extracts the large object body from the distributed ledger storage system and places it in an external decentralized file system. Only the essential metadata needed for verification and tracking remains on the ledger. This extraction eliminates the computational burden of verifying large objects while maintaining the core benefits of decentralized verification through metadata hashing.
2Quantity of substance
If object size increases, then more information is stored, but computational demands for verification increase causing delays
Solution Approach 1:
The patent creates a cryptographic hash (digital fingerprint) of the object body and stores this hash in the metadata on the distributed ledger. Instead of storing and verifying the entire large object on the ledger, nodes verify the object by checking if its hash matches the stored metadata hash. This copying approach allows verification of large objects to be reduced to verifying a small fixed-size hash value, dramatically reducing verification time while maintaining security.
3Adaptability or versatility
If objects are managed in a decentralized manner, then system autonomy is maintained, but coordination complexity increases
Solution Approach 1:
The patent implements a feedback mechanism where object metadata stored on the distributed ledger serves as a source of truth that guides all nodes in the system. When objects are added, modified, or deleted, the metadata is updated on the ledger, and all nodes can independently verify and follow these changes by checking the ledger. This feedback loop maintains decentralized autonomy while reducing coordination complexity, as nodes don't need to directly communicate with each other - they all reference the same authoritative metadata on the ledger.
Data Source
AI summary
Systems and methods are disclosed for providing decentralized policy-based transactional object management for systems employing federated workflows. Various disclosed components may be added to one or more nodes of a decentralized network, wherein the disclosed components perform registration, replication, and read/write access interfacing functions. These functions result in the storage of objects on the decentralized network in a way which allows for decentralized, policy-based, and transactional management of the objects.