Verification method and verification computer system having an nft-generating device and a verification device

EP4463977A1Pending Publication Date: 2024-11-20ETO GRP TECH GMBH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
EP2022838814
Authority / Receiving Office
EP · EP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-01-10
Filing Date
2022-12-20
Publication Date
2024-11-20

AI Technical Summary

Technical Problem

Current technologies lack effective solutions for digital verification and data security in real-world applications beyond the art and gaming markets, where non-fungible tokens (NFTs) are underutilized for authenticating public keys in asymmetric cryptosystems.

Method used

A verification method utilizing NFTs created with a public key or its deterministic derivative, stored on a distributed ledger like blockchain, allows for secure and simple authentication of public keys, potentially replacing traditional certification authorities and public key infrastructures.

Benefits of technology

This method enables reliable and secure verification of public key authenticity, ensuring high security and trust through decentralized ownership verification and smart contracts, facilitating secure communication and data management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 1.1
    Figure 1.1
Patent Text Reader

Abstract

The invention relates to a verification method, in particular a computer-implemented verification method, in an asymmetric cryptosystem having at least one entity (20) to which a public key (10) and a private key (12) are assigned. According to the invention, in at least one method step (14), at least one non-fungible token (NFT, 18) is generated (minting) which contains a copy of the public key (16) or a deterministic derivation of the public key (10) and which is stored in a distributed ledger, such as a blockchain, tangle or hashgraph, of a distributed ledger technology (DLT, 44).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Verification method and verification computer system with an NFT creation device and a verification device

[0002] State of the art

[0003] The invention relates to a verification method according to the preamble of claim 1, a verification computer system according to claim 19, an NFT creation device according to claim 21 and a verification device according to claim 22.

[0004] Although non-fungible tokens (NFTs) are already enjoying great popularity in the crypto community, real-world technical applications outside of the art market or the computer game market are still rare.

[0005] The object of the invention is, in particular, to provide a generic method with advantageous properties regarding digital verification and / or data security. This object is achieved according to the invention by the features of patent claims 1, 19, 21, and 22, while advantageous embodiments and further developments of the invention can be found in the subclaims.

[0006] Advantages of the invention

[0007] The invention is based on a verification method, in particular a computer-implemented verification method, in an asymmetric cryptosystem with at least one entity to which a public key and a private key are assigned. It is proposed that in at least one method step at least one non-fungible token (NFT) is created, which contains a copy of the public key or a deterministic derivative of the public key and which is stored in a distributed ledger, such as a blockchain, a tangle or a hashgraph, a distributed ledger technology (DLT). This advantageously enables simple and at the same time secure verification of the authenticity of the public key. Advantageously, for example, a separate certification authority can be replaced. In particular, the verification method is intended for verifying the authenticity of the public key.“Intended” should be understood in particular to mean specially programmed, designed and / or equipped. The fact that an object is intended for a specific function should be understood in particular to mean that the object fulfills and / or executes this specific function in at least one application and / or operating state. In particular, the verification method is carried out with the aid of computers, in particular with the aid of operating programs stored in the computer memories and executed by the computer processors. An “asymmetric cryptosystem” should be understood in particular to mean a public-key encryption and / or authentication system. In particular, in the asymmetric cryptosystem, each participant has at least one private key unknown to all other participants and one public key that has been made public.The public key enables anyone to encrypt data for the owner of the private key or to authenticate the owner of the private key. In particular, the public key is publicly available / accessible to everyone. The private key enables its owner to decrypt data encrypted with the associated public key or to authenticate themselves. The proposed verification method is advantageously suitable for replacing public key infrastructures (PKIs) based on digital certificates and certification authorities. A non-fungible token (NFT), sometimes also called a non-interchangeable token, is understood in particular to be a digitized form of a data set / asset, preferably based on a DLT, such as a blockchain or a Tangle, or the like, and which, in particular, is not one-to-one interchangeable, non-divisible, and unique.NFTs are distributable and / or transferable at least within the DLT. It is also conceivable that DLTs can also bridge the boundaries between different DLTs and thus be distributable and / or transferable between different DLTs. In public DLTs, the NFTs stored thereon and preferably transactions associated with the NFT can be viewed by anyone. An NFT can, in particular, be linked to at least one physical or digital object. It is conceivable that an NFT is linked to multiple physical or digital objects (e.g., multiple public keys) and / or that an identical physical or digital object (e.g., a public key) is assigned to more than one NFT. In particular, the NFT created in the method step is linked at least to the digital object "public key." For this purpose, the NFT comprises the public key or its deterministic derivative directly or in the form of a hash value of the public key or the like.Once the creation of the NFT containing the public key or its deterministic derivative has been confirmed by the consensus protocol of the respective DLT, the assignment to the NFT is immutable and permanent (until a possible dissolution or destruction by an owner of the NFT) recorded in the DLT. The creation of an NFT, especially an NFT linked to an object, is often referred to as "minting" the NFT. In particular, the NFT is created by the entity itself, for example, using a computer system of the entity that is connected to the DLT. Destruction of an NFT or making it impossible for anyone to own the NFT is often referred to as "burning" the NFT. Triggering an NFT, i.e., dissolving the connection between the NFT and the object assigned to it, is often referred to as "redeeming" the NFT.In particular, the NFT can be created using the smallest possible unit of a DLT token. The DLT token represents an underlying asset. For some applications, the underlying asset can also be increased, for example, by including the actual value of the physical or digital object at the time of creation, etc.

[0008] NFTs are preferably assigned to at least one, preferably exactly one, owner address within the DLT. This owner address assigned to the NFT can change when the NFT is sent, traded, or exchanged. The DLT is preferably designed as a decentralized DLT. Alternatively, the DLT can also be only partially decentralized (distributed across a few nodes) or centralized. The DLT is preferably designed as a publicly accessible DLT. Alternatively, it is conceivable that the DLT has at least one access restriction. Preferably, the NFT is publicly accessible via the DLT. Preferably, the owner address assigned to the NFT is publicly accessible via the DLT. Preferably, the assignment of the NFT to the owner address is publicly accessible via the DLT.A "deterministic derivative" of an object is understood to mean, in particular, a data set / character string generated by the object and uniquely assignable to the object. For example, the deterministic derivative of the object is embodied as a hash value of a digital object or a digital image of a physical object. Alternatively, the deterministic derivative can be embodied as a self-signed public key, etc.

[0009] It is further proposed that the authenticity of the public key be confirmed by the NFT being in the possession of at least one authentication entity other than the entity. This advantageously enables authenticity verification, particularly of the public key, in a simple and secure manner. In particular, the authenticity of the public key is confirmed by the NFT comprising the public key or its deterministic derivative being assigned within the DLT to a DLT owner address of the authentication entity. The authentication entity is preferably designed as a trustworthy entity. In particular, the entity's public key is freely available / visible.In particular, the authenticity of the public key is confirmed (match present) or refuted (match not present) by verifying a match between the publicly accessible public key and the content of the publicly visible NFT held by the legitimizing entity.

[0010] It is also proposed that the NFT be offered for transmission to at least one authentication entity different from the entity, for example, on a digital NFT marketplace, directly or in a private, predefined circle. This advantageously ensures simple implementation of the verification process. In particular, the NFT created by the entity itself is offered to the authentication entity via one of the proposed methods. In particular, the authentication entity or other entities can send at least one transaction request to the entity (directly or via the digital NFT marketplace) requesting the entity to transmit the NFT.

[0011] Furthermore, it is proposed that the legitimizing entity, which is different from the entity, requests transmission of the NFT, whereupon the NFT, preferably the requested NFT, is sent from a DLT owner address of the entity to a DLT owner address of the legitimizing entity, which is different from the entity. This can advantageously ensure a simple implementation of the verification process. Advantageously, a simple, public verification of the public key can be enabled. After the NFT has been transmitted to the DLT owner address of the legitimizing entity, anyone can easily check whether the entity's public key is registered there using the NFT by querying the DLT owner address of the legitimizing entity.whether the NFT containing the public key or its derivative is in the possession of the authentication entity, and thus, depending on its trust in the authentication entity, determine whether the public key is trustworthy. If at least one NFT received by the authentication entity, preferably each NFT received by the authentication entity, is checked in at least one verification step, particularly performed on the authentication entity's side, to determine whether the NFT was previously requested by the authentication entity. If the verification result is negative, the NFT is immediately redeemed or burned, false authentications can be advantageously prevented. This advantageously achieves a high level of verification security and / or a high level of verification trust.In particular, a negative test result determined during the test means that the NFT was sent to the legitimizing entity without being asked to do so. In particular, a positive test result determined during the test means that the NFT was sent to the legitimizing entity after a prior request by the legitimizing entity. When the NFT is redeemed (redeemed), all metadata, links, and relationships of the NFT with the physical or digital object (here: the public key) are detached / removed from the NFT. The NFT is thus converted back into the "empty" DLT token that it was before minting. To carry out the redeeming process, the NFT is sent back to a DLT address of the NFT creator (e.g., a contract address of a smart contract). In particular, the "empty" DLT token is reusable after redeeming, so it can, for example,a new NFT containing an additional public key can be created from it. During burning, the NFT is sent to a DLT "burn address" (e.g., OxOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOdEaD or 0x00000000000000000000000000000000000000000000 for ERC20 tokens, ERC721 tokens, ERC1155 tokens, or BEP-20 tokens). No one has access to this "burn address" and no one can ever have access to it, so NFTs sent there are essentially destroyed. In particular, the NFT sent to the "burn address" and its underlying DLT token are removed from circulation and can no longer be reused. This means, for example, that a new NFT containing an additional public key cannot be created from it. Often, the total number of DLT tokens is limited, so burning increases the rarity of the DLT tokens.

[0012] Additionally, it is proposed that the public key be verified in at least one verification step by determining ownership of the NFT(s) of the public key. This advantageously enables simple, reliable, and secure verification of the public key, in particular by every DLT participant. In particular, ownership of an NFT can be determined by sending a transaction to a smart contract related to the NFT, e.g., to the smart contract through which the NFT was created, or by querying DLT nodes. The transaction or query preferably results in the output of a DLT owner address that currently owns the NFT, in particular the DLT token underlying the NFT, or that currently has control over the NFT, in particular the DLT token underlying the NFT.In this way, ownership of the NFT can be reliably and easily determined by every DLT participant. In particular, the authentication entity is assigned to the owner's address. In particular, only the authentication entity has control over the owner's address and, preferably, over all NFTs in the owner's address's possession. If the authentication entity is trustworthy, e.g., embodied by an official body such as a government agency or by a private trustworthy body such as an IT security company, a KYC (Know Your Customer) provider, etc., it can be concluded that the public key is authentic from the fact that this body is in possession of the NFT with the public key or the deterministic derivative of the public key. Communication based on the use of the public key can thus be trusted.As much trust can be assigned to the NFT as to the entity in possession of the associated NFT. By destroying or redeeming the NFT by the authentication entity, the verifiability of the respective public keys can be terminated. This can be the case, for example, if a paid period or the validity of the public key has expired, if the validity of the linked object has expired (e.g., the expiration date of a passport verified by an authority has been reached), etc.

[0013] It is advantageously proposed that the NFT be made available for verification of ownership, particularly within the DLT, for example, on a digital NFT marketplace, directly or in a private, predefined circle. This advantageously enables simple and reliable verification of the public key. In particular, the appropriate NFT for the respective public key can be determined / provided in this way. The digital marketplace can be publicly accessible or access-restricted, e.g., by a central authority that verifies who is permitted to offer and / or access which type of NFT.

[0014] It is also proposed that, in order for the legitimizing entity to revoke the entity's legitimacy, the NFT be sent to the DLT's burn address or to a DLT address of a DLT developer / administrator, in particular to the DLT address of the smart contract originally used to create the NFT. This can advantageously enable a simple and / or publicly traceable revocation of the legitimacy.

[0015] Alternatively, to revoke the legitimacy of the entity, the NFT can also be sent to a different DLT address than the legitimacy entity's DLT address. The crucial factor here is that the NFT is then verifiably no longer in the possession of the legitimacy entity.

[0016] It is proposed that at least the creation (minting) of the NFT, at least one transaction of the NFT, at least one verification of the NFT, at least one triggering of the NFT (redeeming), and / or at least one destruction of the NFT (burning) be implemented by executing one or more DLT smart contracts or by directly creating it as a native DLT asset. A "smart contract" is understood in particular to be a contract based on a DLT that includes at least one, preferably a plurality of if / then conditions as pre-programmed functions that can be called. For this purpose, "if" conditions are provided to the smart contract as input, and the smart contract reacts by issuing / non-issuing "then" results.

[0017] In particular, the smart contract is implemented as software code on top of the DLT. In particular, the smart contract is immutable due to its implementation on the DLT. In particular, a DLT address in the DLT is assigned to the smart contract. In particular, the smart contract can be invoked by sending transactions to the smart contract's DLT address. In particular, executing the smart contract requires the payment of a fee, which is added in the form of DLT tokens to the transactions invoking the smart contract. In particular, the smart contract is executed after being invoked by more than one DLT node ("quorum"), with the result only being output if all members of the quorum reach the same result.Preferably, the smart contract used at least to create the NFT comprises at least one of the following functions, preferably at least the following functions: mintToken (for creating an NFT from the underlying DLT token and sending this NFT to a DLT address), tokenOwner (for issuing the DLT owner address of an NFT), tokenBalance (for issuing all NFTs of a specific DLT owner address), burnToken (for destroying an NFT, i.e., for sending the NFT to the burn address), redeemToken (for triggering the NFT, i.e., for breaking the link to the physical or digital object and sending the DLT token underlying the NFT back to the DLT address of the smart contract), tokenTransfer (for sending the NFT to another DLT address), and approveTransfer (for accepting a requested transfer of the NFT to a DLT address). In addition, the creation of the NFT using the smart contract will be described below as an example.In particular, the process of creating an NFT according to the invention is also known in technical terms as minting. When minting an NFT linked to a physical or digital object, a digital asset of the DLT, e.g. a DLT token, is converted into the NFT according to the invention by adding metadata (here: public key or its deterministic derivative) to the DLT token. For this purpose, the metadata, in particular, together with information about which functions of the smart contract are to be called with which parameters, are sent to the DLT address of the smart contract. The smart contract then preferably carries out the following steps: a) Verifying the existence of the functions to be called in the smart contract according to the received information, if necessary with a plausibility check of the parameters, b) Verifying whether sufficient fees in the form of DLT tokens have been received, if necessary.Excess fees are assigned to the NFT as value, c) preparing a transaction to a DLT address of the DLT network, in particular to the DLT address from which the smart contract was invoked, whereby the transaction includes the NFT linked to the metadata, and d) executing the NFT transaction. In particular, the DLT address to which the transaction was directed is then the DLT owner address of the newly minted NFT. The DLT owner address is assigned to the entity that holds the key associated with the DLT address (usually a public key of the DLT itself, e.g.

[0018] 0xEfcA6C6981 a448388780cbfefA72dc77C3F73e6b). This enables the entity to send all DLT tokens, NFTs, etc. associated with the DLT owner address within the DLT.

[0019] If the verification step is performed by a web application, such as a web browser, a secure Internet connection can advantageously be established, in particular without the use of certificates. In particular, a web server creates a public key-private key pair for secure communication. In particular, the web server generates at least one NFT in the verification step, preferably by means of the smart contract, which contains the created public key or its deterministic derivative. An authentication entity can now take possession of / purchase the NFT, in particular after the authenticity of the web server has been verified, for example by means of a challenge-response authentication. If the web server now uses the web application, e.g.If the NFT is accessed via the web browser, the web application can check whether an NFT of the public key offered by the web server is in the possession of a trusted authentication entity. To do this, the web server can, for example, retrieve a list of trusted authentication entities and also search the DLT addresses of these authentication entities for the NFT of the public key offered by the web server. If the NFT is found at a trusted authentication entity, the web application can trust the web server and, for example, initiate end-to-end encrypted communication. Advantageously, the authentication entity does not even have to be online or accessible for this process to be successful after it has taken possession of the NFT, especially since all the necessary information is then already available in the DLT.

[0020] Alternatively or additionally, it is proposed that the entity be embodied as a product and that the verification step be performed by a user, purchaser, or provider of the product. This can advantageously achieve a high level of forgery security. The products can then be equipped with public key-private key pairs. The products can then create and / or publish NFTs, each containing the created public key or its deterministic derivative. The products can either have access to the DLT themselves or, in a production step, e.g., during an end-of-line verification, trigger an NFT creation by an external device, e.g., the verification device of the end-of-line verification after successful verification. An authentication entity can now take possession of or purchase the NFT.The user, acquirer, or provider can now verify the authenticity of the product by first performing a simple challenge-response authentication using the known public key supposedly associated with the product to verify whether the private key is actually in the product's possession. If this is successful, the user, acquirer, or provider can then verify whether an NFT of the public key associated with the product is in the possession of a trusted authentication entity. This can be done in a similar way to the web server. If the NFT is found with a trusted authentication entity, the user, acquirer, or provider can assume the authenticity of their product. The same procedure can also be used to secure data communication with the product, if the product is capable of such communication.

[0021] If the legitimizing entity is a central (online) certification authority, especially a digital one, certification can be advantageously replaced and simplified by certificates. Advantageously, an interruption of the online connection of the (online) certification authority does not result in a failure of the (online) certification authority's verification capacity.

[0022] Alternatively or additionally, if the entity is embodied as a product and the authentication entity is a manufacturer of the product, verification of original parts can advantageously be enabled. In particular, the proposed method allows the product manufacturer to include additional product properties in the NFT, such as year of manufacture, serial number, etc., which can then be read and verified during the verification process.

[0023] Alternatively or additionally, if the entity is embodied as a product and the legitimizing entity is a product testing center or a repair and / or maintenance center for the product, it can advantageously be verified whether the product, e.g., the spare part or similar, was successfully tested or whether / when the product was properly repaired and / or maintained. Alternatively or additionally, if the entity is a person and the legitimizing entity is an entity authorized to verify the person's identity, such as a government agency or a KYC provider, the person's identity can advantageously be verified securely and reliably. Persons who are assigned, for example, a Decentralized Identifier (DID) or another digital identity (e.g., via an electronic ID card or an electronic passport) can create or have created NFTs according to the invention.This can be done, for example, with the help of an authority / KYC provider. The legitimizing entity, e.g., the authority or the KYC provider, can now verify a person's identity, e.g., on-site, and take possession of / purchase the person's NFT. If the person's identity is to be verified, the DLT owner address of the legitimizing entity, e.g., the authority or the KYC provider, can be searched for suitable NFTs, similar to the procedures described above. The presence of the NFT at the legitimizing entity verifies the person's identity. The authenticity of the public key to be verified can also be confirmed in advance by means of a challenge-response authentication or similar of the object storing the DID or digital identity (e.g., passport, driver's license, residence permit, etc.). It is also conceivable that the legitimizing entity, e.g.,the authority or the KYC provider packs zero-knowledge proofs along with the public keys into the NFTs, creates them themselves and takes immediate possession of them.

[0024] Furthermore, it is proposed that the NFT created in the method step, in addition to the public key, or in particular instead of the public key, contains at least one confirmation, for example a guarantee certificate, insurance confirmation, a user authorization certificate, or their deterministic derivative and / or at least one expiration date, for example a warranty expiration date, an insurance period, a duration of a user authorization, which is assigned to the entity or an agreement associated with the entity. This advantageously makes it possible for anyone to read a property of the entity in an unforgeable manner. It is conceivable, for example, that a manufacturer of the product creates an NFT that includes the public key associated with the product and the confirmation or its deterministic derivative and / or the expiration date. This NFT can then be taken into possession by an end user of the product, i.e.sent to a DLT address of the end user. In this case, the end user forms an alternative authentication entity. The manufacturer can then advantageously determine whether the respective end user actually owns the product by querying the end user's DLT address. Such verified ownership of the product can then advantageously be linked to the provision of a service, such as a (free) repair, maintenance, warranty, or other service. The additional expiration date makes it advantageous to publicly and unalterably view and verify a time limit on the guaranteed service.

[0025] In particular, it is also conceivable that a third party, such as an insurance company, takes possession of an NFT containing at least the public key of a product or person, whereby possession confirms the existence of insurance for that person or product. As long as the NFT is in the possession of the third party (the insurance company), the insurance is active, which can be viewed by anyone in an unforgeable, simple, and secure manner by querying the DLT owner address of the third party (the insurance company). As soon as the third party (the insurance company) sends the NFT to another address, either the insurance company changes (shipping to another third party) or the insurance coverage expires (redemption or destruction of the NFT). In particular, the NFT can include the insurance terms and conditions, which are thus advantageously tamper-evident.

[0026] It is also proposed that the entity be a person with a Digital ID and / or Decentralized Identifier (DID) comprising a private key / public key pair, and that the NFT created / mined in the process step additionally contains at least one form of identification of the person, for example, an identification document, a driver's license, a residence permit, etc., or its deterministic derivative. This can advantageously enable simple, secure, and / or unforgeable verification of personal identities. In particular, the authenticity of the person's respective identification can be confirmed through the ownership of the NFT by the authentication entity, which in this case is embodied as an authority.

[0027] Furthermore, it is proposed that the NFT created / mined in the procedural step additionally contain at least one confirmation of ownership, for example, a training diploma, a stock portfolio, a certificate of ownership for things or real estate, etc., or their deterministic derivative. This advantageously makes it possible to easily, securely, and / or incorruptibly verify the ownership of the confirmation of ownership to a person. In particular, the ownership of the NFT by the respective legitimizing entity can confirm the authenticity of the respective confirmation of ownership of a person's property. For example, if the land registry contains an NFT assigned to a person P, which also includes a confirmation of ownership of a property G, the ownership relationship can advantageously be verified for everyone by querying the DLT owner address of the land registry.In particular, in this and other cases, to enable verification by a third party, knowledge of an NFT identifier, e.g. a running mint number of the NFT, may be required by the third party.

[0028] Furthermore, a verification computer system, which is provided in particular for carrying out a verification method according to one of the preceding claims, is provided with at least one NFT creation device, which is provided for creating / minting an NFT containing a copy of a public key of an asymmetric cryptosystem assigned to an entity or a deterministic derivative of the public key, and which is provided for storing the created NFT in a distributed ledger, such as a blockchain, a tangle, or a hashgraph, of a distributed ledger technology (DLT). This advantageously enables simple and at the same time secure verification of the authenticity of the public key. In particular, the verification computer system comprises at least one server or a plurality of network-linked servers.In particular, the DLT is distributed across a plurality of preferably public and / or decentralized nodes, each node comprising at least its own computer with at least one processor and a memory. The NFT creation device can be designed, for example, as a mobile computer, e.g., a person's smartphone, or as a stationary computer system, e.g., a government server, a company server, or a server in a product production line. The NFT creation device has, in particular, a processor, a memory, and a computer program (pre-installed) stored in the memory, which is specifically designed to carry out at least the method step of the previously described verification method in which the NFT is created.

[0029] It is also proposed that the verification computer system comprise a verification device, particularly one designed separately from the NFT creation device, which is intended to verify the authenticity of the public key by querying and evaluating the ownership of the NFT. This advantageously enables simple yet secure verification of the authenticity of the public key. The verification device can be designed, for example, as a mobile computer, e.g., a person's smartphone, or as a stationary computer system, e.g., a government server, a personal computer, a company server, or a server in a product production line.The verification device comprises, in particular, a processor, a memory, and a (pre-installed) computer program stored in the memory, which is specifically designed to carry out at least the verification step in which the ownership of the NFT is determined. Furthermore, it is proposed that the verification computer system comprise an authentication device, which is designed separately from the NFT creation device and the verification device, and which is intended to take possession of / acquire the NFT via a publicly visible authentication address of the DLT that can be assigned to a authentication entity. This advantageously enables simple and secure verification of the authenticity of the public key. The authentication device can, for example, be implemented as a mobile computer, e.g., a person's smartphone, or as a stationary computer system, e.g.,a government server, a personal computer, a corporate server, or a server in a product production line. The authentication device comprises, in particular, a processor, a memory, and a computer program (pre-installed) stored in the memory, which is specifically designed to at least request the NFT in the DLT and to control and manage a DLT owner address to which the NFTs are sent, or to enable control and / or management of the NFT for an operator of the authentication device. Preferably, the computer program (pre-installed) stored in the memory of the authentication device is intended to perform the verification step, preferably in an automated manner. Furthermore, the NFT creation device and the verification device are proposed.

[0030] The verification method according to the invention and the verification computer system according to the invention are not intended to be limited to the application and embodiment described above. In particular, the verification method according to the invention and the verification computer system according to the invention may have a number of individual elements, components, and units that differs from the number stated herein to fulfill a functionality described herein. Drawings

[0031] Further advantages will become apparent from the following description of the drawings. The drawings illustrate an exemplary embodiment of the invention. The drawings, the description, and the claims contain numerous features in combination. Those skilled in the art will also expediently consider the features individually and combine them into useful further combinations.

[0032] They show:

[0033] Fig. 1 is a schematic representation of a verification computer system which is intended to carry out a computer-implemented verification method in an asymmetric cryptosystem and

[0034] Fig. 2 is a schematic flow diagram of the computer-implemented verification method in the asymmetric cryptosystem.

[0035] Description of the embodiment

[0036] Figure 1 schematically shows an exemplary verification computer system 32, which is intended to carry out a verification method. The verification computer system 32 has an NFT creation device 34. The NFT creation device 34 is intended to create a non-fungible token (NFT 18) for an entity 20. The entity 20 is assigned a public key 10 of an asymmetric cryptosystem. The entity 20 can be embodied as a physical or digital object (product) or as a person. The public key 10 is publicly accessible / viewable. The entity 20 is assigned a private key 12 of the asymmetric cryptosystem. The private key 12 and the public key 10 of the entity 20 form a public key-private key pair of the asymmetric cryptosystem. The NFT creation device 34 can view / determine the public key 10 of the entity 20.The NFT creation device 34 is intended to verify the affiliation of the public key 10 to the entity 20 before creating the NFT 18, e.g., through challenge-response authentication. The NFT 18 created by the NFT creation device 34 contains a copy of the public key 16 of the asymmetric cryptosystem assigned to the entity 20. Alternatively, the NFT 18 can also contain a deterministic derivative of the public key 10 instead of the copy of the public key 16. The NFT creation device 34 can be a (mobile or stationary) computer of the entity 20 or a computer of another entity different from the entity 20, such as a government agency. The NFT creation device 34 is intended to store the created NFT 18 in a distributed ledger, such as a blockchain, a tangle, or a hashgraph, a distributed ledger technology (DLT) 44. The DLT 44 is designed as a decentralized DLT.Alternatively, centralized or partially centralized DLTs are also conceivable. The NFT 18 is offered via the DLT 44 for transmission to various authentication entities 22, which are different from the entity 20. The authentication entity 22 can be configured, among other things, as a central certification authority, a public authority, a KYC provider, a product manufacturer, a product testing center, a repair center, a maintenance center, or an insurer. The NFT 18 is made publicly available via the DLT 44 for verification of ownership. In addition to the public key 10, the NFT 18 can also contain further information or the like, e.g., a confirmation 28, an expiration date 30, a person's authentication 42, a person's confirmation of ownership 46, or their respective deterministic derivatives.

[0037] The verification computer system 32 has an authentication device 38. The authentication device 38 is configured separately from the NFT creation device 34. The authentication device 38 is designed to acquire / take possession of the NFT 18 via a publicly visible authentication address of the DLT 44 (DLT address of the authentication entity 22) that can be assigned to an authentication entity 22. The authentication device 38 can view / determine the public key 10 of the entity 20. The authentication device 38 is designed to verify the authenticity of the public key 10 by querying and evaluating the ownership of the NFT 18. The legitimation device 38 is intended to verify the affiliation of the public key 10 to the entity 20 before taking possession of the NFT 18, e.g. by a challenge-response authentication.The authentication device 38 makes the NFT 18 publicly available via the DLT 44 for verification of ownership. The authentication device 38 is intended to enable the authentication entity 22 to request a transmission of the NFT 18. The authentication device 38 is intended to enable the authentication entity 22 to receive / take possession of the requested NFT 18. A DLT owner address of the authentication entity 22 is assigned to the authentication entity 22 / the authentication device 38. The legitimizing device 38 is provided to check each NFT 18 received from the legitimizing entity 22 to determine whether the NFT 18 was previously requested by the legitimizing entity 22 / by the legitimizing device 38, wherein in the event of a negative check result, the NFT 18 is immediately redeemed (redeemed) or destroyed (burned).Alternatively, the NFT 18 can also be returned to a DLT sender address if the verification result is negative. The authentication device 22 is designed to destroy the NFT 18, i.e., send it to a burn address of the DLT 44, or trigger it, i.e., send it to a DLT address of a developer / administrator of the DLT 44, in particular to a DLT address of the smart contract originally used to create the NFT 18, in order to revoke the authentication of the entity 20 by the authentication entity 22.

[0038] The verification computer system 32 has a verification device 36. The verification device 36 is configured separately from the NFT creation device 34. The verification device 36 is configured separately from the authentication device 38. The verification device 36 can view / determine the public key 10 of the entity 20. The verification device 36 is provided to verify the authenticity of the public key 10 by querying and evaluating the ownership of the NFT 18. The verification device 36 is provided to verify the affiliation of the public key 10 to the entity 20 before verifying the authenticity of the public key 10 by querying and evaluating the ownership of the NFT 18, e.g., through challenge-response authentication.The verification device 36 can be assigned to any other entity 40 other than the entity 20, for example a private individual, a company or a public authority.

[0039] Fig. 2 shows a schematic flow diagram of a computer-implemented verification method in an asymmetric cryptosystem with at least the entity 20, to which the public key 10 and the private key 12 are assigned. In at least one method step 14, the NFT 18 is created (minting), which contains the copy of the public key 16 or the deterministic derivative of the public key 10. In method step 14, the NFT 18 is stored in the distributed ledger, such as a blockchain, a tangle, or a hashgraph, of the DLT 44. The NFT 18 is created by executing at least one smart contract of the DLT 44. Alternatively, the NFT 18 can be created as a native asset of the DLT 44.The NFT 18 created in method step 14 is sent after creation in a further method step 48 by the smart contract to a DLT address, preferably to the DLT address of the device that initiated the NFT creation, e.g. the NFT creation device 34 of the entity 20 or an NFT creation device 34 of an authority.

[0040] The NFT 18 created in method step 14 can comprise, in addition to the public key 10, at least one confirmation 28 or its deterministic derivative, which is assigned to the entity 20 or an agreement associated with the entity 20. The confirmation 28 can be, for example, a guarantee certificate, insurance confirmation, a usage permit certificate, or the like. The NFT 18 created in method step 14 can comprise, in addition to the public key 10, at least one expiration date 30, which is assigned to the entity 20 or an agreement associated with the entity 20. The expiration date 30 can be, for example, a guarantee expiration date, an insurance period, a duration of a usage permit, or the like.

[0041] If the entity 20 is a person with a digital ID and / or decentralized identifier (DID) comprising a private key-public key pair, the NFT 18 created in method step 14 can contain, in addition to the public key 10, at least one authentication 42 of the person. The authentication 42 of the person can be, for example, an identity document, a driver's license, a residence permit, etc., or a deterministic derivative thereof. Alternatively or additionally, the NFT 18 created in method step 14 can contain, in addition to the public key 10, at least one confirmation of ownership 46. The confirmation of ownership 46 can be, for example, a training diploma, a stock portfolio, a certificate of ownership for things or real estate, etc., or a deterministic derivative thereof.

[0042] In at least one further method step 50, the NFT 18 is offered for transmission to at least one authentication entity 22 different from entity 20. This offer can be made, for example, via a public or restricted-access marketplace. In at least one further method step 52, the authentication entity 22 different from entity 20 requests transmission of the NFT 18. To do so, the authentication entity 22 can send a transaction request to the current DLT owner address of the NFT 18 via the DLT 44. In at least one method step 54, the requested NFT 18 is sent via the DLT 44 to a DLT address of the authentication entity 22. To do so, the device to which the DLT address to which the authentication entity 22 sent the transaction request in method step 52 is assigned can accept (sign) the transaction request.The authenticity of the public key 10 can then be confirmed by determining whether the NFT 18 is in the possession of a trusted authentication entity 22 different from the entity 20. The NFT 18 is then in the possession of the trusted authentication entity 22 if it is under the control of the DLT address assigned to the trusted authentication entity 22. In this case, only the authentication entity 22 knows a private key of this DLT address, which is required to access the NFT 18. Such a trusted authentication entity 22 can be a central certification authority. Such a trusted authentication entity 22 can be a product manufacturer. Such a trusted authentication entity 22 can be a product testing center. Such a trusted authentication entity 22 can be a repair center.Such a trusted authentication entity 22 may be a maintenance center. Such a trusted authentication entity 22 may be an authority. Such a trusted authentication entity 22 may be a KYC provider.

[0043] In at least one verification step 24, each NFT 18 received by the authentication entity 22 is checked to determine whether the NFT 18 was previously requested by the authentication entity 22 in method step 52. In a further method step 56, if the verification result from the verification step 24 is negative, the NFT 18 is immediately redeemed (redeemed). In an alternative further method step 58, if the verification result from the verification step 24 is negative, the NFT 18 is burned. In at least one method step 60, the NFT 18 is made publicly available by the authentication entity 22 for verification of ownership. In this process, the NFT 18 is assigned to a publicly queryable DLT owner address that can be uniquely assigned to the authentication entity 22. In at least one verification step 26, the public key 10 is verified. In the verification step 26, ownership of the NFT 18 is determined using the public key 10.Ownership is determined by a query in the DLT 44. When determining ownership, the DLT owner address that currently has control over the NFT 18 is determined. The verification step 26 can be performed by a web application, such as a web browser. The verification step 26 can be performed by a user, purchaser, or provider of an entity 20 configured as a product.

[0044] In the verification step 26, in addition to the verification of the public key 10, further information contained in the NFT 18 can also be read out, such as the confirmation 28, the expiration date 30, the legitimation 42 and / or the ownership confirmation 46.

[0045] In at least one further method step 62, in order to revoke the legitimacy of entity 20 by legitimizing entity 22, the NFT 18 is sent from the DLT owner address attributable to legitimizing entity 22 to a burn address of DLT 44. Alternatively, the NFT 18 can be sent from the DLT owner address attributable to legitimizing entity 22 to a DLT address of a developer / administrator of DLT 44, in particular to a DLT address of the smart contract originally used to create NFT 18. Alternatively, the NFT 18 can be sent / returned from the DLT owner address attributable to legitimizing entity 22 to another DLT address, e.g., the DLT address of entity 20.

[0046] Reference symbol

[0047] 10 Public Key

[0048] 12 Private Key

[0049] 14 Process step

[0050] 16 Copy of the public key

[0051] 18 NFT

[0052] 20 Entity

[0053] 22 Legitimizing entity

[0054] 24 test steps

[0055] 26 Verification step

[0056] 28 Confirmation

[0057] 30 Expiry date

[0058] 32 Verification computer system

[0059] 34 NFT creation device

[0060] 36 Verification device

[0061] 38 Identification device

[0062] 40 Additional Entity

[0063] 42 Legitimation

[0064] 44 DLT

[0065] 46 Confirmation of ownership

[0066] 48 process steps

[0067] 50 process steps

[0068] 52 process steps

[0069] 54 Process step

[0070] 56 Process step

[0071] 58 Process step

[0072] 60 process steps

[0073] 62 process steps

Claims

Claims: Verification method, in particular a computer-implemented verification method, in an asymmetric cryptosystem with at least one entity (20) to which a public key (10) and a private key (12) are assigned, characterized in that in at least one process step (14) at least one non-fungible token (NFT, 18) is created (minted), which contains a copy of the public key (16) or a deterministic derivative of the public key (10) and which is stored in a distributed ledger, such as a blockchain, a Tangle, or a hashgraph, a distributed ledger technology (DLT, 44). Verification method according to claim 1, characterized in that the authenticity of the public key (10) is confirmed by the fact that the NFT (18) is in possession of at least one authentication entity (22) different from the entity (20).Verification method according to claim 1 or 2, characterized in that the NFT (18) is offered for transmission to at least one authentication entity (22) different from the entity (20). Verification method according to one of the preceding claims, characterized in that at least one authentication entity (22) other than entity (20) requests transmission of the NFT (18) and / or that the NFT (18), preferably the requested NFT (18), is sent to at least one authentication entity (22) other than entity (20). Verification method according to claim 4, characterized in that at least one NFT (18) received by the authentication entity (22), preferably each NFT received by the authentication entity (22), is transmitted to the authentication entity (22). (18), in at least one verification step (24) it is checked whether the NFT (18) was previously requested by the authentication entity (22), wherein, in the event of a negative verification result, the NFT (18) is immediately redeemed or destroyed. Verification method at least according to claim 2, characterized in that in at least one verification step (26) the public key (10) is verified by determining ownership of the NFT (18)(18) of the public key (10). Verification method according to claim 6, characterized in that the NFT (18) is made available for verification of ownership.Verification method at least according to claim 2, characterized in that, in order to revoke the legitimation of the entity (20) by the legitimizing entity (22), the NFT (18) is sent to a burn address of the DLT (44) or to a DLT address of a developer / administrator of the DLT (44), in particular to a DLT address of the smart contract originally used to create the NFT (18). Verification method according to claim 6 or 7, characterized in that the verification step (26) is performed by a web application, such as a web browser. Verification method according to claim 6 or 7, characterized in that the entity (20) is configured as a product and that the verification step (26) is performed by a user, purchaser, or supplier of the product. Verification method at least according to claim 2, characterized in that the authentication entity (22) is a central certification authority. Verification method at least according to claim 2, characterized in that the entity (20) is configured as a product and that the authentication entity (22) is a manufacturer of the product.Verification method at least according to claim 2, characterized in that the entity (20) is configured as a product and that the authentication entity (22) is a product testing facility or a repair and / or maintenance facility for the product. Verification method at least according to claim 2, characterized in that the entity (20) is a person and that the authentication entity (22) is a body authorized to verify the identity of the person, such as a government agency or a KYC provider. Verification method according to one of the preceding claims, characterized in that the NFT (18) created in the process step (14) includes, in addition to the public key (10), at least one confirmation (28), for example a warranty certificate, insurance certificate, a user license certificate, or its deterministic derivative and / or at least one expiry date (30), for example a warranty expiry, an insurance period, a duration of a user license, which is assigned to the entity (20) or to an agreement associated with the entity (20).Verification method according to one of the preceding claims, characterized in that the entity (20) is a person with a Digital ID and / or Decentralized Identifier (DID) having a Private Key-Public Key pair, and that the NFT (18) created in the process step (14) additionally includes at least one authentication (42) of the person, for example, an identity document, a driver's license, a residence permit, etc., or its deterministic derivative. Verification method according to one of the preceding claims, characterized in that the entity (20) is a person with a Digital ID and / or Decentralized Identifier (DID) having a Private Key-Public Key pair, and that the NFT (18) created in the process step (14) additionally includes at least one proof of ownership (46), for example, an educational diploma, a stock portfolio, a certificate of ownership for things or real estate, etc., or includes its deterministic derivative.

18. Verification computer system (32), which is provided in particular for carrying out a verification procedure according to one of the preceding claims, comprising at least one NFT creation device (34), which is provided for creating an NFT (18) which includes a copy of a public key (16) of an asymmetric cryptosystem assigned to an entity (20) or a deterministic derivative of the public key (10), and which is provided for storing the created NFT (18) in a distributed ledger, such as a blockchain, a tangle or a hashgraph, a distributed ledger technology (DLT, 44).

19. Verification computer system (32) according to claim 18, characterized by a verification device (36), in particular designed separately from the NFT creation device (34), which is provided to verify the authenticity of the public key (10) by querying and evaluating the ownership of the NFT (18).

20. Verification computer system (32) according to claim 18 or 19, characterized by a legitimation device (38), which is designed to be separate from the NFT creation device (34) and from the verification device (36), and which is provided to take possession of / acquire the NFT (18) via a legitimation address of the DLT (44) that is publicly viewable and attributable to a legitimation entity (22).

21. NFT creation device (34) of the verification computer system (32) according to claim 18.

22. Verification device (36) of the verification computer system (32) according to claim 19.