Hierarchical Token Storage for Verifiable Asset Documentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to efficiently and securely store and manage the diverse and complex documentation associated with real-world assets like real estate, which often involves numerous users and platforms, leading to separate and incompatible storage of documents across different actors.
Innovation Solution
A hierarchical data storage system using blockchain technology, where data is tokenized and hashed cryptographically, allowing for secure, universal access and verification of asset-related information across multiple users, utilizing Ethereum Request for Comment (ERC) protocols and Secure Hash Algorithms (SHA) to create a verifiable and organized record of transactions and documents.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate storage systems are used for different users and platforms, then each system can store its own data independently, but the systems become incompatible and difficult to integrate
Solution Approach 1:
The patent implements a universal storage system where all data from different users and platforms is stored as tokens on a single blockchain. The blockchain serves as a universal ledger that can accommodate various types of data (documents, media, metadata) from multiple sources, eliminating the need for separate incompatible storage systems while maintaining independence of data sources.
Solution Approach 2:
The blockchain acts as an intermediary layer between different users and platforms. Instead of requiring direct integration between separate systems, all data passes through the blockchain as a common medium. The hierarchical structure with root objects serving as intermediaries further facilitates this by providing a standardized interface for organizing and accessing data from various sources.
2Ease of operation
If all data is stored in a single centralized system, then data management becomes simpler, but security and verification become more difficult to ensure
Solution Approach 1:
The patent segments data into hierarchical levels with root objects at the top and child objects below. Each segment contains specific data related to particular assets or transactions, while the hierarchy provides organizational structure. This segmentation maintains simplicity for management while enabling sophisticated verification through the chained relationship between segments.
Solution Approach 2:
The system performs preliminary hashing of data before storage, creating cryptographic fingerprints that enable verification. The hierarchical structure is pre-established with root objects that contain metadata about child objects, allowing for efficient verification without requiring complex search processes. This preliminary preparation maintains ease of operation while ensuring reliability.
3Loss of information
If detailed documentation is stored for each asset, then information completeness improves, but storage efficiency and accessibility deteriorate
Solution Approach 1:
The patent implements a nested hierarchical structure where root objects contain metadata about child objects, which in turn contain detailed documentation. This nesting allows the system to store comprehensive information while maintaining efficiency by organizing data in a compact, hierarchical manner that enables selective retrieval of only the detailed information needed for specific assets.
Solution Approach 2:
The system adds a hierarchical dimension to data organization, transitioning from flat storage to multi-level structure. Root objects provide high-level summaries while child objects contain detailed information, creating a dimensional approach that improves both completeness and efficiency by allowing users to navigate information at appropriate levels of detail.
Data Source
AI summary
Computing systems are configured to provide a hierarchical organization of blockchain operations, efficiently storing recursive hashes that allow quick verification of received data and data state. Received data from authorized users in associated and stored by representation at a corresponding position in the hierarchy. The computer hashes and tokenizes received data with the hash and stores the same. Each token created is then separately hashed with time and creator into a listing of all such tokens within an object. Such re-hashing is reiterated up each hierarchy level and stored in the containing object. The lists of all hashes at each level can be used to verify a state or individual document that will be reflected in the stored listings is accurate or currently true. Additionally, user actions and histories, as well as state progression and history, can be queried and reported easily with the lists.