Smart Contract Registry for Dynamic Subscription Notifications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional blockchain systems lack the ability to efficiently notify subscribers of changes to smart contracts, as they are immutable and do not allow for editing of transactions, which limits the dynamic management of subscriptions and parameter changes.

Innovation Solution

Implementing a smart contract registry that allows for subscription management and notification of changes by adding registry entries for requestors and subscribers, and enabling edit transactions (ETX) to modify blockchain parameters, thereby allowing dynamic notification of subscribers to changes in smart contract parameters or properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain systems are made immutable to ensure integrity, then reliability is improved, but the ability to notify subscribers of changes is lost

Engineering Contradiction:
Improveblockchain integrityVSAvoidsubscription notification capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the blockchain system into two distinct parts: the immutable ledger that stores transaction history and ensures integrity, and a separate subscription management mechanism that enables change notification. This segmentation allows the blockchain to maintain its immutable nature while the subscription system operates independently to handle notification requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a subscription registry and event emission system. When a smart contract parameter changes, the system emits events that are recorded in the subscription registry, which then notifies relevant subscribers. This intermediary layer bridges the immutable blockchain with the dynamic notification requirements without compromising either aspect.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If conventional blockchain systems are used without edit transactions, then system simplicity is maintained, but dynamic management of subscriptions and parameter changes is limited

Engineering Contradiction:
Improvesystem structureVSAvoidparameter change management
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces dynamic capabilities to the blockchain system through edit transactions (ETX) that allow parameters to be modified after deployment. This dynamic mechanism enables the system to adapt to changing requirements while maintaining a relatively simple overall structure. The edit transaction system works seamlessly with existing smart contract frameworks, adding flexibility without significant complexity overhead.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If edit transactions are implemented to allow parameter changes, then adaptability is improved, but the traditional immutable blockchain characteristic is compromised

Engineering Contradiction:
Improveparameter edit capabilityVSAvoidblockchain immutability
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent segments the blockchain into immutable transaction records and a separate edit transaction system. Traditional transactions remain immutable and form the basis of the ledger, while edit transactions are handled through a distinct mechanism that maintains compatibility with the immutable structure. This segmentation preserves blockchain immutability for core transactions while enabling parameter edits through the ETX framework.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements parameter changes through a dedicated edit transaction mechanism that modifies smart contract parameters without altering the fundamental immutable nature of the blockchain. The ETX system changes parameters by creating new state representations while maintaining the historical immutability of the original transactions, thus reconciling adaptability with immutability.

Inventive Principle:
Principle #35Parameter changes

4Adaptability or versatility

If a subscription registry is added to enable change notifications, then subscriber notification capability is improved, but system complexity increases

Engineering Contradiction:
Improvesubscriber notification functionVSAvoidregistry and notification mechanism
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent designs the subscription registry to serve multiple functions: it stores subscription information, tracks parameter changes, emits events, and manages notifications. By making this component multi-functional, the system achieves comprehensive subscriber notification capability without proportionally increasing complexity. The same registry structure handles various operations including subscription registration, change detection, and event dissemination.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11115804B2Subscription to dependencies in smart contracts
Publication Date: 2021.09.07 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11115804B2 patent drawing
  • US11115804B2 patent drawing
  • US11115804B2 patent drawing

AI summary

The disclosed technology is generally directed to smart contract technology. In one example of the technology, responsive to a smart contract subscription request from a requestor to a first smart contract, a registry entry is added to a first smart contract registry such that the added registry entry includes requestor information associated with the requestor, and subscription information associated with at least one exposed interface of the first smart contract. Responsive to a change occurring that is associated with at least one exposed interface of the first smart contract, based on the registry, any subscribers to the first smart contract that have a subscription to which the change pertains are determined. Responsive to determining subscribers to the first smart contract that have a subscription to which the change pertains, the determined subscribers are caused to be notified of the change.