Granted Patent B2

US 12,354,089 · App. 18/648,183 · Granted Jul 8, 2025

Inventor: Prithvi Krishnan Padmanabhan (San Francisco, CA)

Assignee: Salesforce, Inc.

G06Q20/3825G06Q20/065G06Q20/38215H04L9/3213H04L9/50H04L2209/56

Abstract

Claims (44)

1. A method implemented at a database system, the method comprising:

providing, by a database processor, computing services to a plurality of tenants of the database system via the Internet;

receiving, by the database processor, from a client machine a request to execute an action related to a smart contract owned by a synthetic public trust ledger party and recorded on a public trust ledger external to the database system;

identifying, by the database processor, a database system account associated with the requested action and linked with a tenant of the plurality of tenants;

determining, by the database processor, that the database system account is authorized to perform the action based on identity and access management information stored in the database system and associated with the synthetic public trust ledger party;

transmitting, by a ledger API, to a replica node of the public trust ledger external to the database system a ledger request to perform the action, the request using one or more private keys for the synthetic public trust ledger party to authenticate the synthetic public trust ledger party to the replica node;

receiving, by the ledger API, from the replica node a ledger response indicating that the public trust ledger has been updated to reflect successful execution of the action;

updating, by the database processor, one or more records within the database system to reflect successful execution of the action; and

transmitting, by the database processor, to the client machine a response message indicating that the action has been performed.

2. The method recited in claim 1 , wherein the database system account is an owner of the smart contract.

3. The method recited in claim 1 , wherein the action transfers a token from a first party to a second party.

4. The method recited in claim 1 , wherein the action mints a fungible token.

5. The method recited in claim 1 , wherein the action mints a non-fungible token.

6. The method recited in claim 1 , wherein the action updates a definition stored in the public trust ledger and reflecting one or more synthetic public trust ledger party rules stored in the database system.

7. The method recited in claim 1 , wherein the database system account is identified in the synthetic public trust ledger party as a subordinate party.

8. The method recited in claim 1 , wherein the one or more private keys are stored within the database system.

9. A database system including a database processor, the database system configured to perform a method comprising:

providing, by a database processor, computing services to a plurality of tenants of the database system via the Internet;

receiving, by the database processor, from a client machine a request to execute an action related to a smart contract owned by a synthetic public trust ledger party and recorded on a public trust ledger external to the database system;

identifying, by the database processor, a database system account associated with the requested action and linked with a tenant of the plurality of tenants;

determining, by the database processor, that the database system account is authorized to perform the action based on identity and access management information stored in the database system and associated with the synthetic public trust ledger party;

transmitting, by a ledger API, to a replica node of the public trust ledger external to the database system a ledger request to perform the action, the request using one or more private keys for the synthetic public trust ledger party to authenticate the synthetic public trust ledger party to the replica node;

receiving, by the ledger API, from the replica node a ledger response indicating that the public trust ledger has been updated to reflect successful execution of the action;

updating, by the database processor, one or more records within the database system to reflect successful execution of the action; and

transmitting, by the database processor, to the client machine a response message indicating that the action has been performed.

10. The database system recited in claim 9 , wherein the database system account is an owner of the smart contract.

11. The database system recited in claim 9 , wherein the action transfers a token from a first party to a second party.

12. The database system recited in claim 9 , wherein the action mints a fungible token.

13. The database system recited in claim 9 , wherein the action mints a non-fungible token.

14. The database system recited in claim 9 , wherein the action updates a definition stored in the public trust ledger and reflecting one or more synthetic public trust ledger party rules stored in the database system.

15. The database system recited in claim 9 , wherein the database system account is identified in the synthetic public trust ledger party as a subordinate party.

16. The database system recited in claim 9 , wherein one or more private keys are stored within the database system.

17. Computer readable media having instructions stored thereon for performing a method at a database system, the method comprising:

providing, by a database processor, computing services to a plurality of tenants of the database system via the Internet;

receiving, by the database processor, from a client machine a request to execute an action related to a smart contract owned by a synthetic public trust ledger party and recorded on a public trust ledger external to the database system;

identifying, by the database processor, a database system account associated with the requested action and linked with a tenant of the plurality of tenants;

determining, by the database processor, that the database system account is authorized to perform the action based on identity and access management information stored in the database system and associated with the synthetic public trust ledger party;

transmitting, by a ledger API, to a replica node of the public trust ledger external to the database system a ledger request to perform the action, the request using one or more private keys for the synthetic public trust ledger party to authenticate the synthetic public trust ledger party to the replica node;

receiving, by the ledger API, from the replica node a ledger response indicating that the public trust ledger has been updated to reflect successful execution of the action;

updating, by the database processor, one or more records within the database system to reflect successful execution of the action; and

transmitting, by the database processor, to the client machine a response message indicating that the action has been performed.

18. The computer readable media recited in claim 17 , wherein the database system account is an owner of the smart contract.

19. The computer readable media recited in claim 17 , wherein the action updates a definition stored in the public trust ledger and reflecting one or more synthetic public trust ledger party rules stored in the database system.

20. The computer readable media recited in claim 17 , wherein the database system account is identified in the synthetic public trust ledger party as a subordinate party.

Assignments (2)

Continuity (3)

References Cited (228)