Blockchain Table Replication with Visibility-Based Key Conflict Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional conflict resolution techniques used in active-active replication cannot be applied to blockchain tables due to the immutability of rows, as modifying or deleting rows would invalidate cryptographic hashes, leading to primary key conflicts.
Innovation Solution
Implement a non-unique index for the primary key constraint in blockchain tables, using a visibility field to designate one row as the winning version among conflicting rows, and manage visibility internally without affecting cryptographic hashes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional conflict resolution techniques are used in active-active replication, then conflict resolution is achieved, but cryptographic security is compromised due to row modification or deletion
Solution Approach 1:
The patent segments the primary key into two components: a unique identifier (chain_id, block_id, tx_id) that ensures uniqueness across blockchains, and a visibility field that enables conflict resolution. This segmentation allows multiple rows with the same identifier to coexist while maintaining cryptographic integrity, as the visibility field controls which row is considered the 'winning' version without modifying actual data or hashes.
Solution Approach 2:
The visibility field acts as an intermediary mechanism between conflicting rows. Instead of directly modifying or deleting rows to resolve conflicts (which would break cryptographic hashes), the visibility field mediates by marking which row should be considered the winner for conflict resolution purposes, allowing both rows to remain in the table with valid cryptographic hashes.
2Reliability
If rows are made immutable to maintain cryptographic hashes, then cryptographic security is preserved, but conflict resolution becomes impossible
Solution Approach 1:
By segmenting the primary key and adding a visibility field, the system maintains immutability of actual row data (preserving cryptographic hashes) while introducing a separate mechanism for conflict resolution. The visibility field can be updated without changing the actual row content or its hash, enabling conflict resolution without compromising cryptographic security.
Solution Approach 2:
The visibility field provides dynamic control over which row is considered the winner in conflicts, while the actual row data remains static and immutable. This allows the system to resolve conflicts by changing visibility status rather than modifying actual data, preserving cryptographic integrity while enabling operational flexibility.
3Reliability
If a unique primary key constraint is used, then data integrity is maintained, but multiple conflicting rows cannot coexist
Solution Approach 1:
The primary key is segmented into a unique identifier portion (chain_id, block_id, tx_id) and a visibility portion. The unique identifier ensures data integrity by preventing duplicate entries across different blockchains, while the visibility field allows multiple rows with the same identifier to coexist, enabling storage of conflicting versions for resolution purposes.
Solution Approach 2:
The visibility field is added locally to the primary key structure, creating a non-unique index that allows multiple rows with the same identifier to exist. This local modification to the key structure enables conflict resolution capability while maintaining the unique identifier's role in ensuring data integrity across the system.
Data Source
AI summary
Disclosed herein are various approaches for supporting active-active replication in a blockchain table having a primary key constraint. A blockchain database object may be stored in a first database, the blockchain database object comprising a field defined as a primary key for the database object and a visibility field. A first row may be inserted in the database object, the first row comprising a particular value for the field designated as the primary key. A primary key value conflict may be detected between the first row and a second row from a second database, the second row comprising the particular value for the field defined as the primary key. A conflict resolution procedure may be implemented to determine that the first row is a winning row of the primary key value conflict between the first row and the second row. A visibility field may be stored within the second row to indicate that the second row does not represent a valid row with respect to the primary key.