Method for implementing a transaction involving a non-fungible token uniquely associated with a physical product.

The blockchain-based PBT system authenticates and transfers ownership of luxury products securely, preventing counterfeits and theft by ensuring product verification on both buyer and seller devices, with optional authority verification, providing a secure and unalterable transaction history.

FR3148653A1Pending Publication Date: 2024-11-15AURA BLOCKCHAIN CONSORTIUM
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
FR2023004745
Authority / Receiving Office
FR · FR
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

Existing methods for authenticating and transferring ownership of luxury products fail to ensure that the product is both authentic and legally possessed, as they do not prevent the sale of counterfeit or stolen items, and certificates can be falsified.

Method used

A method involving a blockchain-based non-fungible token (NFT) system, where a 'product-bound token' (PBT) is associated with a physical product, ensuring authentication through QR codes, electronic labels, digital fingerprints, and AI algorithms, and transactions are executed only if the product is verified as authentic on both buyer and seller devices, with optional authority verification.

Benefits of technology

Ensures that only the original and legally owned product can be transferred, preventing counterfeits and theft by requiring authentication on both devices and potentially involving a trusted third party, with a secure, unalterable record of transactions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

The present invention relates to a method for implementing a transaction in a blockchain-type database, involving a non-fungible token, the method being characterized in that it comprises the implementation of the following steps: Reception by a first client device (2a) from a first user recipient of the transaction of an authentication request for a physical product (1) uniquely associated with said non-fungible token; If said physical product (1) is authenticated on said first client device (2a), execution of said transaction in the blockchain-type database [Fig. 1]
Need to check novelty before this filing date? Find Prior Art

Description

Title of the invention: Method for implementing a transaction involving a non-fungible token uniquely associated with a physical product. [0001 ] GENERAL TECHNICAL FIELD

[0002] The present invention relates to the field of securing transactions. More specifically, it relates to a method for implementing a transaction in a blockchain-type database and a method for implementing a transaction relating to a product.

[0003] STATE OF THE ART

[0004] Products from major luxury brands (such as handbags, jewelry, watches, etc.) often have, due to their rarity, a value that decreases only slightly over time and in some cases even increases. Thus, these products are popular on the resale market, known as the secondary market.

[0005] The problem is that this secondary market is plagued by the growing presence of illegal or counterfeit products, which malicious third parties hope to sell among the legal products, which is all the more so since the transactions are most often over-the-counter, without involving a professional who would be capable of assessing the product.

[0006] To solve this problem, solutions have been proposed for the unique identification (and therefore authentication) of a product: - Some products incorporate a physical element such as an RFID tag, or a QR code, encoding a unique product identifier; - We also know of so-called “fingerprinting” solutions that allow the creation of a unique and tamper-proof digital identity of a product from a photo, in particular from visible micro-defects; - More recently, specifically trained artificial intelligence algorithms can recognize each copy of a product.

[0007] These solutions provide satisfaction and allow a potential buyer to ensure that the product he is going to buy is original and not a copy, but do not allow him to ensure that it has not been stolen.

[0008] Luxury products are sold with a certificate which is intended to guarantee legal possession of the product, but these certificates are themselves falsifiable and conversely the seller may not find his certificate.

[0009] The present invention improves the situation. PRESENTATION OF THE INVENTION

[0010] The present invention therefore relates, according to a first aspect, to a method for implementing a transaction in a blockchain-type database, relating to a non-fungible token, the method being characterized in that it comprises the implementation of steps of: a. Reception by a first client device (2a) from a first user receiving the transaction of a request for authentication of a physical product (1) uniquely associated with said non-fungible token; b. If said physical product (1) is authenticated on said first client device (2a), execution of said transaction in the blockchain database.

[0011] According to advantageous and non-limiting characteristics:

[0012] The method comprises implementing a step (b) of receiving by a second client device of a second user at the origin of the transaction another request for authentication of the physical product uniquely associated with said non-fungible token.

[0013] Either step (c) is implemented if said physical product is authenticated on said second client device, or in step (d) said transaction is executed if said physical product is authenticated on each of the first and second client devices.

[0014] Step (c) comprises verifying said authentication by an authority entity.

[0015] Step (d) includes paying a gas fee.

[0016] The authentication of said physical product comprises at least one of: the reading of a QR code carried by the physical product, the reading of an electronic label carried by the physical product, the extraction of a digital fingerprint from a photo of said physical product and the recognition of said physical product by an artificial intelligence algorithm.

[0017] Said blockchain database is the Ethereum® blockchain or one of its side chains, and said non-fungible token is based on the ERC-721 standard.

[0018] The method is implemented in the form of a smart contract.

[0019] Said smart contract is controlled by a trusted third party, step (d) comprising the calculation and payment of a royalty for the benefit of said trusted third party, in particular in accordance with the ERC-2981 standard.

[0020] The non-fungible token contains descriptive metadata of a history of said physical product, step (d) comprising updating said metadata.

[0021] According to a second aspect, the invention relates to a method for implementing a transaction relating to the transfer of a physical product from a second user to a first user, characterized in that it comprises the implementation of a step (a) requesting, from a second client device of the second user, a transfer from the second user to the first user of a non-fungible token uniquely associated with said physical product, then implementing the method according to the first aspect, wherein said transaction in a blockchain database is a transfer of said non-fungible token from the second user to the first user.

[0022] According to a third aspect, the invention relates to a method for implementing a transaction relating to the initial acquisition by a first user of a physical product, characterized in that it comprises the implementation of a step (a') of requesting the creation of a non-fungible token uniquely associated with said physical product for the benefit of the first user, then the implementation of the method according to the first aspect, in which said transaction in a blockchain type database is the creation of said non-fungible token for the benefit of the first user.

[0023] According to a fourth aspect, the invention relates to a first client device of a first user receiving a transaction in a blockchain type database, relating to a non-fungible token, characterized in that it is configured to: - receive a request for authentication of a physical product uniquely associated with said non-fungible token; - If said physical product is authenticated on said first client device, execute said transaction in the blockchain database.

[0024] According to a fifth aspect, the invention relates to a set of a first client device according to the fifth aspect and a second client device of a second user at the origin of said transaction and configured to receive another request for authentication of the physical product uniquely associated with said non-fungible token.

[0025] According to a sixth and a seventh aspect, the invention relates to a computer program product comprising code instructions for executing a method according to the first aspect of implementing a transaction in a blockchain-type database, relating to a non-fungible token; and a storage means readable by computer equipment on which is recorded a computer program product comprising code instructions for executing a method according to the first aspect of implementing a transaction in a blockchain-type database, relating to a non-fungible token. PRESENTATION OF FIGURES

[0026] Other characteristics and advantages of the present invention will appear on reading the following description of a preferred embodiment. This des- description will be given with reference to the attached drawings in which:

[0027] [Fig.l] [Fig.l] is a diagram of a system for implementing the method according to the invention;

[0028] [Fig.2a] [Fig.2a] is a diagram illustrating the transfer of a state-of-the-art physical NFT;

[0029] [Fig.2b]Figure 2c is a diagram illustrating the transfer of a PBT according to the invention;

[0030] [Fig.3a] [Fig.3a] is a flowchart illustrating the steps of a first embodiment of the method according to the invention;

[0031] [Fig.3b] [Fig.3b] is a flowchart illustrating the steps of a second embodiment of the method according to the invention;

[0032] [Fig.3c] [Fig.3c] is a flowchart illustrating the steps of a third embodiment of the method according to the invention. DETAILED DESCRIPTION

[0033] Architecture

[0034] The present invention relates to a method for implementing a transaction in a blockchain-type database 3 relating to a non-fungible token, which as will be seen will be uniquely associated with a physical product 1, in a system such as represented in [Fig.l], in particular for implementing a transaction relating to said product 1. This physical product may be any marketable merchandise, in particular a luxury product such as a handbag, a watch, a pair of shoes, etc. Preferably, said physical product 1 is authenticable, or even uniquely identifiable; techniques for this purpose will be presented later.

[0035] Said system comprises at least one client device 2a, 2b (generally a large number of them), acting as a “wallet”, each being a personal device of a user allowing him to carry out transactions on his behalf, for example sending or receiving cryptocurrencies. As such, each client device 2a, 2b can implement an application such as MetaMask.

[0036] In particular, there is at least one first client device 2a called the creditor as the device of a first “buyer” user in said transaction (recipient of the transaction), and advantageously a second client device 2b called the debtor as the device of a second “seller” user in said transaction (at the origin of the transaction). Said non-fungible token and / or said physical product are in other words transferred from the second user (of the second client device 2b) to the first user (that of the first client device 2a). Note that we will see a specific use case of creation of the non-fungible token for the benefit of the first user (of the first client device 2a).

[0037] In the present case, each client device 2a, 2b is preferably a lightweight physical device such as a smart card or a terminal such as a smartphone, in particular a security element (Secure Element) of such a terminal, i.e. a dedicated closed microprocessor of the enclave type. It will be understood that the present invention is not limited to these cases and that the client device 2a, 2b can always be a smartphone, a touch tablet, a personal computer, etc. Each client device 2a, 2b can further comprise a camera and / or an NFC or RFID reader.

[0038] The devices 2a, 2b communicate with each other via at least one network 20, for example the Internet network, a cellular network, or a combination of such networks. They each have read and write access to a blockchain-type database 3 stored in the network 20. It should be noted that in the same case there are also transaction validating devices, called “miners”, which are known to those skilled in the art and which will not be discussed in more detail.

[0039] The database 3 is public, in the sense that it is freely accessible for reading not only by the devices 2a, 2b present but also by any other third-party device. Any third-party device can in particular consult the data written by one of the devices 2a, 2b.

[0040] Blockchain databases generally serve as the basis for electronic money transaction systems. Each client device 2a, 2b stores a mutually associated public key and a private key that are specific to it (and allow transactions to be carried out on the blockchain database 3). The private key allows signed data to be written to the database; it is intended not to be communicated to third parties. The public key allows the device 2a, 2b (and any other holder of an account for accessing the database 3) to verify that data present in the database 3 has been written therein by the device 2a, 2b. Generally, the client device 2 is designated by an address that is typically a cryptographic fingerprint of its public key.

[0041] The database 3 is distributed or decentralized in the network 20, that is to say it is stored by a plurality of nodes of the network 20 with which the devices 2a, 2b can communicate.

[0042] A blockchain database is distributed among several storage nodes in a network. The storage nodes are configured to validate data written to the database by implementing a consensus-building method between the storage nodes. Such a method is, for example, "proof of work" or POW, or "proof of stake" or POS. The contents of the database (a history of all past transactions made between accounts of system users) is thus protected against falsification despite its distributed nature.

[0043] The most famous blockchain-type databases are the Bitcoin® or Ethereum® blockchains, typically the second in the context of the present invention, or any other compatible blockchain, i.e. based on the EVM (Ethereum Virtual Machine), the execution environment for Ethereum instructions (in a language such as Solidity). We speak of “sidechains”, such as Polygon or Avalanche.

[0044] A non-fungible token, or NFT, is a type of cryptographic token that can be transferred on a blockchain, just like a cryptocurrency, but is unique and therefore non-interchangeable, unlike the latter. The Ethereum blockchains (or side chains), but also Solana or Cardano are the most used for NFTs.

[0045] An NFT generally contains a reference to a digital object such as an image or video, sometimes artistic, of which it constitutes a sort of certificate of authenticity, and sometimes metadata. It is claimed that an NFT could constitute ownership of said digital object, but there is no real legal basis.

[0046] Minting is the act of creating an NFT, typically by means of a smart contract on the blockchain, for example in accordance with the ERC-721 standard on the Ethereum blockchain. In particular, an ERC-721 token has a tokenld parameter making it unique (as opposed to an ERC-20 fungible token which is a standard ETH, i.e. the native cryptocurrency of the Ethereum blockchain). Like any other transaction on the blockchain, minting involves the payment of a “gas fee,” to reward miners for the computing power they must use to execute transactions.

[0047] Principle

[0048] The present invention proposes a new type of NFT, advantageously still based on the ERC-721 standard, which will be called a “product-bound token”, or PBT (“product-bound token”), which very cleverly allows the ownership and authenticity of a physical product to be guaranteed during a transaction.

[0049] Note that it is already known to associate an NFT with a physical product (we speak of a “physical NFT”), for example if the digital data to which it points constitutes a unique digital identifier of said physical product, for example that coded by a QR code or an RFID tag carried by the physical product, as explained in the introduction.

[0050] However, as seen in [Fig.2a], such physical NFTs do not provide any solution to the problem of the resale of counterfeit or stolen products, and are only of advertising interest, since the NFT and the product can be resold independently. In practice, the object of value is the physical NFT and the attached physical product is an "accessory" often offered for the purchase of the NFT.

[0051] On the contrary, the PBT is an NFT accessory to a physical product (and not the other way around), which has no value in itself and is only transferable if the buyer provides proof of possession of the linked product, as seen in [Fig.2b]. Thus: - If the product is a fake, the transfer of the NFT will be rejected; - If the product is stolen, it will not be resalable due to lack of access to the NFT.

[0052] Method for implementing a transaction relating to an NFT

[0053] The present invention relates, as explained according to a first aspect, to a method for implementing a transaction in a blockchain-type database, relating to a non-fungible token, i.e. an NFT, here of the PBT type.

[0054] In practice, there are two possible types of transactions on said token: - Either a transfer of the token from the second user to the first user, preferably within the framework of a transfer of the physical product 1 from the second user to the first user, represented by [Fig.3a] and 3b; - Either the creation of the token (“mint”) by the second user for the benefit of the first user, typically when the physical product 1 is first put on sale (the second user is then the manufacturer of the product 1, i.e. the brand), represented by [Fig.3c].

[0055] The present methods are in all cases implemented by the data processing means of the client devices 2a and / or 2b, typically in the form of a smart contract as permitted in particular by the Ethereum ecosystem, in particular via an MTM centralizer (“multi-token minter”) which makes it possible to deploy smart contracts via any public blockchain. Alternatively, one can go through a trusted third party, i.e. a dedicated platform such as OpenSea.

[0056] The methods have at least one step (c) of reception by the first client device 2a of the first user receiving the transaction of a request for authentication of the physical product 1 uniquely associated with said non-fungible token, and (d) of execution of said transaction in the blockchain type database if said physical product 1 is authenticated on said first client device 2a.

[0057] By authentication of the physical product 1, we mean at least the verification of the authenticity of the physical product 1, and advantageously its identification, that is to say the verification that it is indeed a specific copy of the product. In both cases, we ensure that the first user has been given the original product and not a counterfeit.

[0058] Preferably, said authentication is proximity authentication, im- replicating the immediate presence of said physical product 1, and in particular a direct interaction of the first terminal 2a with the product. This makes it possible to guarantee that the second user has in his hands the product 1 associated with the PBT, i.e. that the second user has for example given it to him by hand or sent it by post.

[0059] Note that certain authentication techniques which will be presented use a photo which is thus advantageously acquired live by a camera of the first client device 12a, and not received from a remote terminal, which could lead to risks of falsification (it is understood in any case that the first user would have no interest in doing this because he is precisely seeking to ensure that he has been given an authentic product).

[0060] Preferably, the authentication of said physical product 1 comprises at least one of: - reading a QR code carried by the physical product 1 (by a camera of the first client device 2a). In particular, it is possible to extract from the QR code a product identifier, or even a unique identifier of this copy of the product 1, and to verify this identifier, in particular by means of a proprietary function of the brand of said product, where appropriate using digital data directly contained or linked to the PBT. For example, it is possible to have a cryptographic fingerprint (hashed) of a reference identifier of the product accessible via a URL contained in the PBT, called the expected cryptographic fingerprint (it could even be directly contained in the PBT), and the verification is carried out by hashing (with a predefined hash function) the identifier extracted from the QR code and comparing it with said expected cryptographic fingerprint - reading an electronic label (also called a “radio tag”, typically NFC or RFID) carried by the physical product 1, for example by an appropriate reader of the client device 2a. The same identifier mechanism can be used as for the QR code; - the extraction of a digital fingerprint from a photo of said physical product 1. Again, it is possible to have a reference digital fingerprint contained or accessible via the PBT, and to use a mechanism for calculating the distance between the extracted digital fingerprint and the expected fingerprint, in particular by fuzzy logic. Again, such a mechanism is known to those skilled in the art. - the recognition of said physical product 1 by an artificial intelligence algorithm. We can directly have AI algorithms such as classification neural networks (typically CNNs) provided by the product brands, taking as input a photo of the product 1 allowing directly answer the question of its authenticity, in a secure manner since it is a “black box”.

[0061] In the case where the transaction is a transfer of the PBT (figures 3a and 3b), there is advantageously a prior step (b), similar to step (c), of reception by a second client device 2a from a first user at the origin of the transaction of another request for authentication of a physical product 1 uniquely associated with said non-fungible token. It is noted that this is also the case in [Fig.2b]. This makes it possible to ensure that the second user (the seller) has an original, and therefore has the right to transfer the PBT.

[0062] The same authentication / identification techniques of product 1 are advantageously used.

[0063] In such a case of double authentication: - either step (c) is implemented if (and in particular only if) said physical product 1 is authenticated on said second client device 2b, as represented by [Fig.3a]. In other words, at this stage the second user can transfer the physical product 1 to the first user, and this triggers the authentication request by the first user. This is an asymmetric scheme, which is typically used if the product is transferred by post, and therefore with a delay (and that represented by [Fig.2a]). At step (d) it is then sufficient for the product 1 to be authenticated on the first client device 2a for the transaction to be able to be executed. - either in step (d) said transaction is executed if (and in particular only if) said physical product 1 is authenticated on each of the first and second client devices 2a, 2b, as shown in [Fig.3b]. In other words, the two authentications can be done simultaneously or almost simultaneously, and we just wait to have the results of the two verifications to launch the execution. This is a symmetrical scheme, which is typically used when handing over the product 1 in person.

[0064] In all cases, step (b) (if it takes place) and / or step (c) may comprise the verification of said authentication by an authority entity. By authority entity is meant either the manufacturer of the product 1 (the brand), or a trusted third party, for example an intermediary involved in the transaction, for example a marketplace.

[0065] The notion of verification of said authentication by an authority entity can be interpreted here in the broad sense and can take many forms: - according to a first embodiment, there may be a third authentication in its own right, i.e. the presence of a step (c') similar to steps (b) and / or (c) (which may take place at any time before step (d)) of reception by a third client device of the authority entity (potentially a remote and automated server, or a terminal of an employee of the brand) of another request for authentication of the physical product 1 uniquely associated with said non-fungible token. For example, each user can implement authentication via electronic label, and in addition the authority entity can implement remote authentication by recognition of said physical product 1 by an artificial intelligence algorithm kept secret: the second user performs his authentication (b) and takes a photo that he transfers to said third client device for it to perform. Thus, when the first user receives the product 1, he knows that he has also been authenticated by the brand, and he is even more convinced of the authenticity of the product when he scans his electronic label in step (c). Alternatively, the exchange can take place in a store, and the seller also authenticates the product 1.

[0066] In such an embodiment, again either step (b) or step (c) is implemented if said physical product 1 is authenticated on the third client device of the authority entity (sequential operation), or in step (d) said transaction is executed if said physical product 1 is authenticated on each of the first and / or second client device 2a, 2b, and the third client device (triple authentication). - according to a second embodiment, visible in [Fig.3b], the first and / or the second authentication is controlled by the authority entity, and it can be provided that if necessary the latter signs the transaction, and that only a signed transaction can be executed in step (d). This means that the authority entity certifies for example that a recognized authentication mechanism has been used, and correctly. - According to a third embodiment, the authority entity carries out additional checks making it possible to observe the context of the authentication, for example by analyzing the state of wear of the product, by comparing it with a digital maintenance log, by verifying a guarantee, but also by verifying a location of the authentication if the transaction must take place at a specific place, etc.

[0067] Step (d) typically includes the payment of a gas fee (by the first user, on his client device 2a). In other words, as soon as the required authentication(s) are made, the transaction is executable, and it is the first user, who now has the conviction that the product being legally possessed by the second user and was an original, who can trigger the effective transfer of the PBT by paying the gas fee. The execution of the transaction in the blockchain is then done in a conventional manner: it is verified by the miners, and included in the next block mined. Miners collect gas fees for their work.

[0068] Note that the transaction may also involve the transfer of cryptocurrencies from the first user to the second user as payment for the transfer of the PBT (and of the physical product 1), although as we will see this transfer may involve a classic payment outside the blockchain, or even be free of charge (gift).

[0069] Step (d) may further comprise, in particular in the case of a payment in cryptocurrency and when the smart contract is controlled by a trusted third party, the calculation and payment of a royalty to the benefit of said trusted third party, as a commission for having ensured the transaction. This is typically permitted by the ERC-2981 standard.

[0070] Finally, in a particularly preferred manner, the non-fungible token contains descriptive metadata of a history of said physical product, called traceability data. They may include the ownership history of the product and / or the repair and maintenance history, where appropriate in a pseudo-anonymized manner. In this case, step (d) advantageously comprises updating said metadata, in particular by adding the transaction currently carried out. This makes it possible to have a complete, public, and unalterable record of what happened to the product 1.

[0071] Method for implementing a transaction relating to the physical product

[0072] We will now describe two methods of implementing a transaction relating to the transfer of the physical product 1, involving the method of implementing a transaction in a blockchain type database, relating to a non-fungible token, according to the first aspect.

[0073] According to a second aspect, said transaction relating to the transfer of the physical product 1 is from a second user to a first user, this is the case of resale of the physical product 1.

[0074] With reference to Figures 3a and 3b, the method begins with a step (a) of requesting, from the second client device 2b of the second user, the transfer of the non-fungible token uniquely associated with said physical product 1 (the PBT), from the second user to the first user.

[0075] It is understood that this step is only feasible if the second user actually has the PBT in his wallet. Otherwise, the product 1 is stolen. It is carried out in particular by identifying the first user on the second terminal 2b, in particular by entering a public address of his wallet.

[0076] Then, the method according to the first aspect is implemented so as to implement the transfer of said non-fungible token from the second user to the first user as a transaction in a blockchain type database which is the subject of the method (at least steps (c) and (d), and preferably step (b)). From here to step (c), the second user must have transmitted the physical product to the first user, possibly against payment of a sum of money, in exchange for something, etc. Preferably, as explained, the transaction in the blockchain database 3 may involve the reverse transfer of electronic money from the first user to the second user as payment. Alternatively, it may be a gift.

[0077] In summary, the method according to the second aspect is as follows:

[0078] Method for implementing a transaction relating to the transfer of a physical product 1 from a second user to a first user, characterized in that it comprises the implementation of steps of: a. request, from a second client device 2b of the second user, to transfer from the second user to the first user a non-fungible token uniquely associated with said physical product 1, b. optionally, reception by the second client device 2b of a request for authentication of the physical product 1; c. Receipt by a first client device 2a from the first user of a request for authentication of the physical product 1; d. If said physical product 1 is authenticated on said first client device 2a (and where applicable on the second client device 2b), execution of a transaction in the blockchain type database for transferring said non-fungible token from the second user to the first user.

[0079] According to a third aspect, said transaction relating to the transfer of the physical product 1 is the initial acquisition by a first user of a physical product, this is the case of a purchase in store or online of the new physical product 1.

[0080] With reference to [Fig.3c], the method begins with a step (a') of requesting the creation of the non-fungible token uniquely associated with said physical product 1 (the PBT), for the benefit of the first user. There may or may not be a second user, depending on whether this is done uniquely, or by a seller in the store on his client device (which is then the second client device 2b, which is then potentially confused with the possible third client device of the authority entity). This step may be triggered by the payment of the price of the new physical product 1.

[0081] Then, the method according to the first aspect is again implemented so as to implement said creation (“mint”) of said non-fungible token from the second user to the first user as a transaction in a blockchain type database which is the subject of the method (at least steps (c) and (d)).

[0082] In summary, the method according to the third aspect is as follows:

[0083] Method for implementing a transaction relating to the initial acquisition by a first user of a physical product 1, characterized in that it comprises the implementation work of stages of:

[0084] (a') request to create a non-fungible token uniquely associated with said physical product (1) for the benefit of the first user; a. optionally, reception by a possible second client device 2b from which the creation request would have been issued, of a request for authentication of the physical product 1; b. Reception by a first client device 2a from the first user of a request for authentication of the physical product 1; c. If said physical product 1 is authenticated on said first client device 2a (and where applicable on the second client device 2b), execution of a transaction in the blockchain type database for the creation of said non-fungible token for the benefit of the first user.

[0085] Client devices

[0086] According to a fourth and / or a fifth aspect, the invention relates to the first and / or the second client device 2a, 2b, and in particular the whole of the first and second client devices 2a, 2b, for implementing the method for implementing a transaction in a blockchain type database, relating to a non-fungible token, according to the first aspect.

[0087] The first client device 2a, of a first user receiving a transaction in a blockchain type database, relating to a non-fungible token, is configured to: - receive a request for authentication of a physical product 1 uniquely associated with said non-fungible token; - If said physical product 1 is authenticated on said first client device 2a, execute said transaction in the blockchain type database.

[0088] The first client device 2b, of a second user at the origin of said transaction in a blockchain type database, relating to a non-fungible token, is configured to: - If said transaction is a transfer of a non-fungible token uniquely associated with said physical product 1, from the second user to the first user, require this transfer of the non-fungible token; or if the transaction is the creation of said non-fungible token uniquely associated with said physical product 1, for the benefit of the first user, require this creation of the non-fungible token; - receive a possible other authentication request for the physical product 1 uniquely associated with said non-fungible token.

[0089] Computer program product

[0090] According to a sixth and a seventh aspect, the invention relates to a program product computer comprising code instructions for the execution (on the data processing means of the client devices 2a and / or 2b) of a method according to the first aspect of implementing a transaction in a blockchain type database, relating to a non-fungible token (or even the methods according to the second or third aspect), as well as storage means readable by computer equipment (for example the memories of the client devices 2a and / or 2b) on which this computer program product is found.

Claims

Claims

1. Method for implementing a transaction in a blockchain-type database, relating to a non-fungible token, the method being characterized in that it comprises the implementation of steps of: a. Reception by a first client device (2a) of a first user receiving the transaction of a request for authentication of a physical product (1) uniquely associated with said non-fungible token; b. If said physical product (1) is authenticated on said first client device (2a), execution of said transaction in the blockchain-type database.

2. Method according to claim 1, comprising the implementation of a step (b) of reception by a second client device (2b) of a second user at the origin of the transaction of another request for authentication of the physical product (1) uniquely associated with said non-fungible token.

3. The method of claim 2, wherein either step (c) is performed if said physical product (1) is authenticated on said second client device (2b), or in step (d) said transaction is performed if said physical product (1) is authenticated on each of the first and second client devices (2a, 2b).

4. Method according to one of claims 1 to 3, in which step (c) comprises the verification of said authentication by an authority entity.

5. The method of one of claims 1 to 4, wherein step (d) comprises paying a gas fee.

6. Method according to one of claims 1 to 5, wherein the authentication of said physical product (1) comprises at least one of: reading a QR code carried by the physical product (1), reading an electronic label carried by the physical product (1), extracting a digital fingerprint from a photo of said physical product (1) and recognizing said physical product (1) by an artificial intelligence algorithm.

7. Method according to one of claims 1 to 6, in which said blockchain type database is the Ethereum® blockchain or one of its side chains, and said non-fungible token is based on the ERC-721 standard.

8. Method according to one of claims 1 to 7, implemented in the form of a smart contract.

9. The method of claim 8, wherein said smart contract is controlled by a trusted third party, step (d) comprising calculating and paying a royalty to said trusted third party, in particular in accordance with the ERC-2981 standard.

10. Method according to one of claims 1 to 9, in which the non-fungible token contains metadata descriptive of a history of said physical product, step (d) comprising updating said metadata.

11. Method for implementing a transaction relating to the transfer of a physical product (1) from a second user to a first user, characterized in that it comprises the implementation of a step (a) of requesting, from a second client device (2b) of the second user, the transfer from the second user to the first user of a non-fungible token uniquely associated with said physical product (1), then the implementation of the method according to one of claims 1 to 10, in which said transaction in a blockchain type database is a transfer of said non-fungible token from the second user to the first user.

12. Method for implementing a transaction relating to the initial acquisition by a first user of a physical product (1), characterized in that it comprises the implementation of a step (a') of requesting the creation of a non-fungible token uniquely associated with said physical product (1) for the benefit of the first user, then the implementation of the method according to one of claims 1 to 10, in which said transaction in a blockchain type database is the creation of said non-fungible token for the benefit of the first user.

13. First client device (2a) of a first user receiving a transaction in a blockchain type database, relating to a non-fungible token, characterized in that it is configured to: - receive a request for authentication of a physical product (1) uniquely associated with said non-fungible token; - If said physical product (1) is authenticated on said first client device (2a), execute said transaction in the blockchain-type database.

14. Set of a first client device (2a) according to claim 10 and a second client device (2b) of a second user at the origin of said transaction and configured to receive another request for authentication of the physical product (1) uniquely associated with said non-fungible token.

15. Computer program product comprising code instructions for executing a method according to one of claims 1 to 10 for implementing a transaction in a blockchain type database, relating to a non-fungible token, when said program is executed on a computer.

16. Storage means readable by computer equipment on which is recorded a computer program product comprising code instructions for the execution of a method according to one of claims 1 to 10 for implementing a transaction in a blockchain type database, relating to a non-fungible token.

Citation Information

Patent Citations

  • Tracking apparel items using distributed ledgers

    US11374756B1

  • Authentication of products

    US20210248653A1

  • Fingerprinting Physical Items to Mint NFT's

    US20230109574A1

  • Method of providing real asset authentication service using decentralized identifier and non-fungible token

    US20230145439A1