IP Library Granted Patent US 12,469,077
Granted Patent B2
US 12,469,077 · App. 17/662,804 · Granted Nov 11, 2025

Public trust ledger smart contract representation and exchange in a database system

Inventors: Prithvi Krishnan Padmanabhan (San Francisco, CA); Marc Benioff (San Francisco, CA)
Assignee: Salesforce, Inc.
G06Q40/04G06F16/24558G06Q20/3678G06Q20/3829G06Q20/389G06Q20/4016H04L9/50G06Q2220/00
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 12,469,077
App. No.
17/662,804
Granted
Nov 11, 2025
Kind
B2
Abstract

A designated smart contract representation may be determined based on configuration information provided by a first database system account. The designated smart contract representation may include a binary executable representation of a smart contract template. Access to the designated smart contract representation may be provided via an application exchange in an database system. The database system may provide computing services to a plurality of entities via the internet. The plurality of entities may include a first entity associated with the first database system account and a second entity associated with a second database system account. The application exchange may provide access to a plurality of smart contract representations including the designated smart contract representation. A selection of the designated smart contract representation may be received in association with the second database system account. The binary executable representation may be deployed to a blockchain.

Claims (56)

1 . A method implemented at a computing services environment providing computing services to a plurality of entities via the Internet, the computing services including access to a database system, the method comprising:

determining via one or more processors a designated smart contract representation based on configuration information provided by a first database system account associated with a first entity of the plurality of entities, the designated smart contract representation including a binary executable representation of a smart contract template;

providing the plurality of entities with access to an application exchange by a service provider of the computing services environment via the one or more processors, the application exchange facilitating exchanges of computing resources among the plurality of entities within the computing services environment, the plurality of computing resources including a plurality of applications executable within the computing services environment to provide the computing services, the plurality of computing resources including a plurality of smart contract representations including the designated smart contract representation;

receiving, by the one or more processors, a selection of the designated smart contract representation in association with a second database system account associated with a second entity of the plurality of entities;

deploying by the one or more processors the binary executable representation of the smart contract template to a blockchain outside the computing services environment as a designated instance of the smart contract template, wherein the deploying is authenticated using a cryptographic key pair associated with the second database system account;

receiving a request to perform a blockchain transaction related to the binary executable representation of the smart contract template deployed to the blockchain, the request received at a communication interface from the designated instance of the smart contract template;

determining by the one or more processors a blockchain transaction risk assessment score associated with the blockchain transaction; and

transmitting a response to the designated instance of the smart contract template, the response denying the request to perform the blockchain transaction upon determining that the blockchain transaction risk assessment score exceeds a designated threshold.

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

storing a representation of the designated instance of the smart contract template in the database system, the database system storing information about a plurality of smart contract instances including the designated instance of the smart contract template.

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

transmitting an instruction from the database system to the designated instance of the smart contract template to mint a non-fungible token; and

creating a record in the database system representing the non-fungible token.

4 . The method recited in claim 3 , the method further comprising:

identifying a blockchain transaction in which the non-fungible token is transferred from a first party to a second party on the blockchain; and

storing in the database system a transaction record representing the blockchain transaction.

5 . The method recited in claim 1 , wherein the database system stores information about a plurality of wallet objects, a designated one of the wallet objects corresponding with a wallet in the blockchain, the designated wallet object having as an owner the second database system account.

6 . The method recited in claim 1 , wherein deploying the designated instance of the smart contract template to the blockchain involves receiving one or more smart contract configuration parameters associated with the second database system account and customizing the designated instance of the smart contract template based on the one or more smart contract configuration parameters.

7 . The method recited in claim 1 ,

transmitting an instruction from the database system to the designated instance of the smart contract template to mint a fungible token; and

creating a record in the database system representing the minted fungible token.

8 . The method recited in claim 7 , the method further comprising:

identifying a blockchain transaction in which the fungible token is transferred from a first party to a second party on the blockchain; and

storing in the database system a transaction record representing the blockchain transaction.

9 . The method recited in claim 1 , wherein the binary executable representation is not modifiable by the second database system account.

10 . The method recited in claim 1 , wherein receiving the selection of the designated smart contract representation comprises identifying one or more desired characteristics associated with a smart contract and identifying the designated smart contract representation from a plurality of smart contract representations as exhibiting the one or more desired characteristics.

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

upon receiving the request to perform the blockchain transaction, identifying by the one or more processors one or more security restrictions associated with the request to perform the blockchain transaction, wherein the blockchain transaction risk assessment score is associated with the one or more security restrictions.

12 . The method recited in claim 1 , wherein the database system stores a private key for a blockchain account corresponding with the second database system account, and wherein the database system uses the private key to deploy the designated instance of the smart contract template to the blockchain on behalf of the second database system account.

13 . The method recited in claim 1 , wherein the database system stores in a database a plurality of database objects corresponding with blockchain wallets, blockchain transactions, and blockchain tokens, and wherein the database is a dynamic schema database in which the plurality of database objects are stored in a designated database table.

14 . The method recited in claim 1 , wherein the database system includes a multi-tenant database, and wherein the first database system account is a first tenant within the multi-tenant database, and wherein the second database system account is a second tenant within the multi-tenant database.

15 . A database system implemented at a computing services environment providing computing services to a plurality of entities via the Internet, the database system having a processor and a communication interface, the database system configured to perform a method, the computing services including access to the database system, the method comprising:

determining via one or more processors a designated smart contract representation based on configuration information provided by a first database system account associated with a first entity of the plurality of entities, the designated smart contract representation including a binary executable representation of a smart contract template;

providing the plurality of entities with access to an application exchange by a service provider of the computing services environment via the one or more processors, the application exchange facilitating exchanges of computing resources among the plurality of entities within the computing services environment, the plurality of computing resources including a plurality of applications executable within the computing services environment to provide the computing services, the plurality of computing resources including a plurality of smart contract representations including the designated smart contract representation;

receiving, by the one or more processors, a selection of the designated smart contract representation in association with a second database system account associated with a second entity of the plurality of entities;

deploying by the one or more processors the binary executable representation of the smart contract template to a blockchain outside the computing services environment as a designated instance of the smart contract template, wherein the deploying is authenticated using a cryptographic key pair associated with the second database system account;

receiving a request to perform a blockchain transaction related to the binary executable representation of the smart contract template deployed to the blockchain, the request received at a communication interface from the designated instance of the smart contract;

determining by the one or more processors a blockchain transaction risk assessment score associated with the blockchain transaction; and

transmitting a response to the designated instance of the smart contract template, the response denying the request to perform the blockchain transaction upon determining that the blockchain transaction risk assessment score exceeds a designated threshold.

16 . The system recited in claim 15 , the method further comprising:

storing a representation of the designated instance of the smart contract template in the database system, the database system storing information about a plurality of smart contract instances including the designated instance of the smart contract template.

17 . The system recited in claim 15 , the method further comprising:

transmitting an instruction from the database system to the designated instance of the smart contract template to mint a non-fungible token; and

creating a record in the database system representing the non-fungible token.

18 . The system recited in claim 17 , the method further comprising:

identifying a blockchain transaction in which the non-fungible token is transferred from a first party to a second party on the blockchain; and

storing in the database system a transaction record representing the blockchain transaction.

19 . The system recited in claim 17 , wherein the database system stores information about a plurality of wallet objects, a designated one of the wallet objects corresponding with a wallet in the blockchain, the designated wallet object having as an owner the second database system account.

20 . One or more non-transitory computer readable media having instructions stored thereon for performing a method implemented at a computing services environment providing computing services to a plurality of entities via the Internet, the computing services including access to a database system, the method comprising:

determining via one or more processors a designated smart contract representation based on configuration information provided by a first database system account associated with a first entity of the plurality of entities, the designated smart contract representation including a binary executable representation of a smart contract template;

providing the plurality of entities with access to an application exchange by a service provider of the computing services environment via the one or more processors, the application exchange facilitating exchanges of computing resources among the plurality of entities within the computing services environment, the plurality of computing resources including a plurality of applications executable within the computing services environment to provide the computing services, the plurality of computing resources including a plurality of smart contract representations including the designated smart contract representation;

receiving, by the one or more processors, a selection of the designated smart contract representation in association with a second database system account associated with a second entity of the plurality of entities;

deploying by the one or more processors the binary executable representation of the smart contract template to a blockchain outside the computing services environment as a designated instance of the smart contract template, wherein the deploying is authenticated using a cryptographic key pair associated with the second database system account;

receiving a request to perform a blockchain transaction related to the binary executable representation of the smart contract template deployed to the blockchain, the request received at a communication interface from the designated instance of the smart contract template;

determining by the one or more processors a blockchain transaction risk assessment score associated with the blockchain transaction; and

transmitting a response to the designated instance of the smart contract template, the response denying the request to perform the blockchain transaction upon determining that the blockchain transaction risk assessment score exceeds a designated threshold.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 29, 2025
From: BENIOFF, MARC
To: SALESFORCE, INC.
Reel/Frame 071862/0175 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2024
From: PADMANABHAN, PRITHVI KRISHNAN
To: SALESFORCE, INC.
Reel/Frame 068556/0044 →
Continuity (1)
Related Publication 20230368291A1 · Nov 16, 2023
References Cited (216)
US 10585657B2 · Padmanabhan · 2020 [cited by applicant]
US 10701054B2 · Padmanabhan · 2020 [cited by applicant]
US 10915891B1 · Winklevoss · 2021 [cited by applicant]
US 11038771B2 · Padmanabhan · 2021 [cited by applicant]
US 11082226B2 · Hildebrand · 2021 [cited by applicant]
US 11128465B2 · Hildebrand · 2021 [cited by applicant]
US 11144335B2 · Padmanabhan · 2021 [cited by applicant]
US 11157484B2 · Padmanabhan · 2021 [cited by applicant]
US 11200569B1 · James · 2021 [cited by applicant]
US 11244313B2 · Padmanabhan · 2022 [cited by applicant]
US 11288280B2 · Padmanabhan · 2022 [cited by applicant]
US 11308487B1 · Foster · 2022 [cited by applicant]
US 11315138B1 · Olson · 2022 [cited by applicant]
US 11334883B1 · Auerbach · 2022 [cited by applicant]
US 11372635B2 · Padmanabhan · 2022 [cited by applicant]
US 11430066B2 · Doney · 2022 [cited by applicant]
US 11431486B2 · Padmanabhan · 2022 [cited by applicant]
US 11431693B2 · Padmanabhan · 2022 [cited by applicant]
US 11468406B2 · Padmanabhan · 2022 [cited by applicant]
US 11469886B2 · Padmanabhan · 2022 [cited by applicant]
US 11488176B2 · Padmanabhan · 2022 [cited by applicant]
US 11611560B2 · Padmanabhan · 2023 [cited by applicant]
US 11671531B1 · Mudireddy · 2023 [cited by applicant]
US 11743137B2 · Padmanabhan · 2023 [cited by applicant]
US 11764950B2 · Padmanabhan · 2023 [cited by applicant]
US 11770445B2 · Padmanabhan · 2023 [cited by applicant]
US 11783024B2 · Padmanabhan · 2023 [cited by applicant]
US 20110246460A1 · Hsieh · 2011 [cited by applicant]
US 20150213443A1 · Geffon · 2015 [cited by applicant]
US 20160192165A1 · Agulnik · 2016 [cited by applicant]
US 20160260169A1 · Arnold · 2016 [cited by applicant]
US 20170214522A1 · Code · 2017 [cited by applicant]
US 20170242887A1 · Zhao · 2017 [cited by applicant]
US 20170272901A1 · Chen · 2017 [cited by applicant]
US 20180005186A1 · Hunn · 2018 [cited by applicant]
US 20180219836A1 · Peterson · 2018 [cited by applicant]
US 20180374173A1 · Chen · 2018 [cited by applicant]
US 20190057223A1 · Hanna · 2019 [cited by applicant]
US 20190080406A1 · Molinari · 2019 [cited by applicant]
US 20190109709A1 · Wu · 2019 [cited by applicant]
US 20190146979A1 · Madisetti · 2019 [cited by applicant]
US 20190236559A1 · Padmanabhan · 2019 [cited by applicant]
US 20190236562A1 · Padmanabhan · 2019 [cited by applicant]
US 20190236598A1 · Padmanabhan · 2019 [cited by applicant]
US 20190236606A1 · Padmanabhan · 2019 [cited by applicant]
US 20190238316A1 · Padmanabhan · 2019 [cited by applicant]
US 20190238525A1 · Padmanabhan · 2019 [cited by applicant]
US 20190244243A1 · Goldberg · 2019 [cited by applicant]
US 20190280862A1 · Crego · 2019 [cited by applicant]
US 20190303445A1 · Padmanabhan · 2019 [cited by applicant]
US 20190303926A1 · Yantis · 2019 [cited by examiner]
US 20190318122A1 · Hockey · 2019 [cited by applicant]
US 20190333033A1 · Finlow-Bates · 2019 [cited by applicant]
US 20190340623A1 · Rivkind · 2019 [cited by applicant]
US 20190340689A1 · Gordon, III · 2019 [cited by applicant]
US 20190370544A1 · Wright, Jr. · 2019 [cited by applicant]
US 20190377806A1 · Padmanabhan · 2019 [cited by applicant]
US 20190385236A1 · Mcconnell · 2019 [cited by applicant]
US 20200005284A1 · Vijayan · 2020 [cited by applicant]
US 20200036515A1 · Chari · 2020 [cited by applicant]
US 20200042939A1 · Padmanabhan · 2020 [cited by applicant]
US 20200074461A1 · Derosa-Grund · 2020 [cited by applicant]
US 20200089663A1 · Padmanabhan · 2020 [cited by applicant]
US 20200089670A1 · Padmanabhan · 2020 [cited by applicant]
US 20200089671A1 · Padmanabhan · 2020 [cited by applicant]
US 20200089672A1 · Velisetti · 2020 [cited by applicant]
US 20200092362A1 · Viswanathan · 2020 [cited by applicant]
US 20200112434A1 · Goodson · 2020 [cited by applicant]
US 20200133955A1 · Padmanabhan · 2020 [cited by applicant]
US 20200134656A1 · Padmanabhan · 2020 [cited by applicant]
US 20200137082A1 · Jimenez-Delgado · 2020 [cited by applicant]
US 20200159847A1 · Smith · 2020 [cited by applicant]
US 20200184558A1 · Crumb · 2020 [cited by applicant]
US 20200202038A1 · Zhang · 2020 [cited by applicant]
US 20200204375A1 · Coulmeau · 2020 [cited by applicant]
US 20200204557A1 · Singh · 2020 [cited by applicant]
US 20200213127A1 · Maniyar · 2020 [cited by applicant]
US 20200250174A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250176A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250177A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250295A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250661A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250683A1 · Padmanabhan · 2020 [cited by applicant]
US 20200250747A1 · Padmanabhan · 2020 [cited by applicant]
US 20200252205A1 · Padmanabhan · 2020 [cited by applicant]
US 20200252404A1 · Padmanabhan · 2020 [cited by applicant]
US 20200252406A1 · Padmanabhan · 2020 [cited by applicant]
US 20200287718A1 · Hildebrand · 2020 [cited by applicant]
US 20200287719A1 · Hildebrand · 2020 [cited by applicant]
US 20200293500A1 · Patil · 2020 [cited by applicant]
US 20200294165A1 · Yang · 2020 [cited by applicant]
US 20200328899A1 · Glickshtein · 2020 [cited by applicant]
US 20200334752A1 · Doney · 2020 [cited by applicant]
US 20200349142A1 · Padmanabhan · 2020 [cited by applicant]
US 20200349564A1 · Padmanabhan · 2020 [cited by applicant]
US 20200371995A1 · Padmanabhan · 2020 [cited by applicant]
US 20200374105A1 · Padmanabhan · 2020 [cited by applicant]
US 20200374106A1 · Padmanabhan · 2020 [cited by applicant]
US 20200380624A1 · Turgman · 2020 [cited by examiner]
US 20210042746A1 · Westland · 2021 [cited by applicant]
US 20210073647A1 · Hunter · 2021 [cited by applicant]
US 20210117938A1 · Arora · 2021 [cited by applicant]
US 20210133700A1 · Williams · 2021 [cited by applicant]
US 20210150610A1 · Mao · 2021 [cited by applicant]
US 20210150626A1 · Robotham · 2021 [cited by applicant]
US 20210152536A1 · Padmanabhan · 2021 [cited by applicant]
US 20210182272A1 · Shpurov · 2021 [cited by applicant]
US 20210182423A1 · Padmanabhan · 2021 [cited by applicant]
US 20210182773A1 · Padmanabhan · 2021 [cited by applicant]
US 20210182806A1 · Ornelas · 2021 [cited by applicant]
US 20210226774A1 · Padmanabhan · 2021 [cited by applicant]
US 20210240498A1 · Padmanabhan · 2021 [cited by applicant]
US 20210243193A1 · Padmanabhan · 2021 [cited by applicant]
US 20210342329A1 · Padmanabhan · 2021 [cited by applicant]
US 20210357893A1 · Kang · 2021 [cited by applicant]
US 20210373878A1 · Padmanabhan · 2021 [cited by applicant]
US 20210374759A1 · Padmanabhan · 2021 [cited by applicant]
US 20210377028A1 · Doney · 2021 [cited by applicant]
US 20210382966A1 · Shii · 2021 [cited by applicant]
US 20210385087A1 · Hildebrand · 2021 [cited by applicant]
US 20210397604A1 · Padmanabhan · 2021 [cited by applicant]
US 20220006705A1 · Padmanabhan · 2022 [cited by applicant]
US 20220027356A1 · Padmanabhan · 2022 [cited by applicant]
US 20220058633A1 · Yantis · 2022 [cited by applicant]
US 20220094549A1 · Moreno · 2022 [cited by examiner]
US 20220101316A1 · Cramer · 2022 [cited by applicant]
US 20220114238A1 · Padmanabhan · 2022 [cited by applicant]
US 20220129475A1 · Thaw · 2022 [cited by applicant]
US 20220147988A1 · Alexa · 2022 [cited by applicant]
US 20220173893A1 · Basu · 2022 [cited by applicant]
US 20220210061A1 · Simu · 2022 [cited by applicant]
US 20220245560A1 · Dhaliwal · 2022 [cited by applicant]
US 20220248165A1 · Dhaliwal · 2022 [cited by applicant]
US 20220253836A1 · Russell · 2022 [cited by applicant]
US 20220276996A1 · Gaur · 2022 [cited by applicant]
US 20220284008A1 · Treitlinger · 2022 [cited by applicant]
US 20220300487A1 · Wright · 2022 [cited by applicant]
US 20220300966A1 · Andon · 2022 [cited by applicant]
US 20220303141A1 · Branton · 2022 [cited by applicant]
US 20220311611A1 · Gaur · 2022 [cited by applicant]
US 20220351186A1 · Quigley · 2022 [cited by applicant]
US 20220358450A1 · Stephens · 2022 [cited by applicant]
US 20220358462A1 · Oldfield · 2022 [cited by applicant]
US 20220391895A1 · Weber · 2022 [cited by applicant]
US 20220398538A1 · Jakobsson · 2022 [cited by applicant]
US 20220414621A1 · Parlotto · 2022 [cited by applicant]
US 20220414665A1 · Gelda · 2022 [cited by examiner]
US 20220414809A1 · Geng · 2022 [cited by applicant]
US 20230081152A1 · Blazevige · 2023 [cited by applicant]
US 20230126016A1 · Nelson · 2023 [cited by applicant]
US 20230267456A1 · Garner · 2023 [cited by examiner]
US 20230274270A1 · Marty · 2023 [cited by applicant]
AU 2019345039A1 · 2021 [cited by applicant]
AU 2019345040A1 · 2021 [cited by applicant]
AU 2019345041A1 · 2021 [cited by applicant]
AU 2020351764A1 · 2022 [cited by applicant]
CN 111902810A · 2020 [cited by applicant]
CN 111919417A · 2020 [cited by applicant]
CN 113039568A · 2021 [cited by applicant]
CN 113056760A · 2021 [cited by applicant]
EP 3747153A1 · 2020 [cited by applicant]
EP 3776255A1 · 2021 [cited by applicant]
EP 3853794A1 · 2021 [cited by applicant]
JP 2021512416A · 2021 [cited by applicant]
WO 2018109010 · 2018 [cited by applicant]
WO 2019152750A1 · 2019 [cited by applicant]
WO 2019190855A1 · 2019 [cited by applicant]
WO 2019241071A1 · 2019 [cited by applicant]
WO 2020061224A1 · 2020 [cited by applicant]
WO 2020061225A1 · 2020 [cited by applicant]
WO 2020061226A1 · 2020 [cited by applicant]
WO 2020092900A2 · 2020 [cited by applicant]
WO 2020160109A1 · 2020 [cited by applicant]
WO 2020234814A1 · 2020 [cited by applicant]
WO 2021116950A1 · 2021 [cited by applicant]
WO 2021250045A1 · 2021 [cited by applicant]
U.S. Appl. No. 16/294,646, Corrected Notice of Allowance mailed Jun. 30, 2021, 11 pgs. [cited by applicant]
U.S. Appl. No. 16/294,646, Examiner Interview Summary mailed Mar. 29, 2021, 3 pgs. [cited by applicant]
U.S. Appl. No. 16/294,646, Examiner Interview Summary mailed May 28, 2021, 2 pgs. [cited by applicant]
U.S. Appl. No. 16/294,646, Examiner Interview Summary mailed Jun. 30, 2021, 1 pg. [cited by applicant]
U.S. Appl. No. 16/294,646, Non-Final Office Action mailed Feb. 22, 21, 2023 pgs. [cited by applicant]
U.S. Appl. No. 16/294,646, Notice of Allowance mailed May 28, 2021, 13 pgs. [cited by applicant]
U.S. Appl. No. 16/294,654, Corrected Notice of Allowance mailed Jun. 30, 2021, 10 pgs. [cited by applicant]
U.S. Appl. No. 16/294,654, Examiner Interview Summary mailed Mar. 29, 2021, 2 pgs. [cited by applicant]
U.S. Appl. No. 16/294,654, Examiner Interview Summary mailed Jun. 1, 2021, 1 pg. [cited by applicant]
U.S. Appl. No. 16/294,654, Examiner Interview Summary mailed Jun. 30, 2021, 1 pg. [cited by applicant]
U.S. Appl. No. 16/294,654, Non-Final Office Action mailed Feb. 22, 2021, 26 pgs. [cited by applicant]
U.S. Appl. No. 16/294,654, Notice of Allowance mailed Jun. 1, 2021, 13 pgs. [cited by applicant]
Notice of Allowance dated May 11, 2023 for U.S. Appl. No. 17/648,865 (pp. 1-12). [cited by applicant]
Notice of Allowance dated Oct. 20, 2023 for U.S. Appl. No. 17/662,812 (pp. 1-8). [cited by applicant]
Office Action (Final Rejection) dated Jun. 21, 2023 for U.S. Appl. No. 17/410,376 (pp. 1-30). [cited by applicant]
Office Action (Final Rejection) dated Jun. 22, 2023 for U.S. Appl. No. 17/410,366 (pp. 1-32). [cited by applicant]
Office Action (Final Rejection) dated Oct. 24, 2023 for U.S. Appl. No. 17/412,056 (pp. 1-17). [cited by applicant]
Office Action (Final Rejection) dated Nov. 20, 2023 for U.S. Appl. No. 17/517,522 (pp. 1-15). [cited by applicant]
Office Action (Non-Final Rejection) dated Mar. 2, 2023 for U.S. Appl. No. 17/410,376 (pp. 1-26). [cited by applicant]
Office Action (Non-Final Rejection) dated May 24, 2023 for U.S. Appl. No. 17/517,522 (pp. 1-13). [cited by applicant]
Office Action (Non-Final Rejection) dated May 31, 2023 for U.S. Appl. No. 17/412,059 (pp. 1-13). [cited by applicant]
Office Action (Non-Final Rejection) dated Jul. 11, 2023 for U.S. Appl. No. 17/412,056 (pp. 1-16). [cited by applicant]
Office Action (Non-Final Rejection) dated Jul. 26, 2023 for U.S. Appl. No. 17/517,543 (pp. 1-23). [cited by applicant]
Office Action (Non-Final Rejection) dated Sep. 14, 2023 for U.S. Appl. No. 17/410,376 (pp. 1-29). [cited by applicant]
Office Action (Non-Final Rejection) dated Oct. 19, 2023 for U.S. Appl. No. 17/410,366 (pp. 1-23). [cited by applicant]
Office Action (Non-Final Rejection) dated Oct. 26, 2023 for U.S. Appl. No. 17/933,827 (pp. 1-15). [cited by applicant]
Office Action (Non-Final Rejection) dated Dec. 14, 2023 for U.S. Appl. No. 17/662,810 (pp. 1-15). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jul. 27, 2023 for U.S. Appl. No. 17/412,059 (pp. 1-8). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Dec. 20, 2023 for U.S. Appl. No. 17/648,862 (pp. 1-14). [cited by applicant]
Office Action dated Mar. 6, 2023 for U.S. Appl. No. 17/517,541 (pp. 1-28). [cited by applicant]
Office Action dated Sep. 20, 2023 for U.S. Appl. No. 17/517,541 (pp. 1-24). [cited by applicant]
Padmanabhan, Prithvi Krishnan et al., “Database System Public Trust Ledger Contract Linkage”, U.S. Appl. No. 17/412,059, filed Aug. 25, 2021, 81 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Ledger Architecture”, U.S. Appl. No. 17/410,366, filed Aug. 24, 2021, 62 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Ledger Architecture”, U.S. Appl. No. 17/410,376, filed Aug. 24, 2021, 62 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Ledger Contract Linkage”, U.S. Appl. No. 17/412,056, filed Aug. 25, 2021, 81 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Ledger Multi-Owner Token Architecture”, U.S. Appl. No. 17/517,543, filed Nov. 2, 2021, 94 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Ledger Token Creation and Exchange”, U.S. Appl. No. 17/517,522, filed Nov. 2, 2021, 97 pages. [cited by applicant]
Padmanabhan, Prithvi Krishnan, “Database System Public Trust Token Redeem Architecture Using Wallets”, U.S. Appl. No. 17/517,541, filed Nov. 2, 2021, 96 pages. [cited by applicant]
Torres et al. A Survey on Identity Management for the Future Network, IEEE, Aug. 20, 2012, pp. 1-16. (Year: 2012). [cited by applicant]
Zhikui Chen, A Scenario for Identity Management in Daidalos, IEEE, May 1, 2012, pp. 1-8. (Year: 2007). [cited by applicant]