Versioned Bitcoin Data Storage Using Derived Public Key Indexing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The rapid growth of AI and ML has led to an exponential increase in the demand for high-quality training data, straining the available pool of quality public data online, with issues of opacity, unfair compensation, and lack of control for data providers, while AI companies seek untapped information sources and experiment with synthetic data that could cause malfunctions.
Innovation Solution
A privacy-preserving data collaboration platform utilizing adversarial question generation techniques and cryptographic shares for secure, decentralized data storage and retrieval, ensuring transparent, auditable, and incentivized data collection, with verifiable aggregation functions and compliance with data privacy regulations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is stored directly on Bitcoin blockchain using op_return, then data storage is possible, but data size is limited to 80 Bytes
Solution Approach 1:
The patent segments large datasets into smaller chunks that can be stored on the Bitcoin blockchain. Each chunk is stored as a separate transaction, with the original public key serving as an index to retrieve all segments. This allows substantial data to be stored while maintaining compatibility with Bitcoin's transaction size limits.
Solution Approach 2:
The patent introduces an intermediary indexing system using the original public key. Instead of storing all data in a single transaction, the public key acts as a mediator that links multiple transactions containing different data segments. This intermediary mechanism enables efficient retrieval of segmented data without exceeding blockchain size constraints.
2Reliability
If versioned data is stored on blockchain, then data updates can be tracked, but storage efficiency decreases due to redundant data
Solution Approach 1:
The patent uses cryptographic hashing to create compact representations of data versions. Instead of storing complete copies of each version, it stores hash values that serve as unique identifiers for each version. This copying mechanism allows efficient version tracking while minimizing storage requirements on the blockchain.
Solution Approach 2:
The patent changes the parameter representation from storing complete data to storing cryptographic parameters (hashes, public keys). By transforming the data into its cryptographic parameter representation, the system achieves efficient version tracking with minimal storage overhead, as identical data versions produce identical hash values.
3Reliability
If decentralized data storage is implemented, then security and immutability are improved, but data management complexity increases
Solution Approach 1:
The patent makes the original public key serve multiple functions simultaneously: it acts as a cryptographic key for secure access, an index for retrieving segmented data, and a version tracker for managing data updates. This multi-functionality reduces management complexity by consolidating multiple management tasks into a single universal identifier.
Solution Approach 2:
The system enables self-service data management where the cryptographic parameters themselves perform management functions. The public key automatically serves as the retrieval index, and cryptographic hashes automatically track versions, eliminating the need for separate management systems and reducing overall complexity while maintaining security.
4Reliability
If existing blockchain storage methods are used, then data can be anchored, but contextual meaning is lost due to minimal data storage
Solution Approach 1:
The patent implements a nested structure where cryptographic anchors (hashes and public keys) are embedded within the blockchain, and these anchors in turn point to and contain references to larger datasets stored off-chain. This nested arrangement preserves the anchoring reliability while recovering contextual meaning by enabling access to the full nested data structure.
Solution Approach 2:
The patent transitions from storing data in a single dimension (directly in blockchain transactions) to a multi-dimensional structure where blockchain transactions contain cryptographic anchors that reference data segments stored in another dimension (off-chain storage). This dimensional change allows minimal on-chain storage while preserving complete contextual information in off-chain storage.
Data Source
AI summary
The present embodiment discloses a novel process and system for storing versioned data on the Bitcoin blockchain network. This process involves generating derived public keys linked to specific versions and data parts using a key tweaking method, and storing each data part on the blockchain using its associated derived public key. Information about versions and parts are stored in root transactions. An API is provided for managing the stored data, with options for encryption, checksums, data anchoring, timestamping, segmentation, and digital signatures. AIDIOS, a data protocol designed for direct storage and retrieval on the Bitcoin blockchain, is also included. This system allows for significant amounts of data to be stored directly on the blockchain.