Non-transferable tokens

Non-transferable tokens on the blockchain enable secure, non-interactive identity verification, addressing the challenge of native identity verification in blockchain transactions by using cryptographic methods to authenticate users without external API calls.

JP2024541125APending Publication Date: 2024-11-06AVA LABS INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024548516
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-10-19
Filing Date
2022-10-19
Publication Date
2024-11-06

AI Technical Summary

Technical Problem

Blockchain transactions require identity verification that cannot be performed natively and typically rely on external third-party API calls, making interactive identity verification challenging.

Method used

Implement non-transferable tokens (NTTs) on the blockchain for non-interactive identity verification, using cryptographic methods like signature verification and zero-knowledge proofs to authenticate users without external API calls.

Benefits of technology

NTTs provide secure, non-interactive identity verification, ensuring that only authorized users can interact with blockchain assets while maintaining privacy and preventing unauthorized access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024541125000001_ABST
    Figure 2024541125000001_ABST
Patent Text Reader

Abstract

Various aspects of the subject technology relate to systems, methods, and machine-readable media for providing digital credentials. Various aspects may include receiving a request to perform a transaction on a blockchain. Aspects may also include identifying a party originating the request. Aspects may also include selecting an issuer of a non-transferable credential stored on the blockchain. Aspects may also include requesting receipt of the non-transferable credential from the party. Aspects may include performing a credential check based on a digitally signed statement including a key pair of the non-transferable credential.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This disclosure is related to and claims priority under 35 U.S.C. § 1.119(e) from U.S. Provisional Patent Application No. 63 / 257,475, “NON-TRANSFERABLE TOKEN,” filed on October 19, 2021, the contents of which are incorporated by reference in their entirety and for all purposes.

[0002] The present disclosure relates generally to assets and transactions implemented via blockchain, and more specifically to blockchain exchanges (e.g., cryptocurrency exchanges) that require credential verification based on immobile digital credentials. [Background technology]

[0003] Blockchain transactions require identity verification to be performed in a manner native to the blockchain. That is, certain blockchain transactions should not use interactive identity verification because the blockchain cannot address identity verification that requires external third-party application programming interface (API) calls. Thus, verification credentials on the blockchain can avoid interactive identity verification. Specifically, non-transferable tokens stored on the blockchain can be used for non-interactive identity verification. [Brief description of the drawings]

[0004] The accompanying drawings, which are included to provide a further understanding, and which are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and, together with the description, serve to explain the principles of the disclosed embodiments.

[0005] [Figure 1] FIG. 1 is a block diagram of a device operating environment in which aspects of the present disclosure can be implemented. [Diagram 2]FIG. 1 is a block diagram of an example computing network of an example blockchain-based platform for generating non-transferable security credentials in accordance with certain aspects of the present disclosure. [Diagram 3] 1 is a block diagram illustrating an example computer system (e.g., representing both a client and a server) in which aspects of the subject technology may be implemented. [Figure 4A] 1 illustrates an example flow diagram for validating a non-transferable token as disclosed herein. [Figure 4B] 1 illustrates an example flow diagram for validating a non-transferable token as disclosed herein. [Figure 4C] 1 illustrates an example flow diagram for validating a non-transferable token as disclosed herein. [Diagram 5] FIG. 1 illustrates an example flow diagram for generating non-transferable blockchain security credentials via a computing platform in accordance with certain aspects of the present disclosure. [Figure 6] FIG. 1 is a block diagram illustrating an example computer system on which aspects of the present disclosure may be implemented.

[0006] In one or more implementations, not all of the components depicted in each figure may be required, and one or more implementations may include additional components not shown in the figures. The arrangement and types of components may be changed without departing from the scope of the present disclosure. Additional, different, or fewer components may be utilized within the scope of the subject disclosure. In the figures, elements having the same or similar reference numbers are associated with the same or similar attributes, unless otherwise noted. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that embodiments of the present disclosure may be practiced without some of these specific details. In other instances, well-known structures and techniques are not shown in detail so as not to obscure the present disclosure.

[0008] The detailed description set forth below describes various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be implemented. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. Thus, dimensions may be provided for certain embodiments as non-limiting examples. However, it will be apparent to those skilled in the art that the technology of the present disclosure may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

[0009] It should be understood that the present disclosure includes examples of the subject technology and does not limit the scope of the included provisions. Various aspects of the subject technology are now disclosed according to specific, but non-limiting examples. Various embodiments described in the present disclosure can be implemented in different ways and variations according to a desired application or implementation.

[0010] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that embodiments of the present disclosure may be practiced without some of the specific details. In other instances, well-known structures and techniques are not shown in detail so as not to obscure the present disclosure.

[0011] Blockchain transactions may be conducted through centralized or decentralized exchanges. It may be beneficial to verify the identity of a transaction, similar to the application of know-your-customer (KYC) checks in general financial transactions. Blockchain assets may include programs (e.g., smart contracts) for financial transactions, or other programs that use code on the blockchain for other functions. Non-transferable tokens (NTTs) may advantageously provide a mechanism for global verification of the parties to a transaction. NTTs are assets associated with addresses on the blockchain. In some embodiments, NTTs may optionally include additional credentials, as well as encrypted or encoded data payloads. Additionally, NTTs may verify the identities of the parties using non-interactive identity proofing (e.g., in smart contracts or any other asset transactions). Being non-interactive may be advantageous, as certain blockchain implementations may not be able to perform external third-party application programming interface (API) calls for the required information required to perform interactive identity proofing. NTT may be used for identity verification prior to requested execution or function invocation of a blockchain transaction (e.g., a swap function) to allow execution upon proper identity verification based on the NTT assigned to the requesting blockchain address. As an example, NTT verification may be performed by a centralized exchange or via an extended function invocation with NTT verification preconditions. In particular, blockchain transactions interacting with NTT may check the signature associated with the issuer of the NTT.

[0012] NTT may be an advantageous means to verify the identity of parties in a blockchain platform that operates in an open-source fashion (e.g., any participant in the platform can develop any application). NTT may also be used to evaluate accredited investor status associated with the blockchain platform. Blockchain transactions may include, for example, releasing funds to the appropriate party, registering a vehicle, sending notifications, issuing tickets for an event, granting contract employees access to a particular building or area within a building, verifying the identity of a third party, etc. The corresponding public blockchain is updated once the transaction is completed and cannot be changed. Therefore, it may be beneficial for security mechanisms and verifications to be implemented, such as through NTT. Assets (smart contracts, cryptocurrencies, etc.) stored on a public blockchain should limit the parties that can interact with the blockchain assets. However, transactions performed on a public blockchain may be difficult to prevent user accounts from interacting with or performing functions defined on the blockchain. Therefore, blockchain transactions may require identity proofing implemented in a manner that is native to the blockchain. In some embodiments, the blockchain platform supports deterministic execution. Thus, all nodes may be able to execute the same code with the same results. External calls are typically not allowed in blockchains because they cannot be verified to be deterministic by the blockchain system. Thus, blockchain platforms may not make external API calls. In some embodiments, blockchains may allow external API calls that include certain validity checks, as disclosed herein.

[0013] The NTTs of the present disclosure can serve as proof of identity without requiring external API calls that a blockchain cannot perform. Validity checks as disclosed herein may include signature checks, checks of data payloads, and / or zero-knowledge proofs of possession of the NTT. Specifically, a signature check of the NTT or associated with the NTT may be required before a particular user account or blockchain address is allowed to interact with a particular asset. The signature check may be based on a public-private key cryptographic (e.g., security) check or a zero-knowledge proof. As an example, an NTT holder may use a digitally signed statement (e.g., attribute-value pair) from an NTT issuer or a proof based on an NTT credential to complete a credential check without disclosing sensitive personal information. As discussed herein, an issuer of an NTT may perform a robust security check of the user identity and other relevant information before issuing the NTT to a particular public blockchain address controlled by a corresponding user whose identity has been verified.

[0014] FIG. 1 is a block diagram of a device operating environment in which aspects of the disclosure can be implemented. In the device illustrated in FIG. 1, there is no clear distinction between the server 130 and the client 110. For example, the server 130 may execute code implementing one blockchain, and any one of the client devices 110 (e.g., a mobile phone, a laptop, a palm device, or a desktop) may execute the code to qualify, at least temporarily, as a server hosting the blockchain. FIG. 1 illustrates an example network architecture 100 for providing a blockchain credential information platform for outputting filtered visual media content items, according to some embodiments. The network architecture of FIG. 1 includes one or more client devices 110 and one or more servers 130 communicatively coupled via a network 150. The network 150 may include a wired network (e.g., via optical fiber or copper wires, telephone lines, etc.) or a wireless network (e.g., a cellular network, a radio frequency (RF) network, Wi-Fi, Bluetooth, etc.). The client device 110 may be any one of a mobile device, a laptop, a desktop, a tablet (e.g., palm or pad) device, a television, a display device, and the like. The client device 110 may be controlled by a user to conduct transactions through a blockchain platform with non-interactive identity verification, such as through mechanisms described herein. The multiple client devices 110 may access the blockchain platform hosted by the server 130 through online or offline connections, such as wireless, wired, ad-hoc, mobile, satellite, and the like. The server 130 may also run, at least temporarily, on a light device or a mobile device, such as a smartphone. Each of the servers 130 may be a computing device, such as a portion of a cloud computing server, including one or more desktop computers or panels mounted on a rack, and the like.The panels may contain processing boards and also switch boards, routers, and other network devices.

[0015] FIG. 2 is a block diagram of an exemplary computing network 200 of an exemplary content platform for implementing blockchain-based identity verification according to certain aspects of the present disclosure. Identity verification may be based on a non-interactive, non-transferable token, which may be advantageous for blockchain transactions that operate effectively on one collective operating system. That is, blockchain transactions are not configured to interact with external or remote APIs, and thus cannot make external API calls by query for identity verification. FIG. 2 illustrates a client device 110 (among one or more client devices) and a server 130 (among one or more servers) of an exemplary computing network 200 for use in the network architecture of FIG. 1, according to some embodiments. Identity verification may be used to verify that the user of the client device 110 is in fact who the user represents and / or that the user is not a limited user (e.g., a citizen of a limited jurisdiction, etc.). Thus, it may be beneficial for the blockchain to verify identity based on a non-interactive type of identity tag (e.g., which may be visualized as the user of the client device 110 holding a yellow card, a red card, etc.) owned by an address corresponding to the client device 110. In other words, an identity tag can be represented as a non-transferable token (NTT) that is assigned or attached to a public address on the blockchain. The identity tag can be shown as proof of ownership to the public address on the blockchain.

[0016] Each of the one or more client devices 110 and the one or more servers 130 may access each other and other devices in the network 150 via a corresponding communication module 210a-210b. The communication modules 210a-210b may each include wireless hardware and software, such as an RF antenna, analog circuitry, digital-to-analog conversion circuitry, digital signal processing circuitry, etc. Each of the client devices 110 and the servers 130 depicted in FIGS. 1-2, respectively, may include a processor 205a-205b and a memory 220a-220b. The processor 205a of the client device 110 may be used to operate the client device 110, such as executing applications and their functions rendered on the client device 110. The processor 205b of the server 130 may be used to implement blockchain-based identity verification. In some embodiments, NTT issuance is implemented by a third party, and the server 130 processes and records NTT issuance transactions. The server 130 may correspond to a credential issuer that can act as a certified authority for generating digital credentials on the blockchain. As an example, the server 130 may mint new cards (e.g., NTTs, digital credentials) on the blockchain based on receiving blockchain asset addresses (e.g., cryptocurrency account addresses, smart contract addresses, etc.) from one or more clients. The NTTs thus created are tokens recorded as NTT records owned on the blockchain addresses entered via the corresponding clients and / or users. That is, the NTTs or credentials may be associated with, reserved by, or owned on the blockchain addresses. The blockchain addresses of the corresponding client devices 110 may store other blockchain tokens (e.g., licenses, votes, cryptocurrencies) encoded in assets.

[0017] Generally, the client device 110 and the server 130 comprise computing devices including at least a memory 220a-220b that stores instructions and a processor 205a-205b configured to execute instructions to at least partially implement one or more steps described in the methods disclosed herein. For example, the memory 220a of the client device 110 may be used to access a browser, application, or device component corresponding to a blockchain platform hosted by the server 130. The configuration of the server 130 may be defined via user / operator input, such as via an input device 230b. The client device 110 may be used by a user of the blockchain platform, such as for conducting blockchain transactions, such as via a graphical user interface (GUI) screen rendered on the client device 110. For example, the client device 110 may be coupled to at least one input device 230a and an output device 232 accessible by a user (e.g., for user input and output perceivable by the user). The input devices 230a may include a mouse, keyboard, pointer, stylus, touchscreen display, microphone, voice recognition software, graphical user interface (GUI), etc. The output devices 232 may include a display (e.g., the same touchscreen display as the input devices), speakers, alarms, etc.

[0018] Advantageously, blockchain-based identity verification may not require the user of the client device 110 to provide personal details (e.g., personal name, physical geographic address, etc.). Since NTT is a digital asset that cannot be moved or transferred by the owner of a public address on the blockchain, identity verification can be performed by an entity such as an exchange that knows that NTT cannot have been received by the user of the client device 110 from another third party. Identity verification can be used to allow a verified user / client device 110 to perform certain actions that are not available to unverified people, such as purchasing certain items or conducting certain cryptocurrency-based transactions. Additionally or alternatively, NTT can be implemented as a digital credential embedded with limited transfer capabilities such that NTT is transferable in a strictly limited manner for specific purposes (e.g., verified transitions when NTT is inherited from the owner of NTT). NTT can function similarly to a non-fungible token (NFT). In particular, NTT can be a unique token that cannot be subdivided into smaller units. That is, an NTT cannot be divided into smaller tokens and is unique such that no other instance of the same NTT can exist.

[0019] The NTT may be in a database 222 of the client device 110 that stores the token. The input device 230a may be used to access the token stored on the client to perform transactions, including token exchanges, swaps, etc. The data file 224 may be used by the credential issuer to perform blockchain-based identity verification. The data file 224 stored in memory 220a may include application settings, files, and data specific to an associated user of the client device 110. The credential identifier may correspond to a server 130 that may include a memory 220b that includes databases 226, 228 that store information for issuing NTT digital credentials and / or performing credential checks on specific blockchain addresses and / or client devices 110 for identity verification. During a requested interaction with a blockchain asset or transaction, the NTT stored on the address corresponding to the blockchain asset may be checked for accuracy to enable a swap, function call (e.g., a blockchain function), or other desired interaction with the blockchain. A swap may refer to swapping a source token with a destination token. Therefore, the credential check does not require any interactivity (e.g., no third-party API calls are required). Interaction with the owner of the NTT may only be required when the NTT is first issued and stored at the owner's address on the blockchain.

[0020] The server 130 that issues the NTT can be any suitable certified credential issuing authority, such as an authority that performs KYC, a centralized exchange, a decentralized exchange, etc. Since the developer of a particular blockchain asset can select the NTT from any suitable group of credential issuers, when another party requests to interact with the particular blockchain asset, this party can be subject to a credential check. That is, the other party must prove that they are in possession of the correct NTT before being allowed to interact with the particular blockchain asset. The credential check can include checking a digitally signed statement that includes an attribute-value pair (e.g., corresponding to a key pair such as a public-private key for encryption) to verify the NTT stored on the blockchain address generated by the other party. In this way, a signature corresponding to the public address of the credential issuing authority can be encoded on the particular blockchain asset so that it can be verified whether the NTT is issued by the correct credential issuing authority.

[0021] In particular, a blockchain asset that interacts with an NTT can check the signature associated with the issuer of the NTT to verify that the NTT is authorized and verified (e.g., based on the public key of the certificate authority / NTT issuer's public-private key and / or a public-private key held by the NTT issuer that is not shared with the signature check). In other words, the digital signature of the NTT can be checked for validity and authenticity, since a party cannot replicate the digital signature without the private key held by the NTT issuer. Because the NTT is non-interactive, a blockchain exchange can advantageously authorize actions such as depositing cryptocurrency or other tokens (e.g., blockchain transactions) based on verifying the NTT without requiring personal information of other parties. The exchange can implement rules such as extended function calls for a particular blockchain asset, so that operations cannot be performed unless the sender of the function call is from an address that stores a verified NTT.

[0022] Issuance of an NTT to a given address on the blockchain may require the implementation of rigorous security checks of the NTT applicant. For example, the credential authority may check for details such as certified legal name, social security number, taxpayer identification number, passport information, accredited investor status, etc. Additionally, the credential authority may have the power to revoke the NTT or set expiration or timeout parameters at which point the NTT will expire. In some embodiments, the NTT may be a credential issued to someone who performs an action on a website, reaches a certain level in a game, etc.

[0023] Although the above description describes certain functions being performed by the processor 205a of the client device 110 and other certain functions being performed by the processor 205b of the server 130, all of the functions described herein may be performed by the client device 110 and / or the server 130 in some other alternative division of roles. That is, the processors 205a, 205b may perform more or less functions (e.g., machine learning algorithms and / or portions of image processing) than those described above. In some embodiments, some or part of the client device 110 may be co-located with the server 130. That is, the server 130 may be located remotely from the client device 110, or both the client device 110 and the server 130 may be part of the same larger computing system, network, or architecture.

[0024] The techniques described herein may be implemented as a method performed by a physical computing device, as one or more non-transitory computer-readable storage media that store instructions that, when executed by a computing device, cause the method to be performed, or as a physical computing device specially configured with a combination of hardware and software that causes the method to be performed.

[0025] 3 is a block diagram illustrating an example computer system 300 (e.g., representing both a client and a server) on which aspects of the subject technology may be implemented. The system 300 may be configured to provide digital credentials in accordance with certain aspects of the present disclosure. In some implementations, the system 300 may include one or more computing platforms 302. The computing platform 302 may correspond to a server component of a blockchain platform, which may be similar or the same as the server computing device 130 of FIG. 3 and includes the client computing device 110 of FIG. 1. The computing platform 302 may be configured to store, determine, transmit, receive, and / or analyze blockchain transactions and / or digital credentials (e.g., NTT) to better secure the use of applications on a public blockchain system (e.g., the computer system 300). In particular, the computing platform 302 (e.g., as an exchange or lending marketplace) may provide protections and controls such that applications involving blockchain transactions may limit who a party or developer may interact with the application, for example, based on NTT identity verification of the protections and controls provided.

[0026] The computing platform 302 may be configured to communicate with one or more remote platforms 304 according to a client / server architecture, a peer-to-peer architecture, and / or other architectures. The remote platform 304 may be configured to communicate with other remote platforms via the computing platform 302 and / or according to a client / server architecture, a peer-to-peer architecture, and / or other architectures. Because transactions on a public blockchain may be limited to native applications within its own operating system, the computing platform 302 may address this limitation with non-interactive credentials for proof of identity. That is, credentials such as NTT may be stored in the blockchain of the system 300 as a non-transferable digital asset or a digital asset with limited transferability. In this manner, the remote platform 304 may interact with the computing platform 302 and its transactions upon providing digital identification information based on the corresponding. As an example, the remote platform 304 may provide a digitally signed statement, a zero-knowledge proof, a digital identification card based on NTT, etc. as identity verification before being allowed to interact with blockchain assets. The computing platform 302 , the external resources 324 , and the remote platform 304 may communicate and / or be accessible to each other via the network 150 .

[0027] The computing platform 302 may be configured with machine-readable instructions 306. The machine-readable instructions 306 may be executed by the computing platform to implement one or more instruction modules. The instruction modules may include computer program modules. The implemented instruction modules may include one or more of an operating system module 308, an identity verification module 310, an NTT issuing module 312, an issuer signature module 314, an NTT parameters module 316, and / or other instruction modules.

[0028] The operating system module 308 may run, for example, a public operating system or a shared operating system that implements a public blockchain. The operating system module 308 may host a public operating system on which various users may install applications. Such installed applications may communicate and operate in a collaborative manner, such as conducting cryptocurrency transactions, such as swapping, borrowing, lending, etc. Independently developed applications may be included in one public operating system of the operating system module 308. The blockchain may provide public addresses for storage of NTT or other digital credentials. The owner of a particular public address may not be able to move or transfer NTT stored on the corresponding public address unless a limited transfer function is available. For example, the limited transfer function may allow NTT to transfer a certain amount of instances, such as a limited number of times. The value of the limited transfer function may be set to zero as a default, such that NTT is non-transferable by default. However, as an example, an issuer of NTT may set the value to a value greater than zero to authorize transfers of a limited amount. Such transfers may be monitored by the NTT issuer to ensure that the transferor and transferee of the NTT are authenticated and identified before effecting the transfer. Thus, users may be authenticated and pay fees before making function calls or interacting with any other blockchain functionality on the network from other developers.

[0029] The identity verification module 310 may perform a signature check. The identity verification module 310 may perform a signature check based on receiving an issued and approved NTT from a party that wishes to interact with the asset on the public blockchain. As an example, a blockchain asset interacting with an NTT that is the subject of a credential check may verify that the NTT can generate a valid digitally signed statement (e.g., including data and a signature) or signature. For example, the NTT may be a credential "card" that shows the signature of the NTT issuer or is associated with the signature of the NTT issuer. The signature check may include the blockchain asset checking the public-private key with which the blockchain asset signs the submitted NTT. If the public-private key of the NTT matches the private key that the NTT issuer keeps secret and uses to generate the signature, the blockchain asset may verify that the NTT is legitimate via the signature check. The NTT credential may include attribute-value pairs (e.g., first name=Diego, last name=Maradona, location=CA, country=US) associated with the NTT issuer or user. Signature checking may be more secure in scenarios where a malicious participant improperly copies an NTT but cannot copy the NTT issuer's securely held confidential private key signature. Thus, signature checking can prevent a malicious participant from improperly issuing an NTT for itself because the malicious participant does not have the private key.

[0030] The identity verification module 310 can also verify identity via the NTT, similar to analyzing the NFT for unique identification codes and metadata. As an example, a given NTT provided by the remote platform 304 for identity verification can display a picture that can function as a digital identification card. The picture can indicate the functionality and nature of the NTT credential, such as, for example, the citizenship of the NTT holder, approved financial transactions, etc. The NTT-based verification performed by the identity verification module 310 can advantageously be non-interactive, such that the subject blockchain asset or transaction does not need to make external API calls by querying the identity provider, since the blockchain asset does not have the ability to make such external API calls. In some embodiments, the NTTs disclosed herein have associated images for user interface purposes. For example, the United States flag may be used for NTTs that refer to or identify U.S. citizens, people or businesses residing in the United States, etc. In this manner, the computing platform 302 can receive an image representation that indicates features of the NTT, such as the functionality and nature of the NTT credential. NTT could act as a contract that exists on the blockchain to verify the identity of NTT holders without revealing sensitive personal information. NTT could be held on the blockchain address of the NTT holder so that assets on the blockchain could verify that NTT's digital identity (similar to an identification tag, for example) is accurate as part of a KYC type identity / credentials check before approving any cryptocurrency financial transactions involving the blockchain.

[0031] Regardless of the method of credential check, the identity verification module 310 can maintain privacy of personal information when checking the submitted target NTT. For example, the identity verification module 310 can use zero-knowledge proofs to securely verify the holder of the target NTT without revealing sensitive personal information. A blockchain user holding the target NTT can use a client program that generates a binary value to perform a credential check of the holder. For example, the credential check can verify that the target NTT holder is over 18 years old without revealing sensitive personal information such as the holder's actual date of birth. The NTT holder or owner can also generate different types of identity verification information, such as a proof of ownership, that is different from the blockchain or blockchain-based verification information. As an example, a critical number of cryptographic signatures can be used as a threshold before a proof of ownership is generated. As an example, a quorum attestation from multiple NTT certificate authorities can be used to determine that the NTT holder truly possesses the credential (e.g., controls an address with the NTT or stores the NTT). The quorum proof may be based on an on-chain oracle configured to check the credential status at a particular moment (e.g., when the check is being performed). The on-chain oracle may connect blockchain assets to external systems to allow transactions (e.g., smart contracts) to be executed based on the quorum proof of the external systems. For example, multiple certificate authorities or NTT issuers (e.g., in N-factor authentication) may verify that the NTT holder has correctly provided authentic cryptographic information / identifiers associated with the target NTT.

[0032] In this manner, the identity verification module 310 may verify that the requester originating the request for execution of the program stored on the blockchain has been verified based on being a legitimate NTT holder. As discussed herein, the attribute / value pair may be used to indicate the NTT holder possessing a public-private key that uniquely identifies the NTT issuer that issued the NTT to the requester and to authenticate the requester. The public-private key of the pair may be made public, while the private key may be used to cryptographically sign the digitally signed statement. A special function may be invoked by the identity verification module 310 with the public-private key to determine whether the NTT issuer truly created the statement. For example, the function may return a binary "1" if the statement is true and a binary "0" if the statement is false. As an example, the blockchain asset being requested by the requester may have the address of the NTT issuer such that the requester is verified to have the NTT on the blockchain derived from the correct public / private key pair encoded on the blockchain asset. The identity verification module 310 can also be configured to set expiration dates and / or revoke issued NTTs based on settings agreed upon by the NTT issuer and the requestor. As discussed herein, the identity verification module 310 advantageously does not require any external action by the requestor and does not receive any sensitive personal information of the requestor for authentication. Thus, the requestor may be authenticated without disclosing any sensitive information, such as by using a non-interactive secure link protocol.

[0033] The NTT issuing module 312 may be used to issue non-transferable digital assets or non-transferable digital credentials such as NTT. The NTT issuing module 312 may attach NTT to a public address on the blockchain implemented by code in the operating system module 308. The owner of the public address may be restricted from moving or transferring the NTT, but a limited number of supervised transfers may be made based on a limited transfer function set to a value greater than zero. The NTT issuing module 312 may include multiple different NTT credential issuers. Multiple blockchain users may accept NTT from multiple different NTT credential issuers. That is, a user wanting an NTT credential may choose which NTT issuer to trust. That is, a user may locally select which NTT issuer he or she uses, rather than having a globally imposed NTT issuer. A blockchain-based exchange, such as a virtual currency exchange platform, may designate a specific NTT issuer and use the identity verification module 310 to perform a credential / identity check corresponding to the designated NTT issuer. In this way, cryptocurrency exchange platforms can regulate or restrict who interacts with blockchain assets on their platforms, such as restricting who can interact with cryptocurrency swap functionality based on proper ownership of authenticated NTT. Cryptocurrency exchanges can be centralized or decentralized. Each NTT provider can be part of a marketplace of certificate authorities. In this system, exchange platforms can use the expertise of NTT providers in identity verification as trusted digital credential issuers.

[0034] The issuer signature module 314 can generate a signature of the issuer of the NTT. The signature can only be replicated by the NTT issuer, such as based on a public / private key encryption system. The blockchain is encoded with the asset type and issuer of the NTT. The NTT can be identified by an asset identifier. Thus, the NTT disclosed herein ensures that only selected issuers can issue a given blockchain asset. In particular, the public-private key address pair can be verified to be correct to properly determine that the corresponding blockchain asset has the encoded public address of the NTT issuer, thereby establishing that the corresponding NTT was issued by the correct issuer. The NTT issuer can issue the NTT in an NFT format or as a fungible token (e.g., a non-transferable, non-unique ticket). For example, the NTT issuer can issue classes or categories of NTT. Each class or category of NTT can be used for a particular type of verification, such as age verification, citizenship verification, financial verification, etc. Thus, a particular class of NTT may correspond to a particular type of identity verification or credential check for a particular type of transaction call, cryptocurrency function, etc. Each class or category of NTT may include multiple non-unique instances, i.e., instances within a given class or category are indistinguishable. An owner of any of the multiple instances may be identified as an NTT credential owner within the associated credential class or category.

[0035] The NTT parameters module 316 can determine or set values ​​for NTT characteristics, such as a limited amount of confirmed NTT transfers. As an example, the NTT characteristic can be a certain number of approved transfers, such as through a limited transfer function, where a number of zero makes the associated NTT completely non-transferable, while a number greater than zero allows a limited amount of monitored transfers to be allowed. As an example, the NTT characteristic can be an expiration or revocation characteristic. The NTT parameters module 316 can set a time value for when the target NTT will expire. In other words, the NTT issuer can automatically disable the NTT as a specific time or period. The NTT parameters module 316 can also set whether the NTT issuer is authorized to revoke the target NTT in certain circumstances, such as in the case of fraud or other malicious activity, based on the terms of an agreement between the NTT holder and the NTT issuer, etc. Additionally or alternatively, the NTT issuer or certified authority / credential authority can have revocation capabilities to choose to revoke the set of keys approved by the NTT issuer at any time or under any circumstances. The NTT parameters module 316 may also determine encryption parameters, such as which NTTs are decryptable by the NTT owner. For example, the NTT issuer may issue the NTT credentials in an encrypted form on a public blockchain that is decryptable only by a key (e.g., a private key) known only by the NTT owner.

[0036] In some implementations, the computing platform 302, the remote platform 304, and / or the external resources 324 may be operatively linked via one or more electronic communications links. For example, such electronic communications links may be established, at least in part, via the network 150, such as the Internet and / or other networks. This is not intended to be limiting, and it will be understood that the scope of the present disclosure includes implementations in which the computing platform 302, the remote platform 304, and / or the external resources 324 may be operatively linked via some other communications medium.

[0037] A given remote platform 304 may include client computing devices, each of which may include one or more processors configured to execute computer program modules. The computer program modules may be configured to enable a professional or user associated with a given remote platform 304 to interface with the system 300 and / or external resources 324 and / or provide other functionality attributed herein to the remote platform 304. As a non-limiting example, a given remote platform 304 and / or a given computing platform 302 may include one or more of a server, a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a netbook, a smartphone, a game console, and / or other computing platforms. The external resources 324 may include information sources external to the system 300, external entities participating in the system 300, and / or other resources. For example, the external resources 324 may include externally designed blockchain elements and / or applications designed by a third party. In some implementations, some or all of the functionality attributed herein to the external resources 324 may be provided by resources included in the system 300.

[0038] Computing platform 302 may include electronic storage 326, a processor, such as processor 110, and / or other components. Computing platform 302 may include communication lines or ports that enable the exchange of information with a network and / or other computing platforms. The illustration of computing platform 302 in FIG. 3 is not intended to be limiting. Computing platform 302 may include multiple hardware, software, and / or firmware components that operate together to provide computing platform 302 with the functionality attributed herein. For example, computing platform 302 may be implemented by a cloud of computing platforms operating together as computing platform 302.

[0039] Electronic storage 326 may comprise non-transitory storage media that electronically store information. The electronic storage media of electronic storage 326 may include one or both of system storage provided integrally (i.e., substantially non-removable) with computing platform 302 and / or removable storage that is removably connectable to computing platform 302 via, for example, a port (e.g., USB port, Firewire port, etc.) or drive (e.g., disk drive, etc.). Electronic storage 326 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drives, floppy drives, etc.), charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drives, etc.), and / or other electronically readable storage media. Electronic storage 326 may include one or more virtual storage resources (e.g., cloud storage, virtual private networks, and / or other virtual storage resources). The electronic storage 326 may store software algorithms, information determined by the processor 110, information received from the computing platform 302, information received from the remote platform 304, and / or other information that enables the computing platform 302 to function as described herein.

[0040] The processor 110 may be configured to provide information processing capabilities in the computing platform 302. Thus, the processor 110 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and / or other mechanisms for electronically processing information. Although the processor 110 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, the processor 110 may include multiple processing units. These processing units may be physically located within the same device, or the processor 110 may represent the processing functions of multiple devices acting in concert. The processor 110 may be configured to execute the modules 308, 310, 312, 314, 316, and / or other modules. Processor 110 may be configured to execute modules 308, 310, 312, 314, 316, and / or other modules by software, hardware, firmware, any combination of software, hardware, and / or firmware, and / or other mechanisms for configuring processing power on processor 110. As used herein, the term "module" may refer to any component or set of components that performs the functions attributed to a module. This may include one or more physical processors among those executing processor-readable instructions, processor-readable instructions, circuitry, hardware, storage media, or any other component.

[0041] 3 as being implemented within a single processing unit, it should be understood that in implementations in which the processor 110 includes multiple processing units, one or more of the modules 308, 310, 312, 314, and / or 316 may be implemented remotely from the other modules. The descriptions of the functionality provided by the different modules 308, 310, 312, 314, and / or 316 described herein are for purposes of illustration and are not intended to be limiting, and any of the modules 308, 310, 312, 314, and / or 316 may provide more or less functionality than described. For example, one or more of modules 308, 310, 312, 314, and / or 316 may be eliminated, and some or all of its functionality may be provided by other of modules 308, 310, 312, 314, and / or 316. As another example, processor 110 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed to one of modules 308, 310, 312, 314, and / or 316, including:

[0042] The techniques described herein may be implemented as a method performed by a physical computing device, as one or more non-transitory computer-readable storage media that store instructions that, when performed by a computing device, cause the method to be performed, or as a physical computing device specially configured with a combination of hardware and software that causes the method to be performed.

[0043] 4A-4C illustrate example flow diagrams 400A, 400B, and 400C (collectively referred to herein as "flow diagram 400") for validating a non-transferable token as disclosed herein. In some embodiments, one or more of the steps of flow diagram 400 may be performed by a processor executing instructions from a memory of one of a server or a client device hosting a blockchain network as disclosed herein. Additionally, in some embodiments, one or more of the steps of flow diagram 400 may be performed in a different order, simultaneously, quasi-concurrently, or overlapping in time.

[0044] Flow diagram 400 begins with a request for a transaction 402 in the blockchain from a user. After validation blocks 450A, 450B, and 450C (collectively referred to hereafter as "validation block 450"), the blockchain determines in step 410 whether the transaction request is valid and passes validation block 450. If the answer is "yes," step 412 involves accepting the transaction. If the answer is "no," step 414 involves rejecting the transaction.

[0045] In the signed problem flow 400A, the confirmation block 450A receives the public key 421 (K p ) to verify the public address of the NTT owner. Step 406A includes issuing an issue to the NTT owner via the blockchain. The NTT owner uses a private key 423 (k p ) to sign the problem. Step 408A includes receiving the signature for verification before proceeding to step 410.

[0046] In transaction flow 400B (e.g., smart contract), the blockchain has already verified the public address (step 404A) and knows whether the NTT holder possesses the private key 423 (kp). The flow then proceeds to step 410.

[0047] In zero-knowledge flow 400C, for verification block 450C, the blockchain issues a challenge in step 4004C. The user provides a zero-knowledge response in step 406C, and the flow then proceeds to step 410. The zero-knowledge response is a response to the challenge that does not reveal the public-private key pair 421 / 423, but still provides an answer to the challenge that the blockchain can verify.

[0048] FIG. 5 illustrates an example flow diagram (e.g., process 500) for generating non-transferable blockchain security credentials via a computing platform according to certain aspects of the present disclosure. For purposes of explanation, the example process 500 is described herein with reference to one or more of the figures above. Furthermore, for purposes of explanation, the blocks of the example process 500 are described herein as occurring sequentially or linearly. However, multiple instances of the example process 500 may occur in parallel, overlap in time, occur approximately simultaneously, or occur in a different order than the order illustrated in the process 500. In addition, the blocks of the example process 500 need not be performed in the order shown, and / or one or more of the blocks of the example process 500 may not be performed.

[0049] In step 502, a request for execution of a program stored on the blockchain may be received. In step 504, a party originating the request may be identified. According to an embodiment, identifying the party includes determining that the party possesses a non-transferable credential and that the non-transferable credential is classified under a category of non-unique credentials. In step 506, an issuer of the non-transferable credential stored on the blockchain may be selected. According to an embodiment, selecting an issuer of the non-transferable credential includes storing the non-transferable credential as a non-movable credential attached to a public address on the blockchain. In step 508, receipt of the non-transferable credential from the party may be requested. According to an embodiment, requesting receipt of the non-transferable credential from the party includes receiving an attribute value pair indicative of a party possessing a private key corresponding to the non-transferable credential. In step 510, a credential check may be performed based on a digitally signed statement related to the ownership of the non-transferable credential. For example, the digitally signed statement includes the attribute value pair. According to an embodiment, performing the credential check includes receiving a zero-knowledge proof from the party.

[0050] According to an embodiment, the process 500 may further include determining, by an issuer of the non-transferable credential, an expiration date for the non-transferable credential. According to an embodiment, the process 500 may further include determining, by an issuer of the non-transferable credential, to effect a revocation of a key set of the non-transferable credential. According to an embodiment, the process 500 may further include capturing a quorum proof that the party possesses the non-transferable credential via a cryptographic signature. The process 500 may include generating, for the party, a proof of ownership of the non-transferable credential based on the quorum proof. According to an embodiment, the process 500 may further include determining parameters of the non-transferable credential, where the encryption of the non-transferable credential on the blockchain is decryptable by a key corresponding to the party. The process 500 may include receiving a pictorial representation indicative of characteristics of the non-transferable credential.

[0051] 6 is a block diagram illustrating an example computer system 600 in which aspects of the subject technology may be implemented. In certain aspects, computer system 600 may be implemented using hardware or a combination of software and hardware, either in a dedicated server, integrated in another entity, or distributed across multiple entities.

[0052] Computer system 600 (e.g., a server and / or a client) includes a bus 608 or other communication mechanism for communicating information, and a processor 602 coupled with the bus 608 for processing information. By way of example, computer system 600 may be implemented with one or more processors 602. Each of the one or more processors 602 may be a general purpose microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity capable of performing computations or other manipulations of information.

[0053] In addition to hardware, computer system 600 may include code that creates an execution environment for the computer programs in question, e.g., code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these, stored in associated memory 604, such as random access memory (RAM), flash memory, read only memory (ROM), programmable read only memory (PROM), erasable PROM (EPROM), registers, a hard disk, a removable disk, a CD-ROM, a DVD, or any other suitable storage device coupled to bus 608 for storing information and instructions executed by processor 602. Processor 602 and memory 604 may be supplemented by, or incorporated in, special purpose logic circuitry.

[0054] The instructions may be stored in memory 604 and implemented in one or more computer program products, i.e., encoded on a computer-readable medium for execution by computer system 600 or in one or more modules of computer program instructions encoded on a computer-readable medium for controlling the operation of computer system 600, according to any manner known to those skilled in the art, including, but not limited to, computer languages ​​such as data-oriented languages ​​(e.g., SQL, dBase), system languages ​​(e.g., C, Objective-C, C++, Assembly), architecture languages ​​(e.g., Java, NET), and application languages ​​(e.g., PHP, Ruby, Perl, Python). The instructions may also be implemented in a computer language, such as an array language, an aspect-oriented language, an assembly language, an authoring language, a command line interface language, a compiled language, a concurrent language, a curly bracket language, a dataflow language, a data structuring language, a declarative language, an esoteric language, an extensible language, a fourth generation language, a functional language, an interactive mode language, an interpretive language, an iterative language, a list-based language, a miniature language, a logic-based language, a machine language, a macro language, a metaprogramming language, a multi-paradigm language, numerical analysis, a non-English based language, an object-oriented class-based language, an object-oriented prototype-based language, an offside rule language, a procedural language, a reflective language, a rule-based language, a scripting language, a stack-based language, a synchronization language, a syntax processing language, a visual language, a worth language, and an xml-based language. The memory 604 may also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 602.

[0055] A computer program as discussed herein does not necessarily correspond to a file in a file system. A program may be stored in part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files that store one or more modules, subprograms, or portions of code). A computer program may be deployed to run on one computer or multiple computers located at one site or distributed across multiple sites and interconnected by a communications network. The processes and logic flows described herein may be implemented by one or more programmable processors executing one or more computer programs to perform functions by manipulating input data and generating output.

[0056] The computer system 600 further includes a data storage device 606, such as a magnetic or optical disk, coupled to the bus 608 for storing information and instructions. The computer system 600 may be coupled to various devices via an input / output module 610. The input / output module 610 may be any input / output module. An exemplary input / output module 610 includes a data port, such as a USB port. The input / output module 610 is configured to connect to a communication module 612. An exemplary communication module 612 includes a networking interface card, such as an Ethernet card and a modem. In certain aspects, the input / output module 610 is configured to connect to multiple devices, such as input devices 614 and / or output devices 616. An exemplary input device 614 includes a keyboard and a pointing device, such as a mouse or trackball, by which a user can provide input to the computer system 600. Other types of input devices may also be used to provide interaction with a user, such as a tactile input device, a visual input device, a voice input device, or a brain-computer interface device. For example, feedback provided to the user may be any form of sensory feedback, e.g., visual, auditory, or tactile feedback, and input from the user may be received in any form, including acoustic, speech, tactile, or brainwave input. Exemplary output devices 616 include display devices, such as LCD (liquid crystal display) monitors for displaying information to the user.

[0057] According to one aspect of the disclosure, the above-described system may be implemented using computer system 600 in response to processor 602 executing one or more sequences of one or more instructions contained in memory 604. Such instructions may be read into memory 604 from another machine-readable medium, such as data storage device 606. Execution of the sequences of instructions contained in main memory 604 causes processor 602 to perform the process steps described herein. One or more processors of a multi-processing arrangement may also be used to execute the sequences of instructions contained in memory 604. In alternative aspects, hard-wired circuitry may be used in place of or in combination with software instructions to implement various aspects of the disclosure. Thus, aspects of the disclosure are not limited to any specific combination of hardware circuitry and software.

[0058] Various aspects of the subject matter described herein may be implemented in a computing system that includes a back-end component, such as a data server, a middleware component, such as an application server, or a front-end component, such as a client computer having a graphical user interface or web browser, through which a user can interact with an implementation of the subject matter described herein, or any combination of one or more such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as a communication network. The communication network may include, for example, any one or more of a LAN, a WAN, the Internet, and the like. Furthermore, the communication network may include, for example, any one or more of the following network topologies, including, but not limited to, a bus network, a star network, a ring network, a mesh network, a star-bus network, a tree or hierarchical network, and the like. The communication module may be, for example, a modem or an Ethernet card.

[0059] Computer system 600 may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communications network. The relationship of clients and servers arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. Computer system 600 may be, for example, but not limited to, a desktop computer, a laptop computer, or a tablet computer. Computer system 600 may also be embedded in another device, such as, for example, but not limited to, a mobile phone, a PDA, a mobile audio player, a Global Positioning System (GPS) receiver, a video game console, and / or a television set-top box.

[0060] The terms "machine-readable storage medium" or "computer-readable medium" as used herein refer to any medium or media that participates in providing instructions to the processor 602 for execution. Such media may take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as the data storage device 606. Volatile media include dynamic memory, such as memory 604. Transmission media include coaxial cables, copper wire, and fiber optics, including the wires that comprise the bus 608. Common forms of machine-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs, any other optical media, punch cards, paper tape, any other physical media with a pattern of holes, RAM, PROM, EPROM, FLASH EPROM, any other memory chip or cartridge, or any other medium from which a computer can read. The machine-readable storage medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagated signal, or a combination of one or more of these.

[0061] The techniques described herein may be implemented as a method performed by a physical computing device, as one or more non-transitory computer-readable storage media that store instructions that, when executed by a computing device, cause the method to be performed, or as a physical computing device specially configured with a combination of hardware and software that causes the method to be performed.

[0062] The phrase "at least one of" preceding a series of items with the term "and" or "or" to separate any of the items, as used herein, modifies the list as a whole, not each member (i.e., each item) of the list. The phrase "at least one of" does not require the selection of at least one item; rather, the phrase allows for a meaning including at least one of any one of the items, and / or at least one item of any combination of the items, and / or at least one of each of the items. By way of example, the phrase "at least one of A, B, or C" or "at least one of A, B, or C" refers to A only, B only, or C only, any combination of A, B, and C, and / or at least one of each of A, B, and C, respectively.

[0063] To the extent that terms such as "include," "have," and the like are used in the description or claims, such terms are intended to be inclusive in the same manner as the term "comprise" is interpreted as "comprise" when used as a transitional term in a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0064] Reference to an element in the singular is not intended to mean "one and only one," but rather "one or more," unless specifically noted otherwise. All structural and functional equivalents to the elements of the various configurations described throughout this disclosure that are known or later known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the subject art. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly set forth in the description above.

[0065] Although the present specification contains many details, these should not be construed as limitations on the scope that may be claimed, but rather as descriptions of particular implementations of the subject matter. Certain features described herein in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately in multiple embodiments or in any suitable subcombination. Furthermore, although features are described above as acting in a particular combination and are initially claimed as such, in some cases, one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be subject to a subcombination or a variation of the subcombination.

[0066] Although the subject matter herein has been described in terms of certain aspects, other aspects may be implemented and are within the scope of the following claims. For example, although operations are depicted in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequence depicted, or that all illustrated operations must be performed to achieve desirable results. The acts described in the claims may be performed in a different order and still achieve desirable results. As an example, the processes depicted in the accompanying figures do not necessarily require the particular order or sequence depicted to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system components in the aspects described above should not be understood as requiring such separation in all aspects, and it should be understood that the program components and systems described may generally be integrated in a single software product or packaged in multiple software products. Other variations are within the scope of the following claims.

Claims

1. 1. A computer-implemented method, comprising: Receiving a request for execution of a transaction on a blockchain; identifying the party that originated the request; selecting an issuer of non-transferable credentials stored on the blockchain; and performing a credential check based on a digitally signed statement associated with ownership of the non-transferable credential.

2. 2. The computer-implemented method of claim 1, wherein identifying the party includes determining that the party is in possession of the non-transferable credential, and that the non-transferable credential falls under a category of non-unique credentials.

3. 2. The computer-implemented method of claim 1 , wherein selecting an issuer of a non-transferable credential comprises storing the non-transferable credential as a non-transferable credential attached to a public address on the blockchain.

4. 2. The computer-implemented method of claim 1, wherein requesting receipt of the non-transferable credential from the party includes receiving an attribute-value pair indicating the party in possession of a private key corresponding to the non-transferable credential, and the digitally signed statement includes the attribute-value pair.

5. 2. The computer-implemented method of claim 1, wherein performing a credential check includes receiving a zero-knowledge proof from the party.

6. The computer-implemented method of claim 1 , further comprising determining, by the issuer of the non-transferable credential, an expiration date for the non-transferable credential.

7. The computer-implemented method of claim 1 , further comprising: determining to enforce revocation of a key set of the non-transferable credential by the issuer of the non-transferable credential.

8. capturing, via a cryptographic signature, a quorum attestation that the parties are in possession of the non-transferable credentials; The computer-implemented method of claim 1 , further comprising: generating, for the party, proof of ownership of the non-transferable credential based on the quorum proof.

9. determining parameters of the non-transferable credential, wherein encryption of the non-transferable credential on the blockchain is decryptable by a key corresponding to the party; and receiving a graphical representation indicative of characteristics of the non-transferable credential.

10. 1. A system comprising: one or more processors; a memory, which when executed by the one or more processors, causes the one or more processors to: Receiving a request for execution of a transaction on a blockchain; identifying the party that originated the request; selecting an issuer of non-transferable credentials stored on the blockchain; determining parameters of the non-transferable credential, wherein encryption of the non-transferable credential on the blockchain is decryptable by a key corresponding to the party; requesting receipt of said non-transferable credential from said party; and performing a credential check based on a digitally signed statement associated with ownership of the non-transferable credential.

11. 11. The system of claim 10, wherein the instructions that cause the one or more processors to identify the party that originated the request cause the one or more processors to determine that the party is in possession of the non-transferable credential and that the non-transferable credential falls under a category of non-unique credentials.

12. 11. The system of claim 10, wherein the instructions that cause the one or more processors to select an issuer of a non-transferable credential cause the one or more processors to store the non-transferable credential as a non-transferable credential assigned to a public address on the blockchain.

13. 11. The system of claim 10, wherein the instructions that cause the one or more processors to request receipt of the non-transferable credential from the party that originated the request cause the one or more processors to receive an attribute-value pair indicative of the party that possesses a private key that corresponds to the non-transferable credential, and the digitally signed statement includes the attribute-value pair.

14. 11. The system of claim 10, wherein the instructions for causing the one or more processors to perform a credential check cause the one or more processors to receive a zero-knowledge proof from the party.

15. 11. The system of claim 10, wherein the instructions causing the one or more processors to perform determining the parameters include determining a limited amount of movement of the non-transferable credentials that is permitted.

16. 11. The system of claim 10, further comprising a stored sequence of instructions that, when executed by the one or more processors, cause the one or more processors to perform determining an expiration date for the non-transferable credential by the issuer of the non-transferable credential.

17. 11. The system of claim 10, further comprising a stored sequence of instructions that, when executed by the one or more processors, cause the one or more processors to determine whether to perform revocation of a key set of the non-transferable credential by the issuer of the non-transferable credential.

18. When executed by the one or more processors, the one or more processors capturing via a cryptographic signature a quorum proof that said party possesses said non-transferable credential; 11. The system of claim 10, further comprising: generating, for the party, proof of ownership of the non-transferable credential based on the quorum proof.

19. When executed by the one or more processors, the one or more processors determining parameters of the non-transferable credential, wherein encryption of the non-transferable credential on the blockchain is decryptable by a key corresponding to the party; 11. The system of claim 10, further comprising a stored sequence of instructions causing the system to: receive a graphical representation indicative of characteristics of the non-transferable credential.

20. 1. A non-transitory computer-readable storage medium that, when executed by one or more processors, causes the one or more processors to: Receiving a request to execute a transaction on a blockchain; identifying the party that originated the request; selecting an issuer of non-transferable credentials stored on the blockchain; determining transferable parameters of said non-transferable credentials; requesting receipt of said non-transferable credential from said party; receiving a pictorial representation indicative of characteristics of the non-transferable credential; and performing a credential check based on a digitally signed statement associated with ownership of the non-transferable credential.

Citation Information

Patent Citations

  • Systems and methods for realizing block chain-based multifactor personal identity verification

    JP2019057271A

  • Non-transferable anonymous credentials

    US7222362B1

  • Systems and methods for blockchain based identity verification and transaction processing

    WO2020014282A1