Distributed Entity Tracking With Split Metadata Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing entity tracking systems face issues with security, trust, inefficiency, and high operational costs due to the use of centralized ledgers, while distributed ledgers require significant processing resources and energy for maintaining metadata-rich transaction blocks.
Innovation Solution
Implementing a system where metadata is stored in a separate database, with only ownership transfers recorded on an immutable ledger, reducing data volume and processing requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If metadata is stored on the distributed ledger, then entity tracking security and trust are improved, but processing resources and energy consumption increase significantly
Solution Approach 1:
The patent divides the data storage system into two segments: a distributed ledger that stores only essential ownership transfer records (virtual identifier, account identifiers, transfer indication) and a separate metadata database that stores entity metadata. This segmentation allows the ledger to maintain security and immutability while avoiding the energy-intensive processing of large metadata volumes on the distributed network.
Solution Approach 2:
The patent extracts metadata from the distributed ledger storage scope and places it in a separate metadata database. Only the minimal necessary data for ownership tracking (transaction records with virtual identifiers and account identifiers) remains on the ledger. This extraction resolves the contradiction by removing the energy-consuming element (metadata storage and validation) from the security-critical distributed ledger while preserving entity tracking integrity.
2Reliability
If distributed ledgers are used to maintain entity ownership chains, then trust and security are improved, but device complexity and operational costs increase
Solution Approach 1:
The system is segmented into a distributed ledger component for ownership tracking and a centralized metadata database component for entity information. This segmentation reduces device complexity by allowing the distributed ledger to focus solely on maintaining the immutable ownership chain, while the metadata database handles complex entity data, effectively dividing system responsibilities.
Solution Approach 2:
The patent introduces an intermediary metadata database that mediates between the distributed ledger and entity information. The ledger stores only references (virtual identifiers) while the metadata database holds detailed entity information. This intermediary structure simplifies the ledger's operational complexity while maintaining trust through the immutable ownership records.
3Measurement precision
If complete entity metadata is recorded on the ledger, then entity verification capability is improved, but data storage volume and processing time increase
Solution Approach 1:
The patent extracts entity metadata from the ledger storage scope and stores it in a separate metadata database. The ledger retains only the virtual identifier and ownership transfer information, while detailed entity metadata (descriptions, images, specifications) are stored externally. This extraction maintains entity verification capability through the immutable ownership chain while dramatically reducing data storage volume on the distributed ledger.
Solution Approach 2:
The system uses virtual identifiers as references that copy the essential identity information needed for verification on the ledger, while the full entity metadata are stored in the metadata database. This copying approach allows verification capability to be maintained through reference links without duplicating large amounts of data across the distributed network.
Data Source
AI summary
In some aspects, the disclosure is directed to methods and systems for secure and authenticated tracking of entity possession via a lightweight centralized or distributed ledger. Ownership records of different entities may be recorded on an immutable ledger such that provenance of the entities is verifiable and a user cannot create or counterfeit an entity. In some implementations, the system may store metadata of entities in a separate database that may store records for each entity and correspond to the respective entity's virtual identifier, enabling the ledger records to contain much less data, saving memory resources and the energy that is required to maintain the ledger. In some implementations, distributed incremental values may be provided to members of an ownership or possession chain of an entity, which may encourage compliance, reporting of ownership transfer, and encourage additional transfers.