IP Library Granted Patent US 11,989,726
Granted Patent B2
US 11,989,726 · App. 17/517,522 · Granted May 21, 2024

Database system public trust ledger token creation and exchange

Inventor: Prithvi Krishnan Padmanabhan (San Francisco, CA)
Assignee: Salesforce, Inc.
G06Q20/3825G06Q20/065G06Q20/381G06Q20/38215H04L9/3213H04L9/50H04L2209/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,989,726
App. No.
17/517,522
Filed
Nov 2, 2021
Granted
May 21, 2024
Kind
B2
Art Unit
3685
USPC
705/64
Abstract

A request to exchange of a first quantity of a first fungible digital token type stored within a smart contract instance recorded in a public trust ledger and owned by a first party within the public trust ledger may be received via a communication interface at a database system. The request may authenticate a first account in the database system. The first account may be linked with the first party within the public trust ledger. The smart contract instance may be executed to determine whether the requested exchange is permissible based on one or more transaction rules included within the smart contract instance. The database system may be updated to reflect a transaction recorded within the public trust ledger when it is determined that the requested exchange is permissible.

Claims (28)

1. A method comprising:

receiving via a communication interface at an on-demand database system a request to exchange a first quantity of the first fungible digital token type owned by a first party in the public trust ledger for a second quantity of a second fungible digital token type, the first fungible token type being defined by a smart contract inheriting one or more properties from an originating fungible digital token type defined by the service provider, the on-demand database system providing customer relations management services from a service provider to a plurality of tenants;

authenticating the request as being authorized by a first database account represented in customer relations management data in the on-demand database system and linked with the first party in one or more records stored in the on-demand database system;

executing the smart contract instance to determine whether the requested exchange is permissible based on one or more transaction rules included within the smart contract instance and defined by a tenant account within the on-demand database system based on the one or more properties, the tenant account being linked with a wallet account in the public trust ledger; and

updating the one or more records stored in the on-demand database system to reflect a transaction recorded within the public trust ledger upon determining that the requested exchange is permissible.

2. The method recited in claim 1 , the method further comprising:

determining an exchange rate between the first fungible digital token type and the second fungible digital token type.

3. The method recited in claim 1 , wherein executing the requested exchange comprises exchanging the first quantity of the first fungible digital token type for a third quantity of the originating fungible digital token type and exchanging the third quantity of the originating fungible digital token type for the second quantity of the second fungible digital token type.

4. The method recited in claim 1 , wherein the one or more transaction rules specify a maximum quantity of the first fungible digital token type exchangeable for the second fungible digital token type.

5. The method recited in claim 1 , wherein the one or more transaction rules specify a period of time during which the first fungible digital token type may be exchanged for the second fungible digital token type.

6. The method recited in claim 1 , wherein the one or more transaction rules specify one or more fungible digital token types for which the first fungible digital token type may not be exchanged.

7. The method recited in claim 1 , wherein the smart contract instance is minted based on a smart contract template owned by a designated party within the public trust ledger, the designated party being linked with a designated account in the on-demand database system.

8. The method recited in claim 7 , wherein the one or more transaction rules are defined at least in part by the designated account.

9. A database system implemented on a computing system, the database system configured to perform a method comprising:

receiving via a communication interface at an on-demand database system a request to exchange a first quantity of the first fungible digital token type owned by a first party in the public trust ledger for a second quantity of a second fungible digital token type, the first fungible token type being defined by a smart contract inheriting one or more properties from an originating fungible digital token type defined by the service provider, the on-demand database system providing customer relations management services from a service provider to a plurality of tenants;

authenticating the request as being authorized by a first database account represented in customer relations management data in the on-demand database system and linked with the first party in one or more records stored in the on-demand database system;

executing the smart contract instance to determine whether the requested exchange is permissible based on one or more transaction rules included within the smart contract instance and defined by a tenant account within the on-demand database system based on the one or more properties, the tenant account being linked with a wallet account in the public trust ledger; and

updating the one or more records stored in the on-demand database system to reflect a transaction recorded within the public trust ledger upon determining that the requested exchange is permissible.

10. The database system recited in claim 9 , the method further comprising:

determining an exchange rate between the first fungible digital token type and the second fungible digital token type.

11. The database system recited in claim 9 , wherein executing the requested exchange comprises exchanging the first quantity of the first fungible digital token type for a third quantity of the originating fungible digital token type and exchanging the third quantity of the originating fungible digital token type for the second quantity of the second fungible digital token type.

12. One or more non-transitory computer readable media having instructions stored thereon for performing a method, the method comprising:

receiving via a communication interface at an on-demand database system a request to exchange a first quantity of the first fungible digital token type owned by a first party in the public trust ledger for a second quantity of a second fungible digital token type, the first fungible token type being defined by a smart contract inheriting one or more properties from an originating fungible digital token type defined by the service provider, the on-demand database system providing customer relations management services from a service provider to a plurality of tenants;

authenticating the request as being authorized by a first database account represented in customer relations management data in the on-demand database system and linked with the first party in one or more records stored in the on-demand database system;

executing the smart contract instance to determine whether the requested exchange is permissible based on one or more transaction rules included within the smart contract instance and defined by a tenant account within the on-demand database system based on the one or more properties, the tenant account being linked with a wallet account in the public trust ledger; and

updating the one or more records stored in the on-demand database system to reflect a transaction recorded within the public trust ledger upon determining that the requested exchange is permissible.

13. The one or more non-transitory computer readable media recited in claim 12 , the method further comprising:

determining an exchange rate between the first fungible digital token type and the second fungible digital token type.

Assignments (2)
CHANGE OF NAME Recorded Apr 17, 2024
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 067143/0116 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 2, 2021
From: PADMANABHAN, PRITHVI KRISHNAN
To: SALESFORCE.COM, INC.
Reel/Frame 057999/0591 →
Continuity (2)
Provisional Application 63243595 · Sep 13, 2021
Related Publication 20230080927A1 · Mar 16, 2023
Cited By (2)
US 12,350,594 US 12,355,885