METHOD AND DEVICES FOR PROVIDING DATA KNOWLEDGE BY A BLOCKCHAIN USER
Patent Information
- Application Number
- DE602020041614
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-03-29
- Filing Date
- 2020-03-27
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2040-03-27
AI Technical Summary
Current methods for certifying user data in blockchain technology require users to disclose personal information to all network users, compromising privacy and lacking effective proof mechanisms to verify data authenticity.
A method where a user's terminal requests certification from a trusted entity registered on the blockchain, obtaining and publishing a second data piece derived from the first data piece, ensuring the user's knowledge of the original data without disclosing it to all users, using an Oracle service to verify the user's possession of the data before the trusted entity publishes it on the blockchain.
This approach allows for secure verification of user data ownership without disclosing personal information to all network users, protecting user privacy and ensuring data authenticity through timestamped publication and smart contract mechanisms.
Description
Prior art
[0001] The invention relates to the general field of telecommunications networks, and more specifically to blockchain technology.
[0002] As stated in the document (https: / / fr.wikipedia.org / wiki / Blockchain), it is recalled that "blockchain technology is a technology for storing and transmitting information without a controlling body. Technically, it is a distributed database in which the information sent by users and the internal links to the database are verified and grouped at regular time intervals into blocks, the whole being secured by cryptography, and thus forming a chain.
[0003] By extension, a blockchain is a distributed database that manages a list of records protected against falsification or modification by storage nodes; it is therefore a distributed and secure register of all transactions carried out since the start of the distributed system.
[0004] Blockchains are further characterized by the fact that their contents cannot be modified or deleted: information published on a blockchain remains there forever. We refer to information "published" on a blockchain as information recorded or saved on it.
[0005] One issue that arises in the context of blockchain technology is the certification of user data. In particular, this data may relate to user attributes such as their first and last names, addresses, telephone numbers, social media accounts, etc. A so-called "proof" mechanism is required to ensure that user data is correct (true).
[0006] Al-Bassam, M., "A smart contract-based PKI and identity system", Proc. ACM Workshop on Blockchain, Cryptocurrencies and Contracts. ACM, 2017. pages 35-40, proposes a model for managing user identities based on smart contracts. In this model, a user publishes their attributes in a way that makes them public. The attributes can then be signed by a third party on the blockchain to guarantee their authenticity.
[0007] This solution requires the user to disclose their personal data to all users in the chain. Patent application US 2018 / 0365448 A1 discloses a notary service that verifies that a user has access to data before a given date.
[0008] There is therefore a need for a method of verifying user data certification that does not have the drawbacks of prior art methods. Statement of the invention
[0009] The scope of the invention is determined by the independent claims.
[0010] The invention relates to a method for requesting certification from a trusted entity registered in a blockchain of the knowledge of a first piece of data by a user registered in the blockchain, the first piece of data belonging to the user, the method comprising steps of: receiving outside the blockchain, from the trusted entity, a second piece of data obtained from said first piece of data, the trusted entity having become aware of the first piece of data outside the blockchain; and publishing, by a terminal of the user, the second piece of data in the blockchain; said trusted entity being configured to publish the second piece of data in the blockchain at a date later than the date of publication of the second piece of data in the blockchain by the terminal of the user.
[0011] Correlatively, the invention relates to a terminal of a user registered in a blockchain, the terminal being configured to request an attestation from a trusted entity registered in the blockchain, of the knowledge of a first piece of data by the user, the first piece of data belonging to the user, this terminal comprising: communication means configured to receive outside the blockchain, from the trusted entity, a second piece of data obtained from the first piece of data, the trusted entity having become aware of the first piece of data outside the blockchain; and a publication module configured to publish the second piece of data in the blockchain and to send, to the device comprising the trusted entity, a notification, following the publication of the second piece of data in the blockchain by the or a date of publication of the second piece of data in the chain by said terminal; the trusted entity being configured to publish the second data in the blockchain at a date later than the date of publication of the second data in the blockchain by the user's terminal.
[0012] The characteristics and advantages of the certification request method according to the invention presented below apply in the same way to the terminal according to the invention and vice versa.
[0013] For the purposes of the invention, the first data item may be personal data of the user (or attribute): surname, first name, telephone number, postal address, e-mail address, age, profession, etc. The first data item may also be a multimedia object such as a photo, a video, a text document, etc. In other words, the first data item is data belonging to the user or specific to the user. The user holding the first data item thus has knowledge of this first data item.
[0014] In the description, we use the expressions "user registered on the blockchain" or "terminal (of this user) registered on the blockchain" equivalently and for the same meaning. Note that a user can have several terminals.
[0015] According to the invention, the terminal may be a smartphone-type mobile phone, a computer, a tablet, or any other communicating device allowing a user to access a blockchain.
[0016] As mentioned above, data published in the blockchain refers to data recorded on it. To publish data in the blockchain, a user sends this data to the blockchain. After sending the data, a "miner" or "validator" user inserts this data into a block in the chain, then broadcasts (publishes) the new updated block. For the purposes of the invention, the publication date of data in the blockchain refers to the date the block was added to the chain.
[0017] For the purposes of the invention, publication by a user's terminal (or by the trusted entity) means: either a publication in the blockchain when this user (or the trusted entity) is a miner or validator user, or a publication request for another user registered on the blockchain as a miner or validator to publish the second data in the blockchain.
[0018] According to the invention, the trusted entity can deploy an Oracle service. It is recalled that an Oracle is a service authorized to enter data into the blockchain at the request of a user. For information purposes, the article "Oracles, the link between the blockchain and the world" by Simon Polrot, published on 09 / 13 / 2016 on the website "ethereum-france.com" defines and describes the operation of an Oracle.
[0019] The invention allows a third party who consults the blockchain to verify that the user held the first data. Indeed, the terminal publishing the second data (obtained from the first data, this first data being own or belonging to the user) before the trusted entity, it is ensured that the terminal has not simply copied the second data published in the blockchain by the Oracle, but that it has actually received the data from the Oracle by another means. The fact that it received the second data from the Oracle by another means and that this second data was generated by the Oracle from the first data constitutes proof that the user held the first data before the Oracle made public the proof of knowledge of the second data by the user.
[0020] For the purposes of the invention, a “date” may designate an instant, an hour, a day, or any temporal measurement.
[0021] The invention also prevents the user from disclosing their initial data to users in the chain other than Oracle. The invention therefore protects the user's personal data.
[0022] However, it is possible that the publication step by the terminal also includes a publication of the first data.
[0023] In one embodiment, the attestation request method according to the invention further comprises a step of sending by the user, outside the blockchain, the first data to the trusted entity. This step of sending the first data, outside the blockchain, can be implemented via a communication network between the user's terminal and the trusted entity.
[0024] The first data can be sent, for example by a user terminal, in the form of a voice message or a text.
[0025] In one embodiment, the step of receiving the second data is implemented by a user terminal.
[0026] The steps of the method of requesting certification in accordance with the invention, sending the first data item, receiving the second data item, and publishing can be implemented by the same user terminal or by different user terminals.
[0027] In one embodiment, the certification request method according to the invention further comprises a step of sending to the trusted entity a request for the second data item. This request may include the first data item or an identifier allowing the trusted entity to identify the first data item. The second data item is received from the trusted entity in response to this request.
[0028] In another mode, the second data is received without a request having been sent. For example, the decision to send the second data is made by the trusted entity or by the Oracle.
[0029] In one embodiment, the step of publication by the terminal further comprises a publication of timestamp information of this publication. This timestamp information can be used by a third party who consults the blockchain to compare publication dates. However, the third party can find this publication date in the blockchain; it is therefore not necessary for this date to be published explicitly.
[0030] In one embodiment, the second data is published with the first data.
[0031] In another mode, the second data item is published in association with information making it possible to identify a type of the first data item, for example information of the type “this publication relates to a telephone number of Alice (Alice is the user and her telephone number is the first data item)”.
[0032] In one embodiment, this method of requesting certification in accordance with the invention further comprises a step of sending, outside the blockchain, to the trusted entity: a so-called publication date on which the terminal publication step is implemented; and / or a date range during which the trusted entity must publish the second data in the blockchain.
[0033] This mode ensures that the second data is published by the user's terminal before the trusted entity.
[0034] In one embodiment of the invention, the method for requesting certification in accordance with the invention further comprises a step of selecting one or more trusted entities registered in the blockchain.
[0035] This mode allows the user to choose which trusted entity(ies) they collaborate with to prove that they know the first piece of data. This mode also allows the user to choose the number of trusted entities.
[0036] The invention also relates to a method for proving knowledge of a first piece of data by a user registered in a blockchain, the first piece of data belonging to the user, this method being implemented by a trusted entity registered in the blockchain and comprising steps of: obtaining the first data item outside the blockchain; generating a second data item from the first data item; sending, outside the blockchain, the second data item to the user; publishing the second data item in the blockchain after a publication of the second data item in the blockchain by a terminal of the user.
[0037] Correlatively, the invention relates to a communication device, comprising a trusted entity registered in a blockchain, the device being configured to enable proof of knowledge of a first piece of data by a user registered in the blockchain, the first piece of data belonging to the user, the device comprising: communication means configured to obtain the first data outside the blockchain; a generation module configured to generate a second data item from the first data item; the communication means being further configured to send, outside the blockchain, the second data item to the user; and a publication module configured to publish the second data item in the blockchain after publication of the second data item in the blockchain by a terminal of the user.
[0038] The characteristics and advantages of this method for proving knowledge according to the invention presented below apply in the same way to the device according to the invention and vice versa.
[0039] The characteristics and advantages of the request method (and the terminal) according to the invention already presented apply in the same way to the method for proving knowledge and to the device according to the invention and vice versa.
[0040] Note that the trusted entity sends the second data to the user, this user being the holder of the first data. Thus, the publication of the second data by a terminal of the user before the trusted entity proves that the user has actually received the second data from the trusted entity. The user being the holder of the first data, has knowledge of this first data.
[0041] In one embodiment, the step of obtaining the first data item comprises receiving it from a user terminal.
[0042] In another embodiment, the step of obtaining the first data item comprises receiving an identifier allowing the trusted entity to identify the first data item.
[0043] In one embodiment, the device according to the invention sends the second data to a terminal of the user. In particular, this terminal may be different from the terminal from which the device received the first data. In other words, in this embodiment, the device received the first data from a first terminal of the user, and it sends the second data to a second terminal of the user.
[0044] In one embodiment, the device according to the invention implements an Oracle service.
[0045] In one embodiment, the second data sent to the terminal is a one-time password, generated using an OTP (One-Time Password) method. This password can be sent to a telephone number or an email or postal address of the user.
[0046] In another embodiment, the second data is generated by a hash or encryption of the first data and / or a random number generated by the trusted entity.
[0047] In one embodiment, the second data is a file signed with a private key of the trusted entity.
[0048] In one embodiment, the method for proving knowledge of the first data item further comprises a step of detecting the publication of the second data item in the blockchain by a terminal of the user. This detection step comprises reading blocks from the blockchain to detect the presence of the second data item. In this mode, the device according to the invention and comprising the trusted entity monitors the content of the data chain until the second data item is detected.
[0049] In one embodiment, the method for proving knowledge of the first data item further comprises a step of waiting for a publication date previously communicated by the user. This publication date may correspond either to the date on which the user plans to publish the second data item, or to the date on which he wishes the trusted entity to publish the second data item.
[0050] In one embodiment, the publication step is implemented by the device according to the invention following the detection of an addition of at least one block to the blockchain.
[0051] In another mode, the second data is published in association with information making it possible to identify a type of the first data, for example information of the type “this publication relates to a telephone number of Alice”.
[0052] In one embodiment, the publication steps, by the terminal and by the trusted entity deployed in the device, are implemented by methods identified in a smart contract deployed by the user of the terminal, this smart contract being able to further include addresses of the users authorized to invoke these methods.
[0053] For example, a "Publish Attribute" method that publishes the first data item is only allowed to be invoked by the user. A "Publish Server Attribute Proof" method that publishes the second data item generated by the trusted entity is only allowed to be invoked by the trusted entity. A "Publish User Attribute Proof" method that publishes the second data item after it has been received by the user is only allowed to be invoked by the user.
[0054] It should be remembered that a smart contract is an autonomous computer program, which once started, automatically executes conditions defined in advance and recorded in the blockchain (https: / / blockchainfrance.net / 2016 / 01 / 28 / applications-smart-contracts / ). For example, the decentralized dApps applications of the Ethereum project (registered trademark) constitute smart contracts within the meaning of the invention.
[0055] The invention also relates to a system for proving the knowledge of a first piece of data by a user registered in a blockchain. This system comprises at least one user terminal, this terminal being in accordance with the invention, and a device in accordance with the invention comprising a trusted entity. Of course, the system may comprise several user terminals, these terminals being in accordance with the invention, and a device in accordance with the invention comprising a trusted entity.
[0056] The invention also relates to a method for verifying the knowledge of a first piece of data by a user registered in a blockchain, the first piece of data belonging to the user, this method being implemented by verification equipment capable of consulting the blockchain and comprising steps of: detecting a publication in the blockchain by a terminal of the user of a second data item obtained from the first data item; detecting a publication of the second data item in the blockchain by a trusted entity registered in the blockchain; and verifying based on said publications whether the second data item is published in the blockchain by the terminal before being published by the trusted entity, the result of said verification making it possible to determine whether or not the user knew the first data item on a date prior to the dates of the publications.
[0057] Correlatively, the invention relates to equipment for verifying the knowledge of a first piece of data by a user registered in a blockchain, the first piece of data belonging to the user, the verification equipment being able to consult the blockchain and comprising: a detection module configured to detect in the blockchain: * a publication by a terminal of said user of a second piece of data; and * a publication of the second piece of data by a trusted entity registered in the blockchain, the second piece of data having been generated by the trusted entity from said first piece of data; and a decision module configured to verify, based on the publications detected, whether the second piece of data was published in the blockchain by the terminal before having been published by the trusted entity, the result of the verification making it possible to determine whether or not the user knew the first piece of data on a date prior to the dates of the publications.
[0058] The characteristics and advantages of the request method and the method for proving knowledge of the first data, in accordance with the invention, presented previously apply in the same way to the verification method and equipment according to the invention and vice versa.
[0059] According to the invention, when the result of the verification shows that the second data is published in the blockchain by the user's terminal before having been published by the trusted entity, the verification equipment determines that the user already knew the first data on a date prior to the dates of the publications (by the terminal and by the trusted entity).
[0060] Blocks published in the blockchain are immutable, so the verification time is not limited.
[0061] The invention also relates to a first computer program on a recording medium, this program being capable of being implemented in a computer or a terminal in accordance with the invention. This program comprises instructions adapted to the implementation of a request method as described above.
[0062] The invention also relates to a second computer program on a recording medium, this program being capable of being implemented in a computer or a device comprising a trusted entity in accordance with the invention. This program comprises instructions adapted to the implementation of a method making it possible to prove knowledge of the first data as described above.
[0063] The invention also relates to a third computer program on a recording medium, this program being capable of being implemented in a computer or verification equipment in accordance with the invention. This program comprises instructions adapted to the implementation of a verification method as described above.
[0064] Each of these programs may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.
[0065] The invention also relates to an information medium or a recording medium readable by a computer, and comprising instructions of the first or second or third computer program as mentioned above.
[0066] Information or recording media may be any entity or device capable of storing programs. For example, the media may include a storage medium, such as a ROM, for example a CD-ROM or a microelectronic circuit ROM, or a magnetic recording medium, for example a floppy disk or a hard disk, or a flash memory.
[0067] On the other hand, the information or recording media may be transmissible media such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio link, by wireless optical link or by other means.
[0068] The programs according to the invention can in particular be downloaded from an Internet-type network.
[0069] Alternatively, each information or recording medium may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of one of the methods according to the invention. Brief description of the drawings
[0070] Other characteristics and advantages of the present invention will emerge from the description given below, with reference to the appended drawings which illustrate an exemplary embodiment thereof without any limiting character. In the figures: there figure 1 is a flowchart representing steps of a request method and a method for proving knowledge of a first piece of data by a user on a given date, the methods being implemented according to a particular embodiment; the figure 2 is a flowchart representing steps of a verification method, implemented according to a particular embodiment; the figure 3 represents functional architectures, according to a particular embodiment, of a system, a terminal and a device; the figure 4 presents a functional architecture of a verification equipment in a particular embodiment; the Figure 5 presents a hardware architecture of a terminal according to a particular embodiment; the figure 6 presents a hardware architecture of a device according to a particular embodiment; and the figure 7 presents a hardware architecture of verification equipment according to a particular embodiment. Description of the embodiments
[0071] There figure 1is a flowchart representing steps of an attestation request method implemented by a terminal TA of a user A and steps of a method for proving the knowledge of a first data item ID by the user A, implemented by a device D comprising a trusted entity O; both methods being in accordance with the invention. The terminal TA and the device D are in accordance with the invention. The user A as well as the trusted entity O are registered in a blockchain CB. The first data item belonging to the user A, the user A has knowledge of the first data item ID.
[0072] Steps E10, E20, E60 and E70 described below are steps in the certification request process, implemented by the TA terminal.
[0073] In the mode described here, the trusted entity O is an Oracle.
[0074] Steps E30, E40, E50, E80 and E90 described below are steps of the method for proving knowledge of a first piece of data, implemented by the device D or by the trusted entity O.
[0075] During a step E10, the terminal TA deploys a smart contract SC, in which methods of publication in the blockchain to be used by the user A and by the trusted entity O are identified, as well as the addresses of the users authorized to invoke these methods. We note, however, that the deployment of a smart contract only presents a particular embodiment. The methods of the invention can be applied in other contexts, with other methods governing publications on the blockchain.
[0076] During this same step E10, the terminal TA selects the trusted entity O. Alternatively, the terminal TA can select several trusted entities.
[0077] During a step E12, the smart contract SC deployed in the blockchain sends a positive acknowledgment to the terminal TA to confirm the publication of this contract SC and returns the address of this contract, @SC.
[0078] The TA terminal receives this acknowledgment and addresses it @SC during a step E14.
[0079] During a step E20, the terminal TA sends outside the CB blockchain, the first ID data to the trusted entity.
[0080] In the mode described here, the first ID data is an attribute identifying user A, such as their phone number.
[0081] The E20 transmission outside the blockchain is done via a communication network between the terminal TA and the device D deploying the trusted entity. For example, this E20 transmission can be done via radio communication, or wired communication. No limitation is placed on the type of communication used to transmit the first data to the trusted entity.
[0082] In a particular embodiment, during step E20, the terminal TA also sends to the trusted entity O, the address @SC of the smart contract SC, the trusted entity O then being able to use it to publish data on the blockchain in accordance with methods of the contract SC.
[0083] During a step E30, the trusted entity O receives this first data ID, as well as, where applicable, the address @SC of the smart contract SC.
[0084] In another embodiment, the trusted entity O may be managed by a telephone operator to which the user A is subscribed. The trusted entity O may access a database containing subscriber identifiers and their telephone numbers. The user's terminal TA may send to the trusted entity O an identifier making it possible to obtain the user's telephone number, for example the user's first and last name or the number of their identity document. The trusted entity then obtains the first data item (the user's telephone number) by querying the database.
[0085] During a step E40, the trusted entity O generates a second data item P from the first data item ID.
[0086] The second data P can be associated with the date of its generation. It can be an OTP code, or data obtained by compressing the first data ID, or by encrypting the first data ID, or a file signed by a private key of the trusted entity of the Oracle type.
[0087] During a step E50, the trusted entity O sends outside the blockchain CB, the second data P to the user A.
[0088] When the second data P is an OTP code, the E50 sending can be done via a communication network and be intended for a telephone number, an e-mail address or a postal address of user A.
[0089] In the mode described here, this E50 sending is carried out via a communication network connecting the terminal TA to the device D.
[0090] During a step E60, the terminal TA receives via the communication network (outside the blockchain CB), the second data from the trusted entity O.
[0091] During a step E70, the terminal TA publishes on a date t1 the second data P in the block chain CB, using in the embodiment described the method mentioned in the smart contract SC. More precisely, the terminal TA transmits to the block chain a request to publish the second data P. The request is signed with the private key of the user A.
[0092] Alternatively, the TA terminal can use a classic method of publishing in the CB blockchain, without using the SC smart contract.
[0093] During a step E80, the trusted entity O detects the publication of the second data P by the terminal TA, by reading the blocks emitted in the block chain CB.
[0094] Following this detection, the trusted entity O in turn publishes, on a date t2, during a step E90, the second data P in the blockchain CB, according to the method mentioned in the smart contract SC.
[0095] In another embodiment, following the publication E70 of the second data P by the terminal TA, this terminal TA sends during a step E71 a notification to the device D to notify the trusted entity O of the publication E70. Upon receipt of this notification, the trusted entity O then publishes (E90) the second data P. More precisely, during the step E90, the trusted entity O transmits to the blockchain a request for publication of the second data P. The request is signed with the private key of the trusted entity O.
[0096] In another embodiment, for example during the sending step E20, the terminal TA sends to the device D a piece of data relating to a publication date (t1) on which the terminal TA intends to publish the second piece of data P. Upon receipt of this data, the device D monitors the occurrence of this date t1 over time (using a countdown counter for example) and in turn publishes (E90) the second piece of data P after the occurrence of this date t1 (at the expiry of the countdown counter).
[0097] In another embodiment, for example during the sending step E20, the terminal TA sends to the device D a piece of data relating to a publication date (t2) on which the device D must publish the second piece of data P. Upon receipt of this data, the device D monitors the occurrence of this date t2 over time (using a countdown counter for example) and publishes (E90) the second piece of data P at the occurrence of this date t2 (at the expiration of the countdown counter). Preferably, the device D verifies before this publication E90 that the second piece of data P has indeed been published (E70) in the block chain CB by the terminal TA.
[0098] In another embodiment, the device D verifies the publication of the data D in the blockchain by the terminal A, then waits for the publication of a predetermined number n of new blocks added to the blockchain before publishing (E90) the second data D. The number n can for example be equal to or greater than 3.
[0099] In case of a fork of the CB blockchain, the D device may only consider the number of blocks added to the main branch of the CB chain.
[0100] In the mode described with reference to the figure 1, the same terminal TA of user A implements the steps E20 of sending the first data item ID, E60 of receiving the second data item P and E70 of publishing the latter. Alternatively, these steps E20, E60 and E70 can each be implemented by a terminal of user A, different from the terminals implementing the other steps. For example, the sending step E20 is implemented by a first terminal of user A and the steps E60 of receiving the second data item P and E70 of publishing the latter are implemented by a second terminal of user A, the second terminal being different from the first terminal.
[0101] There figure 2 is a flowchart representing steps of a method for verifying the knowledge of the first data ID by the user A. This method is implemented by a verification device TB, the method and the device TB being in accordance with the invention.
[0102] In this mode, the verification equipment TB is registered in the CB blockchain. This equipment TB may be a terminal of a user B. However, to implement the verification method according to the invention, it is sufficient for the verification equipment to be capable of consulting the content of the CB chain, without being registered.
[0103] The TB device consults the publications in the CB blockchain.
[0104] During a step E72, the equipment TB detects the publication by the terminal TA of the second data P obtained (E30) from the first data ID.
[0105] During a step E92, the equipment TB detects the publication by the trusted entity O of the second data P.
[0106] In the mode described here, at least one of the publication steps E70 and E90 comprises, in addition to the publication of the second data item P, that of information on the type of the first data item ID, so that the equipment TB can determine that the second data item P was obtained from the first data item ID. For example, considering that the first data item ID comprises a telephone number of user A, one of the publications E70 or E90 also comprises information of the type “this publication relates to the telephone number of user A”.
[0107] By finding the same second data P in both publications E70 and E90, the verification equipment TB can deduce that they both (E70 and E90) relate to the same first data ID. Preferably, each of the publication steps E70 and E90 includes the publication of information on the type of the first data ID.
[0108] The detection steps E72 and E92 can be implemented simultaneously, or one after the other, regardless of the order in which they are implemented.
[0109] During a step E100, the verification equipment TB compares the dates of the publications, t1 and t2. In the example described with reference to the figure 1 , the date t1 is prior to the date t2; the TB equipment then determines that user A was aware of the second data and, consequently, of a first data item used to generate the first data item of the first data item ID on a date necessarily prior to the date t1 of the publication E70.
[0110] In another embodiment, during step E100, the verification equipment TB determines that the second data item P is recorded in two different blocks of the block chain CB, and that the second data item P published at the initiative of the terminal A was published in a block prior (according to the ordering of the blocks in the chain) to that in which the second data item P was published at the initiative of the trusted entity. For example, the second data item P published at the initiative of the trusted entity is published in a block concatenated to the chain CB located after a number n of blocks counted from the block in which the second data item P published at the initiative of the terminal A appears, n being greater than or equal to 3 for example. Thus, the verification equipment TB determines that the publication E70 is prior to the publication E90 and determines that the user A knew the first data item ID at the time when he published the second data item P.
[0111] There figure 3 represents functional architectures, according to an embodiment of the invention, of a system SYS, of the terminal TA and of the device D in accordance with the invention.
[0112] The SYS system includes the TA terminal and the D device.
[0113] User A is registered in the CB blockchain. The terminal TA comprises communication means COM configured to send (E20), outside the CB blockchain, the first data item ID to the trusted entity O, deployed by the device D and registered in the CB blockchain; these communication means are further configured to receive (E60), from the trusted entity O and outside the CB blockchain, the second data item P.
[0114] The terminal TA also includes a publication module PUB-A configured to publish, or more precisely request the publication, of the second data P in the blockchain CB. As described previously, the trusted entity O is configured to publish (E90) the second data P in the blockchain at a later date (t2) than that (t1) of the publication (E70) by the terminal TA.
[0115] Device D includes: COM communication means configured to receive (E30) the first data item ID from the terminal TA outside the CB blockchain; a generation module P_GEN configured to generate (E40) the second data item P from the first data item ID; said COM communication means being further configured to send (E50), outside the CB blockchain, the second data item P to the terminal TA; and a PUB-O publication module configured to publish (E90) the second data item P in the CB blockchain after a publication (E70) of the second data item P by a terminal TA of the user A.
[0116] In one embodiment, the device D further comprises a detection module DTC configured to detect (E80) the publication (E70) of the second data P in the block chain CB by a terminal TA of the user A. The publication module PUB-O is configured to publish the second data P after the detection (E80).
[0117] There figure 4 represents a functional architecture, according to an embodiment of the invention, of the TB verification equipment in accordance with the invention.
[0118] This TB equipment includes: a detection module DTC-B configured to detect (E72, E92) in the block chain CB: * the publication E70 by the terminal TA of the second data P; and * the publication of the second data P by the trusted entity O; and a decision module CMPR configured to check whether the second data P is published by the terminal TA before the trusted entity O, this module determines that the user A had knowledge of the first data ID on a date prior to the publication dates.
[0119] In the embodiment described here, the terminal TA, the device D and the verification equipment TB each have the hardware architecture of a computer, as illustrated in figures 5 to 7 .
[0120] The architecture of each of them (the terminal TA, the device D and the verification equipment TB) comprises in particular a processor 7, a random access memory 8, a read-only memory 9, a non-volatile flash memory 10 in a particular embodiment of the invention, as well as communication means 11. Such means are known per se and are not described in more detail here.
[0121] The read-only memory 9 of the terminal TA constitutes a recording medium in accordance with the invention, readable by the processor 7 and on which a computer program ProgA in accordance with the invention is recorded here.
[0122] The memory 10 of the terminal TA makes it possible to record variables used for the execution of the steps of the attestation request method as described previously, such as the first data item ID, the second data item P, possibly the address @SC of the smart contract SC, possibly the publication date t1 and / or the publication date t2.
[0123] The ProgTA computer program defines functional and software modules here, configured to request attestation of the first ID data. These functional modules rely on and / or control the hardware elements 7-11 of the TA terminal mentioned above.
[0124] The read-only memory 9 of the device D constitutes a recording medium in accordance with the invention, readable by the processor 7 and on which a computer program ProgO in accordance with the invention is recorded here.
[0125] The memory 10 of the device D makes it possible to record variables used for the execution of the steps of the method as described previously making it possible to prove the knowledge of the first data item ID by the user A of the terminal TA, such as the first data item ID, the second data item P, possibly the address @SC of the smart contract SC, possibly the publication date t1 and / or the publication date t2.
[0126] The computer program ProgO defines functional and software modules here, configured to enable user A to prove knowledge of the first data ID. These functional modules rely on and / or control the hardware elements 7-11 of the device D mentioned above.
[0127] The read-only memory 9 of the TB equipment constitutes a recording medium in accordance with the invention, readable by the processor 7 and on which a computer program ProgTB in accordance with the invention is recorded here.
[0128] The memory 10 of the TB equipment makes it possible to record variables used for the execution of the steps of the verification method as described previously, such as the second data P, the publication date t1, the publication date t2.
[0129] The computer program ProgTB defines functional and software modules here, configured to check the knowledge of the first data ID by the user A. These functional modules rely on and / or control the hardware elements 7-11 of the TB equipment mentioned above.
Claims
1. Method allowing knowledge of a first datum (ID) by a user (A) registered with a blockchain (CB) to be proven, said method being implemented by a trusted entity (O) registered on said blockchain and comprising steps of: - obtaining (E30) said first datum (ID) outside of said blockchain (CB); - generating (E40) a second datum (P) from said first datum (ID); - sending (E50), outside of said blockchain (CB), said second datum (P) to said user (A); and - publishing (E90) said second datum (P) on said blockchain (CB) after publication (E70) of the second datum in the blockchain by a terminal of the user.
2. Method according to Claim 1, further comprising a step of detecting publication of the second datum in the blockchain by a terminal of the user.
3. Method according to Claim 1, further comprising a step of waiting for a publication date communicated by said user or a step of waiting for detection of addition of at least one block to the blockchain.
4. Method for requesting certification from a trusted entity registered with a blockchain (CB) of knowledge of a first datum (ID) by a user (A) registered with said blockchain (CB), said method comprising steps of: - receiving (E60), outside of said blockchain (CB), from said trusted entity (0), a second datum (P) obtained from said first datum (ID), said trusted entity (O) having been apprised of said first datum (ID) outside of said blockchain (CB); and - publishing (E70), by means of a terminal (TA) of said user (A), said second datum (P) on said blockchain (CB) ; - sending, to the device (D) comprising said trusted entity (0): a notification, said notification being sent following publication of said second datum (P) in the blockchain by said terminal (TA); or a date (t1) of publication of said second datum (P) in the chain by said terminal (TA); said trusted entity being configured to publish (E90) said second datum (P) on said blockchain at a date (t2) subsequent to the date (t1) of publication (E70) of the second datum in the blockchain by the terminal of the user.
5. Method according to Claim 4, further comprising a step (E22) of sending, outside of said blockchain (CB), to said trusted entity (O): - a publication date on which the step of publishing by means of said terminal is implemented; and / or - a date range during which said trusted entity must publish said second datum (P) on said blockchain (CB).
6. Method according to either of Claims 4 and 5, further comprising a step (E10) of selecting at least one said trusted entity (O) registered on said blockchain.
7. Method according to any of Claims 1 to 6, wherein said publishing steps (E70, E90) are implemented by methods identified in a smart contract (SC) deployed by said user (A), the contract further possibly comprising addresses of users permitted to invoke these methods.
8. Method for verifying knowledge of a first datum (ID) by a user (A) registered with a blockchain (CB), said method being implemented by a verification equipment (TB) that is able to consult said blockchain (CB) and comprising steps of: - detecting (E72) publication on said blockchain (CB) by a terminal of said user (A) of a second datum (P) obtained from said first datum (ID); - detecting (E92) publication of said second datum (P) on said blockchain (CB) by a trusted entity (O) registered on said blockchain (CB); and - verifying (E100), depending on said detected publications, whether the second datum (P) was published in the blockchain by the terminal before it was published by the trusted entity, the result of said verification (E100) making it possible to determine whether the user knew the first datum (ID) or not at a date prior to the dates of the publications (E70, E90).
9. Computer program (ProgTA, ProgO, ProgTB) comprising instructions for executing: - steps of a method allowing knowledge of a first datum (ID) by a user (A) to be proven according to any of Claims 1 to 3 or 7; or - steps of the method for requesting certification according to any of Claims 4 to 7; or - steps of a verification method according to Claim 8 when said program is executed by a computer (TA, D, TB) .
10. Computer-readable recording medium on which a computer program according to Claim 9 is recorded.
11. Communication device, comprising a trusted entity (0) registered with a blockchain (CB), said device being configured to allow knowledge of a first datum (ID) by a user (A) registered on said blockchain to be proven, said device comprising: - communication means (COM) configured to obtain said first datum (ID) outside of said blockchain (CB); - a generation module (P_GEN) configured to generate a second datum (P) from said first datum (ID); - said communication means further being configured to send, outside of said blockchain (CB), said second datum (P) to said user (A); and - a publication module (PUB-O) configured to publish said second datum (P) on said blockchain (CB) after publication of the second datum in the blockchain by a terminal (TA) of said user (A).
12. Terminal (TA) of a user (A) registered with a blockchain (CB), said terminal being configured to request certification, from a trusted entity registered with the blockchain, of knowledge of a first datum (ID) by the user, said terminal (TA) comprising: - communication means (COM) configured to receive, from said trusted entity (D), outside of said blockchain (CB), a second datum (P) obtained from said first datum (ID), said trusted entity (O) having been apprised of said first datum (ID) outside of said blockchain (CB); and - a publication module (PUB-A) configured to publish said second datum (P) on said blockchain (CB) and to send, to a device (D) comprising said trusted entity: (i) a notification, said notification being sent following publication of said second datum (P) in the blockchain by said terminal (TA); or ii) a date (t1) of publication of said second datum (D) in the blockchain by said terminal (TA); said trusted entity being configured to publish said second datum (P) on said blockchain at a date (t2) subsequent to the date (t1) of publication of the second datum in the blockchain by said terminal (TA).
13. Equipment for verifying knowledge of a first datum (ID) by a user (A) registered with a blockchain (CB), said verification equipment being able to consult said blockchain (CB) and comprising: - a detection module (DTC-B) configured to detect: * publication on said blockchain (CB) by a terminal of said user (A) of a second datum (P); and * publication of said second datum (P) on said blockchain (CB) by a trusted entity (O) registered on said blockchain (CB), the second datum having been generated by the trusted entity from said first datum; and - a decision module (CMPR) configured to verify, depending on said publications, whether the second datum (P) was published in the blockchain by the terminal before it was published by the trusted entity, the result of said verification making it possible to determine whether the user knew the first datum (ID) or not at a date prior to the dates of the publications (E70, E90).
