Trustless Blockchain Notification Service Design

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, bottlenecks during high traffic, and limited data access, which are not addressed by traditional notification systems in blockchain networks.

Innovation Solution

A decentralized trustless notification service using a blockchain-based system where a notifier node connects to a notifier service node to determine if it is designated for a transaction, allowing it to send push notifications to user nodes involved in the transaction, ensuring timely and secure notifications without relying on trusted peers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to store and maintain data, then it is easy to manage, maintain, and control for security purposes, but it has a single point of failure and all data is lost if failures occur

Engineering Contradiction:
Improveease of managementVSAvoidfault tolerance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple decentralized nodes distributed across the network. Each node maintains a copy of the ledger, eliminating the single point of failure while preserving management capabilities through consensus protocols and standardized interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces blockchain consensus mechanisms as intermediaries that coordinate between decentralized nodes. These consensus protocols enable automatic coordination and conflict resolution, maintaining system-wide consistency without requiring centralized control, thus achieving both decentralization and manageable operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If a centralized database is used, then data redundancy is minimized with a single storing place, but data access is limited and multiple devices cannot access the same data simultaneously without creating problems

Engineering Contradiction:
Improvedata redundancyVSAvoiddata access capability
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent implements copying by distributing identical copies of the ledger data across multiple decentralized nodes. Each node maintains a complete or partial copy, enabling simultaneous access by multiple devices without data conflicts, as the immutable blockchain structure ensures consistency across all copies.

Inventive Principle:
Principle #26Copying

3Ease of operation

If traditional notification systems are used in blockchain networks, then peers can be enlisted for notifications, but trust is required and susceptibility to failure or maliciousness increases

Engineering Contradiction:
Improvenotification deliveryVSAvoidtrustlessness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements self-service by enabling nodes to autonomously determine their notifier status through cryptographic verification of blockchain data. Nodes independently verify whether they are designated notifiers using public-key cryptography and blockchain transaction data, eliminating the need to trust external peers while maintaining reliable notification delivery.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11032355B2Trustless notification service
Publication Date: 2021.06.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11032355B2 patent drawing
  • US11032355B2 patent drawing
  • US11032355B2 patent drawing

AI summary

An example operation may include one or more of connecting, by a notifier node, to a notifier service node configured to designate the notifier node, receiving, by the notifier node, a notification from the notifier service node to read a block from a ledger of a blockchain, applying, by the notifier node, a function on the block to determine if the notifier node is a designated notifier for at least one submitted transaction in the block, and, in response to a determination that the notifier is the designated notifier, sending, by the notifier node, a push notification to user nodes involved in a transaction associated with the block.