Distributed Ledger Smart Contract Data Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The subscription-based licensing model for software raises concerns about user control over data, as consumers lose possession and control of their data when using cloud-based services, with issues in data ownership and extraction from vendor infrastructure.

Innovation Solution

A distributed ledger system using smart contracts and transistor-based circuitry is implemented to manage and record software updates, service versions, and license terms, allowing for secure, decentralized control over data and software usage, enabling users to retain ownership and access rights.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If subscription-based licensing model is used, then software updates and maintenance costs are reduced, but user control and possession of data are lost

Engineering Contradiction:
Improvesoftware updates efficiencyVSAvoiduser data control
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

A blockchain-based intermediary system is introduced between the user and the software vendor. The blockchain stores cryptographic hashes of software versions, license terms, and data inventories, serving as a neutral mediator that allows vendors to distribute updates efficiently while enabling users to verify and maintain control over their data through decentralized storage and cryptographic proof mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The software distribution system is segmented into multiple independent components: the vendor maintains the actual software code, the blockchain stores immutable metadata and license terms, and decentralized storage systems hold user data. This segmentation allows the vendor to efficiently update software while users retain control through separate verification and access mechanisms.

Inventive Principle:
Principle #1Segmentation

2Ease of manufacture

If centrally managed hardware is used, then software maintenance cost is reduced, but data ownership and extraction capability are compromised

Engineering Contradiction:
Improvesoftware maintenance costVSAvoiddata extraction capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by having users generate and store cryptographic keys locally before any software interaction. Data inventories and ownership proofs are created in advance and stored on the user's local device, ensuring that users maintain the capability to extract and control their data even when using centrally managed software infrastructure.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If version-based licensing is used, then flexibility for updates is improved, but data ownership standardization is lost

Engineering Contradiction:
Improveupdate flexibilityVSAvoiddata ownership clarity
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The blockchain system provides continuous feedback by maintaining an immutable ledger of software versions, license terms, and data inventories. Each software update and license change is recorded on the blockchain, providing transparent feedback to users about their data ownership rights and the terms of service, thereby standardizing data ownership information across different version-based licensing scenarios.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10666426B2Distributed ledger interaction systems and methods
Publication Date: 2020.05.26 DRAGONCHAIN INC
  • US10666426B2 patent drawing
  • US10666426B2 patent drawing
  • US10666426B2 patent drawing

AI summary

Distributed public ledger interaction methods and systems are presented by which one or more elements of a first smart contract are privately recorded on a secure ledger node. In some variants the first smart contract is executed so as to retrieve public ledger node data from a first public ledger node so as to configure at least one transaction that is thereafter executed at least to the first public ledger node or to a second public ledger node (or both).