Ledger Segmentation for Private Data Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in maintaining private information and state changes visible only to a single entity within shared object interactions, while ensuring a shared single source of truth for entities engaged in transactions.

Innovation Solution

A method that involves adding private and shared blocks to respective ledgers to update private and shared objects, where private data is stored in a private ledger and shared data is stored in a public ledger, ensuring that only the relevant entity has access to private information while maintaining a shared view of public changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a shared object ledger is used to track interactions between entities, then transparency and shared visibility of transaction states are improved, but the ability to maintain private information visible only to single entities deteriorates

Engineering Contradiction:
Improvevisibility of shared transaction stateVSAvoiddata structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the ledger into two distinct components: a shared object ledger that stores public transaction data visible to all entities, and private object ledgers that store confidential data visible only to specific entities. This segmentation allows the system to simultaneously provide transparent shared visibility while maintaining private information isolation, resolving the contradiction between these two requirements.

Inventive Principle:
Principle #1Segmentation

2Reliability

If private data is stored separately in private ledgers, then security and access control are improved, but the complexity of maintaining multiple ledgers increases

Engineering Contradiction:
Improvedata securityVSAvoidledger management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the management of shared and private ledgers under a unified system architecture that handles both public and private data. The system integrates operations across multiple ledgers through a common interface, allowing entities to interact with both shared and private data through standardized mechanisms, thereby reducing the perceived complexity despite maintaining separate storage structures.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary layer that manages communications and data flow between entities and the multiple ledgers. This intermediary handles the complexity of coordinating updates across shared and private ledgers, providing a simplified interface to entities while maintaining the security and organizational benefits of separate ledger structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If both private and shared blocks are added to respective ledgers, then information security is improved, but the processing time and operational complexity increase

Engineering Contradiction:
Improveinformation securityVSAvoidoperation simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements preliminary action by pre-defining the structure and access rules for both shared and private blocks before transactions occur. The system establishes the ledger architecture, data classification rules, and access permissions in advance, allowing transactions to be processed efficiently without requiring complex real-time decisions about data placement and access control.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20230028702A1Private information with a shared single source of truth
Publication Date: 2023.01.26 INTUIT INC
  • US20230028702A1 patent drawing
  • US20230028702A1 patent drawing
  • US20230028702A1 patent drawing

AI summary

A method uses private information with a shared single source of truth. A message is received responsive to adding a first shared block to a shared object ledger of a shared object. The message includes message data. A private block is added to a private object ledger to update a private object. The private block includes private data from the message data. A second shared block is added to the shared object ledger to update the shared object. The second shared block includes shared data from the message data.