Decentralized tokenization technologies

Patent metadata

Field	Value
Publication number	US-12205105-B2
Application number	US-202016740283-A
Country	US
Kind code	B2
Filing date	Jan 10, 2020
Priority date	Jan 10, 2020
Publication date	Jan 21, 2025
Grant date	Jan 21, 2025

Abstract

Disclosed embodiments are related to blockchain asset token management systems, and in particular, to Multiple Decentralized Tokenization with Personal Control (MDTPC). MDTPC allows users to determine how and when asset token evaluation is performed, and also allows users to determine which token management services they wish to use to manage and store their asset token and related data. In embodiments, multiple blockchain token management services are utilized in conjunction with individual digital wallets to share token data and validate ownership of tokens. A registry service is used to ensure visibility of tokens across multiple token management services, which increases the likelihood of identifying the rightful owner of asset tokens. Other embodiments may be described and/or claimed.

First claim

The invention claimed is:

1. One or more non-transitory computer-readable storage media (NTCRSM) comprising instructions for providing blockchain services, wherein execution of the instructions is configurable to cause a computing system to:
receive, from a digital wallet operated by a user system, a validation request requesting validation of an owner of an individual token, the validation request being is cryptographically signed;
initiate, based on the cryptographically signed validation request, a search for the owner of the individual token within a set of blockchains that store tokens having a same asset type or asset class as the individual token;
cause to append a block including the validation request to at least one blockchain of the set of blockchains in response to proper validation of the block; and
send a response message to the digital wallet, wherein the response message includes ownership information at a level specified by the owner of the individual token;
wherein, to determine the set of blockchains, execution of the instructions is configurable to cause the computing system to:
determine an asset type or asset class of the individual token based on the validation request; and
identify, from a database of registered blockchains, a superset of blockchains managing tokens having the same asset type or asset class as the individual token, wherein the set of blockchains are among the identified superset of blockchains;
wherein each registered blockchain in the database are ranked according to reliability scores of each registered blockchain;
determine, as the set of blockchains, blockchains from among the identified superset of blockchains having a reliability score above a threshold reliability score; or
determine, as the set of blockchains, a predetermined number of registered blockchains from among the identified superset of blockchains having reliability scores higher than reliability scores of other registered blockchains in the database of registered blockchains;
wherein the reliability scores are used for comparison of the blockchain services to other blockchain services.

2. The one or more NTCRSM of claim 1 , wherein the reliability scores of each blockchain are based on a total number of stored tokens, a number of stored tokens as compared to other registered blockchains, a number of validation challenges that have been executed, employed token registration processes, and employed protection measures.

3. The one or more NTCRSM of claim 1 , wherein execution of the instructions is configurable to cause the computing system to:
receive a registration request from an individual blockchain;
determine a reliability score for the individual blockchain based on data items included in the registration request, the data items included in the registration request indicate one or more of token classes, subclasses, kinds, types, or categories managed by the individual blockchain, validation procedures performed by the individual blockchain to validate asset ownership, regulatory regimes or standards organizations supported by the individual blockchain, human languages supported by the individual blockchain, or programming languages supported by the individual blockchain; and
store, in the database of registered blockchains, the determined reliability score and the data items in association with an identifier of the individual blockchain.

4. A computing system to be employed as a blockchain service, the computing system comprising:
a network interface configurable to receive, from a digital wallet operated by a user system, a validation request requesting validation of an owner of an individual token; and
a processor system communicatively coupled with the network interface, the validation request being cryptographically signed, the processor system is configurable to:
initiate, based on the cryptographically signed validation request, a search for the owner of the individual token within a set of blockchains that store tokens having a same asset type or asset class as the individual token,
cause to append a block including the validation request to at least one blockchain of the set of blockchains in response to proper validation of the block, and
cause the network interface to send a response message to the digital wallet, wherein the response message includes ownership information at a level specified by the owner of the individual token;

wherein, to determine the set of blockchains, the processor system is configurable to:
determine an asset type or asset class of the individual token based on the validation request; and
identify, from a database of registered blockchains, a superset of blockchains managing tokens having the same asset type or asset class as the individual token, wherein the set of blockchains are among the identified superset of blockchains;
wherein each registered blockchain in the database are ranked according to reliability scores of each registered blockchain;
determine, as the set of blockchains, blockchains from among the identified superset of blockchains having a reliability score above a threshold reliability score; or
determine, as the set of blockchains, a predetermined number of registered blockchains from among the identified superset of blockchains having reliability scores higher than reliability scores of other registered blockchains in the database of registered blockchains;
wherein the reliability scores are used for comparison of the blockchain services to other blockchain services.

5. The computing system of claim 4 , wherein the reliability scores of each blockchain are based on a total number of stored tokens, a number of stored tokens as compared to other registered blockchains, a number of validation challenges that have been executed, employed asset token registration processes, and employed protection measures.

6. The computing system of claim 5 , wherein:
the network interface is configurable to receive a registration request from an individual blockchain; and
the processor system is configurable to:
determine a reliability score for the individual blockchain based on data items included in the registration request, the data items included in the registration request indicate one or more of asset token classes, subclasses, kinds, types, or categories managed by the blockchain, validation procedures performed by the blockchain to validate asset ownership, regulatory regimes or standards organizations supported by the blockchain, human languages supported by the blockchain, or programming languages supported by the blockchain, and
store, in the database of registered blockchains, the determined reliability score and the data items in association with an identifier of the individual blockchain.

Assignees

• Salesforce Com Inc
• Salesforce Inc

Inventors

• Harrison Daniel Thomas

Classifications

• G06Q20/401

  Transaction verification · CPC title

• G06Q2220/00

  Business processing using cryptography · CPC title

• G06F21/6218

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• G06F21/64

  Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title

• H04L9/3263

  involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823) · CPC title