OTA Smart Contract Update System for Zero-Downtime Blockchain Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing smart contract update mechanisms in blockchain systems are cumbersome, often requiring manual intervention, leading to downtime, complexity, and limited rollback capabilities, which hinders efficient digital transformation and modern software development practices.

Innovation Solution

An over-the-air (OTA) smart contract update system that automatically deploys new business logic across a network of peers, supports zero-downtime updates, rollback capabilities, and concurrent version execution, utilizing an administration server with engines for API management, authorization, and transaction processing within the Smart Contract Runtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual smart contract update mechanisms are used, then system reliability is maintained through careful review, but update speed and productivity are significantly reduced

Engineering Contradiction:
Improveupdate speedVSAvoidupdate mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The update mechanism is segmented into distinct functional modules: version management module, authorization module, deployment module, and rollback module. Each module handles specific aspects of the update process independently, enabling automated operation while maintaining system reliability through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-defining version control policies, authorization rules, and rollback procedures before updates are needed. This allows the automated update mechanism to execute rapidly without ad-hoc decision-making, resolving the contradiction between speed and reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traditional update deployment is used, then system stability is maintained through sequential updates, but downtime occurs during update transitions

Engineering Contradiction:
Improvesystem stabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system maintains continuous useful action by enabling concurrent execution of multiple contract versions. While the new version is being deployed, the old version continues to handle transactions, ensuring zero downtime. The system seamlessly transitions between versions without interrupting service.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The update mechanism is made dynamic by allowing flexible version switching and concurrent execution. The system can dynamically allocate traffic between different versions and quickly rollback if needed, maintaining stability while eliminating fixed downtime periods.

Inventive Principle:
Principle #15Dynamics

3Reliability

If comprehensive version control and rollback capabilities are implemented, then update reliability is improved, but system complexity increases

Engineering Contradiction:
Improveupdate reliabilityVSAvoidversion management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The version control system operates autonomously through self-service mechanisms: automatic version tracking, automated rollback execution based on predefined policies, and self-managed version metadata. This reduces the perceived complexity for users while maintaining comprehensive version control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback loops that automatically monitor update status, version performance, and system health. Based on this feedback, the system automatically triggers rollback procedures when needed, reducing the complexity of manual version management while improving reliability.

Inventive Principle:
Principle #23Feedback

4Productivity

If automated update deployment is implemented, then productivity and update speed are improved, but auditability and control are reduced

Engineering Contradiction:
Improvedeployment efficiencyVSAvoidaudit trail completeness
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The automated system implements comprehensive feedback mechanisms that record all update actions, decisions, and outcomes in an immutable audit trail. This feedback loop ensures complete auditability while maintaining automated deployment efficiency, as the system self-documented its actions.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

An intermediary audit module acts as a mediator between the automated update process and external observers. This module captures all automated actions, maintains detailed logs, and provides audit trails without interfering with the speed of automated deployment.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11874827B2System and method for automatic, rapid, and auditable updates of digital contracts
Publication Date: 2024.01.16 KESS PAUL L INC
  • US11874827B2 patent drawing
  • US11874827B2 patent drawing
  • US11874827B2 patent drawing

AI summary

A system and method for automatic, rapid, and auditable updates of digital contracts allows participants to make agreed upon changes to a digital contract that is auditable and fast, so as to improve security, as well as reduce maintenance and operations costs of the management and execution of digital contracts.