Multi-Owner Database Tokens on Public Trust Ledgers for Cloud Transactions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing environments are controlled by a service provider, requiring trust in their security and integrity, while public trust ledgers lack a platform for managing transactions typical of cloud computing systems, necessitating improved transaction management techniques.

Innovation Solution

Integrate an on-demand database system with a public trust ledger to securely record transactions, allowing entities to create and manage digital assets with ownership changes recorded in the ledger, supporting non-fungible tokens and enabling interactions between database systems and public trust ledgers for secure, publicly verifiable transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud computing services are used to provide shared resources and applications, then service delivery and resource sharing are improved, but dependence on a trusted service provider and control over security are worsened

Engineering Contradiction:
Improveservice deliveryVSAvoidtrust in service provider
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces a public trust ledger (blockchain) as an intermediary between users and cloud service providers. The ledger records and verifies transactions, ownership transfers, and access rights without requiring trust in the service provider. Smart contracts automatically enforce agreements, acting as a mediator that eliminates the need for users to trust the provider's security measures while maintaining efficient service delivery.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a public trust ledger is used to record transactions without a trusted party, then independence and security are improved, but lack of platform for cloud computing operations is worsened

Engineering Contradiction:
Improvesecurity without trusted partyVSAvoidplatform for cloud operations
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a multi-functional system where the public trust ledger not only records transactions but also executes smart contracts, manages digital asset ownership, controls access rights, and coordinates with cloud computing platforms. This universal system handles diverse cloud computing operations (resource allocation, billing, access control) directly on the blockchain, making the ledger adaptable to various cloud operations while maintaining security without a trusted party.

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

3Reliability

If digital assets are created and managed on blockchain with smart contracts, then security and verifiability are improved, but system complexity is worsened

Engineering Contradiction:
Improvesecurity and verifiabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service through automated smart contracts that execute transactions, verify ownership, and manage access rights without human intervention. The system automatically handles asset creation, transfer, and verification processes that would otherwise require complex manual procedures. This automation reduces the operational complexity of managing secure digital assets on blockchain, making the system more manageable while maintaining high security and verifiability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12354089B2Database system public trust ledger multi-owner token architecture
Publication Date: 2025.07.08 SALESFORCE INC
  • US12354089B2 patent drawing
  • US12354089B2 patent drawing
  • US12354089B2 patent drawing

AI summary

A request to perform an action related to a smart contract recorded on a public trust ledger external to the database system may be received via a communication interface at a database system. The request may authenticate a designated database system account. A determination may be made as to whether the designated database system account is authorized to perform the action by accessing definition information for a public trust ledger synthetic party identifying a plurality of database system accounts authorized to perform one or more actions related to the smart contract. The database system may communicate with a token exchange to perform the action by executing the smart contract when it is determined that the designated database system account is authorized to perform the action.