Distributed Ledger Code Synchronization via Hash Conflict Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional software development systems face challenges in maintaining synchronization between a developer's working copy of code and the latest version in a source code repository, and are susceptible to single points of failure, leading to inefficiencies and security concerns.

Innovation Solution

A system utilizing a multilayered distributed ledger structure performs real-time source code conflict checks by combining the latest nonce from a primary distributed ledger with the genesis block of a working distributed ledger into a hash algorithm, ensuring mismatches are detected and production systems remain updated, with consensus algorithms like proof of authority and proof of work for validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a conventional source code repository is used, then code storage and version control are provided, but the working copy becomes desynchronized with the latest code version

Engineering Contradiction:

Improvesynchronization reliabilityVSAvoidcode version consistency

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The system implements continuous feedback mechanisms through real-time conflict checks that compare the working distributed ledger with the primary distributed ledger. When desynchronization is detected, the system automatically triggers synchronization operations to restore consistency, ensuring the working copy remains aligned with the latest code version.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary conflict detection by continuously monitoring for changes in the primary ledger before they propagate to working copies. This proactive approach prevents desynchronization by preparing synchronization operations in advance, ensuring code version consistency is maintained preemptively.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If a centralized source code repository is used, then code management is simplified, but the system becomes susceptible to single point of failure

Engineering Contradiction:

Improvesystem availabilityVSAvoiddistributed ledger structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the centralized repository into multiple distributed ledgers - a primary distributed ledger for authoritative code storage and multiple working distributed ledgers for development operations. This segmentation eliminates single points of failure while maintaining simplified code management through the coordinated structure of these distributed components.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the fundamental parameter of repository architecture from centralized to distributed. By implementing a multilayered distributed ledger structure with primary and working ledgers, the system achieves both improved reliability through redundancy and maintained simplicity through standardized synchronization protocols.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If real-time conflict checks are performed, then code synchronization is improved, but computational overhead increases

Engineering Contradiction:

Improvecode synchronizationVSAvoidcomputational energy

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs partial conflict checks by monitoring specific critical parameters such as block hashes and timestamps rather than comparing entire codebases continuously. This selective monitoring approach maintains real-time synchronization reliability while significantly reducing computational energy requirements compared to full code comparison.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system implements periodic conflict checks at strategically determined intervals rather than continuous monitoring. Synchronization operations are triggered periodically or event-driven based on detected changes, ensuring code synchronization is maintained while minimizing unnecessary computational energy expenditure during stable periods.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS11307848B2System for electronic integration and deployment of computer code in a code development network

Publication Date: 2022.04.19 BANK OF AMERICA CORP

AI summary

A system provides electronic integration and deployment of computer code in a code development network. The system may comprise a multilayered distributed ledger structure and may perform real-time source code conflict checks by combining the latest nonce from a primary distributed ledger with the genesis block of a working distributed ledger into a hash algorithm. Depending on whether the output of said hash algorithm satisfies the cryptographic challenge set by the distributed ledger system, the system may be able to detect mismatches between the source code found in a working distributed ledger and the source code found in the primary distributed ledger. Furthermore, the system may include production systems as nodes of the primary distributed ledger such that the production systems may maintain updated copies of the source code throughout the software development process.