Blockchain Fork Conflict Detection and Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain management techniques for use reservations allow improper use of objects by exploiting blockchain behavior during fork events, leading to unaccounted usage and fee evasion.
Innovation Solution
A control method that compares and updates blockchains between nodes after communication is restored, ensuring proper transaction data is recorded and detecting conflicting contract information to prevent improper use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain is used to manage use reservations, then information management between vehicle terminal and user terminal is improved, but improper use of objects can occur by exploiting blockchain behavior during fork events
Solution Approach 1:
The system performs preliminary actions by establishing communication state tracking before fork events occur. The managing device records which nodes were able to communicate during block generation, and uses this information in advance to identify and reject blocks generated during communication disruptions, preventing improper use before it can exploit the fork
Solution Approach 2:
The system implements feedback mechanisms by having nodes report their communication status and by the managing device verifying block generation conditions. The managing device receives block generation notifications, checks communication state records, and provides feedback by accepting or rejecting blocks based on whether they were generated during proper communication conditions, thereby preventing exploitation of fork events
2Adaptability or versatility
If blockchain nodes operate independently during communication disruptions, then node autonomy is improved, but transaction data consistency deteriorates
Solution Approach 1:
Before communication disruptions occur, the system preliminarily establishes a record of which nodes were in a communicative state during each block generation. When disruptions occur and nodes operate independently, this pre-established record enables the managing device to later identify which independently generated blocks should be rejected, maintaining consistency without compromising node autonomy during the disruption
Solution Approach 2:
The managing device acts as an intermediary that receives blocks from various nodes, including those generated during communication disruptions. It mediates between node autonomy (allowing independent block generation) and data consistency (rejecting blocks from disruption periods) by checking communication state records and selectively accepting or rejecting blocks based on whether they were generated during proper communication conditions
3Quantity of substance
If all transaction data from different blocks is retained, then data completeness is improved, but detection of conflicting contract information becomes more difficult
Solution Approach 1:
The system extracts and separates conflicting transaction data into distinct blocks with clear identifiers. By taking out conflicting contracts and placing them in separate, identifiable blocks, the system maintains data completeness while making conflicts easily detectable through block comparison, rather than hiding them within a single undifferentiated data set
Solution Approach 2:
The system segments transaction data into distinct blocks, each containing specific transaction information. When conflicts occur, they are segmented into separate blocks that can be individually identified and compared. This segmentation maintains the quantity of transaction data while making conflicts detectable through systematic block-by-block comparison rather than searching through undifferentiated data
Data Source
AI summary
A control method is executed by a first node holding a first distributed ledger in which a first blockchain is managed, and includes: obtaining, from a second node, a second blockchain managed by a second distributed ledger held by the second node, and comparing the second blockchain with the first blockchain; updating the first blockchain by adding the greater of at least one first different block contained in the first blockchain but not the second blockchain and at least one second different block contained in the second blockchain but not the first blockchain, after at least one common block, and adding at least one additional block containing at least one instance of transaction data contained in the lesser; and determining whether at least two instances of transaction data each containing at least two instances of contract information that conflict with each other are contained in the updated first blockchain.


