FR3125661A1 - Process for enrolling a user by an organization on a blockchain - Google Patents

Abstract

The invention relates to a method of enrolling a user (1) by an organization on a blockchain, said method comprising: the communication by the user (1) of identity data to a platform (2) of said organization, as well as a digital address (3) of a digital safe (4) held by said user; the authentication of said user by said platform by comparison between the identity data communicated by said user and a digital fingerprint of said user stored in said safe; then, when the user (1) communicates electronic documents (16a, 16b, 16c) to finalize his enrollment: the recording of fingerprints of said electronic documents in a digital enrollment safe (18) held by the organization on the blockchain; the sending of said documents to the platform (2) of the organization, in order to allow verification of said documents by comparison with their fingerprints recorded in said enrollment safe. Figure 1

Description

Process for enrolling a user by an organization on a blockchain

The invention relates to a method for enrolling a user of a chain of blocks by an organization present on said chain of blocks, as well as an architecture comprising means for enabling the implementation of such a method.

When enrolling a user with an organization, for example a banking or financial institution, several levels of control must be validated. Indeed, it is necessary to first check the validity and completeness of the supporting documents provided by the user, then the validity of the signature made by said user, for example on a contract binding him to said organization.

This procedure is conventionally done in the physical presence of both parties, namely the user and an employee representing the organization, which significantly limits the risk of fraud, but has a number of drawbacks.

Indeed, in addition to requiring both parties to travel to a common location, the procedure can be slowed down if the user forgets proof(s), insofar as the latter must provide them. later, and thus make a new appointment with the organization.

In addition, the use of documents in paper format increases the risk of loss of said documents by the user and/or the organization, and the employee of the said organization must be particularly vigilant to avoid internal fraud or collusion, which is relatively complex and difficult to implement.

To facilitate the enrollment of their users, more and more organizations are thus using remote enrollment procedures, which is all the more relevant given the ever-increasing presence of IT tools in the field of economics.

This new method of enrollment presents significant challenges, both for an organization and for its users. Indeed, for an organization, remote enrollment must make it possible to:

• identify a user with a sufficiently high level of trust, and in particular compatible with the procedures of said organization;
• link the identity of this user with a digital signature making it possible to easily authenticate said user during his enrollment, and keep this link in memory for the duration of the contract and/or the collaboration between said user and said organization;
• memorize the sharing of each supporting document from the user to the organization;
• guarantee the user security during the transmission of his identity data and supporting documents, in particular by assuring said user that he is sharing this information with the right organization and/or that said information will not be communicated to others. other organizations.

Similarly, remote enrollment must allow a user to:

• simply send supporting documents in electronic form to an organization, while keeping track of this transmission;
• be able to simply update the supporting documents sent to the organization, in particular by sending a new type of document and/or a new version of a previous document that has become obsolete, for example a proof of residence with an old and/or linked date at a former address of said user;
• be able to check at any time the supporting documents sent to the organization and/or validated by the said organization.

The invention aims to improve the prior art by proposing in particular a method which, by means of a chain of blocks, allows a user to be enrolled by an organization in a simple, intuitive and secure manner, with the aforementioned advantages.

To this end, according to a first aspect, the invention proposes a method for enrolling a user of a chain of blocks by an organization present on said chain of blocks, said method providing:

• the communication by the user of identity data to a platform of said organization on the blockchain, as well as a digital address of a digital safe held by said user on the blockchain;
• the authentication of said user by said platform by comparison between the identity data communicated by said user and a digital fingerprint of said user recorded in said safe;

said process also providing, when the user communicates electronic documents to finalize his enrollment:

• the recording of fingerprints of said electronic documents in a digital enrollment safe held by the organization on the blockchain;
• sending said documents to the organization's platform, in order to allow verification of said documents by comparison with their fingerprints recorded in said enrollment safe.

According to a second aspect, the invention proposes an architecture for a chain of blocks, said architecture comprising:

• a terminal comprising means for allowing a user to communicate identity data and a digital address of a digital safe held by said user on the blockchain;
• a platform to allow an organization to enroll users on the blockchain, said platform comprising means for:
  • receive the identity data and the digital address communicated by the terminal;
  • authenticate the user of said terminal by comparison between the identity data communicated by said terminal and a digital fingerprint of said user recorded in said safe;

said terminal further comprising means for, when the user communicates electronic documents to finalize his enrollment:

• record fingerprints of said electronic documents in a digital enrollment safe held by the organization on the blockchain;
• send said documents to the platform, in order to allow verification of said documents by comparison with their fingerprints recorded in said enrollment safe.

Other particularities and advantages of the invention will appear in the following description, made with reference to the appended figures, in which:

schematically represents different steps of a method according to one embodiment of the invention;

schematically represents the recording structure of the alphanumeric sequences linked to each electronic document sent by a user in the digital enrollment safe;

schematically represents different steps for the creation of a digital enrollment safe by an organization on a blockchain.

In relation to these figures, a method for enrolling a user 1 of a chain of blocks by an organization present on said chain of blocks is described below, as well as an architecture comprising technical means suitable for setting implementing such a process.

The organization can be a company offering services, such as a company providing a telephone subscription, or a banking or financial institution. User 1 can also be a new customer wishing to benefit from at least one service provided by this organization, or a candidate for an employee and/or service provider position within said organization.

As represented in FIGS. 1 and 3, the architecture comprises a platform 2 to allow the organization to enroll users 1 on the blockchain, said platform being able in particular to be managed by at least one administrator 10 employed by said organization.

To perform the enrollment of a user 1 of the blockchain, the method initially provides for the communication by said user of identity data to the platform 2 of the organization, as well as a digital address 3 of a digital safe 4 held by said user on said chain of blocks.

To do this, the architecture comprises a terminal 5 which comprises means for allowing the user 1 to communicate his identity data and the digital address 3 of his safe 4, in particular by sending a notification 6 adapted, the platform 2 further comprising means for receiving said identity data and said digital address communicated by said terminal.

As shown in the figures, the terminal 5 can be a mobile phone of the "smart" type (for English "smartphone"). The terminal 5 can also be of another type, subject to being equipped with suitable means for the implementation of the method, in particular a digital tablet, a personal assistant (PDA, for English "Personal Digital Assistant") , laptop or desktop computer.

In particular, the architecture can include an application with suitable means for implementing the method, which the user 1 can download to install it on his terminal 5, in particular by sending a request adapted to said architecture.

To be able to interact with the blockchain, user 1 must first create a pair of public 7 and private 8 keys when first connecting to said blockchain. In particular, the private key 8 is kept secret by user 1, and the public key 7 allows said user to interact with the blockchain and/or another user to perform transactions.

To do this, the user 1 can launch a suitable procedure on his terminal 5, in particular by means of the application described previously. The keys 7, 8 are thus linked to the terminal 5, within which they are created under the control of the user 1. As a result, the private key 8 never leaves the terminal 5 of the user 1, which guarantees to the user optimal security.

To finalize his membership in the blockchain, user 1 then creates a digital safe 4 on the blockchain, in which the public key 7 and a digital fingerprint linked to the identity of said user are stored.

To do this, the architecture comprises a platform 9 for deploying safes on the blockchain, the terminal 5 or the application comprising means for interacting with said platform to create such a safe 4, in particular by sending a suitable request (not shown).

The digital safe 4 can in particular be created in the form of a computer protocol of the smart contract type, said smart contract being accessible on the block chain by means of a digital address 3 public.

The deployment platform 9 further comprises a programming interface (API, for English "Application Programming Interface"), said interface being adapted to allow the creation of safes on the chain of blocks.

Advantageously, the platform 9 is arranged to allow the automatic creation of digital safes 4, on simple request from a user 1 of the block chain. For this purpose, as shown in the , the architecture includes:

• a digital safe 11 linked to the deployment platform 9, in which is recorded at least one identifier of said deployment platform on the blockchain;
• a central digital safe 12, which includes in particular:
  • a list listing the platforms 9 for deploying safes belonging to a network of trusted platforms 9, in particular for the organization, said list comprising the digital addresses 13 of the safes 11 linked to each of these trusted platforms 9; And
  • a list listing all the digital safes 4 created by these trusted platforms 9, said list comprising entries which each contain the digital address 3 of a safe 4 created by a platform 9 associated with the address digital 13 of the safe 11 linked to this platform 9.

As a variant, the deployment platform 9 can be arranged to allow the manual creation of digital safes 4 by an administrator 10 of the blockchain, in particular following the receipt of a request by a user 1 of the blockchain .

After creating his digital safe 4, the user 1 can in particular authenticate his identity with a third-party platform (not shown) having the level of trust required by the organization, in order to create a digital fingerprint using data of identity provided by said third-party platform, said digital fingerprint then being recorded in said digital safe by the deployment platform 9.

The third-party platform has a level of trust that can be assessed within the framework of the eIDAS (Electronic IDentification And Trust Services) regulations, and can for example be a platform for providing a public identification service and/or administrative such as social security, a service for the payment of official taxes such as income tax, or any other identification service to achieve the required level of eIDAS confidence.

At the end of this recording, the deployment platform 9 communicates to the user 1 the public digital address 3 of the safe 4 thus created, in particular by sending a notification adapted to the terminal 5 of said user, in order to that said user can access said safe.

After communication of the notification 6 by the user 1, the method provides for the authentication of said user by the platform 2 of the organization, by comparison between the identity data communicated in the notification 6 and the digital fingerprint recorded in his safe 4.

In relation to the , the platform 2 comprises means for carrying out this authentication, in particular by interaction with the digital safe 4 of the user 1.

To this end, the platform 2 may include means for verifying the validity of the digital address 3, in particular by interaction with the central safe 12 to verify the identity and/or the validity of the deployment platform 9 having created the safe 4, as well as the validity and/or the level of security of the identity data communicated by the user 1.

The platform 2 further comprises means for calculating a digital fingerprint from the identity data communicated in the notification 6, in particular by using a suitable hash function, as well as means for interacting with the digital safe 4, in particular by sending a notification 14, in order to compare the digital fingerprint calculated by said platform with the digital fingerprint recorded in said safe, and thus verify the validity of the link between the identity data and the address number 3 present in the notification 6.

At the end of this authentication, the platform 2 sends to the terminal 5 a notification 15 to indicate to the user 1 the success or the failure of said authentication. In particular, if successful, the notification 15 also includes a request to ask the user 1 to send additional electronic documents 16a, 16b, 16c to finalize his enrollment.

The documents 16a, 16b, 16c to be provided may be electronic copies of official and/or administrative documents, for example chosen from the non-exhaustive list below:

• proof of identity (birth certificate, identity card, passport, driving licence, etc.); and or
• proof of address (recent telephone, electricity, water or gas bill, title deed, rent receipt, tax notice, etc.); and or
• a bank document, for example a bank account statement (RIB).

To obtain these electronic documents 16a, 16b, 16c, the user 1 can make a copy of a paper document by means of a suitable image capture device 17, for example a device integrated into his portable terminal 5, or a separate capture device such as a digital camera or scanner. User 1 can also download these electronic documents 16a, 16b, 16c from platforms linked to administrative services.

When the user 1 communicates electronic documents 16a, 16b, 16c to finalize his enrollment, the process provides:

• the recording of fingerprints 16a', 16b', 16c' of these electronic documents 16a, 16b, 16c in a digital enrollment safe 18 held by the organization on the blockchain;
• sending said documents to platform 2 of the organization, in order to allow verification of said documents by comparison with their fingerprints 16a', 16b', 16c' recorded in said enrollment safe.

To do this, the terminal 5 comprises means for, when the user 1 communicates electronic documents 16a, 16b, 16c to finalize his enrollment, record fingerprints 16a', 16b', 16c' of said documents in such a safe. enrollment 18, and send said documents in parallel to the platform 2 to allow this verification.

The method can provide beforehand for the automatic creation of an enrollment safe 18 for the organization by a deployment platform 9 as described above, upon request from said organization.

For this purpose, as shown in the , the organization's platform 2 comprises means for requesting the deployment platform 9, so that said deployment platform automatically creates an enrollment safe 18 for said organization.

In particular, an administrator 10 of the platform 2 can use a digital safe 19 linked to said platform to interact with the deployment platform 9, provided that said administrator has a public key 20 for access to the chain of blocks which has been previously saved in safe 19.

To obtain an authorization to act on the blockchain on behalf of the organization, the administrator 10 can create on his terminal 21 private 22 and public 20 access keys to the blockchain, then save the public key 20 thus created in the safe 19 linked to the platform 2 of said organization. Then, the digital address 23 of this safe 19 is communicated to the administrator 10, who can thus use said safe to interact with the blockchain.

In relation to the , to request the deployment of an enrollment safe 18 for the organization, an administrator 10 interacts with the platform 2 of said organization to access the safe 19 and send to the deployment platform 9 a request 24 comprising at less identification data of the platform 2 and the digital address 23 of said safe.

Upon receipt of this request 24, the deployment platform 9 automatically creates an enrollment safe 18 for the organization and saves therein the digital address 23 of the safe 19, in particular by sending a notification 25 adapted. Then, the deployment platform 9 sends to the platform 2 of the organization a notification 26 comprising the digital address 27 of the enrollment safe 18 thus created, in order to allow the organization to enroll users 1 in the means of said enrollment safe.

Advantageously, the administrator 10 can send via the platform 2 a request 28 to save this digital address 27 in a central safe 12 of the blockchain, in order to add the new safe 18 to a list of safes previously created by a trusted platform 9 known to the organization.

For this purpose, the request 28 may in particular include, in addition to the digital address 27 of the enrollment safe 18:

• the digital address 23 of the safe 19 used by the administrator(s) 10 of the platform 2 on the blockchain;
• identification data of the organization affiliated with the platform 2;
• the numerical address 13 of a safe 11 linked to the deployment platform 9 having created the enrollment safe 18.

Upon receipt of this request 28, the deployment platform 9 sends to the central safe 12 previously described a notification 29 to record therein the digital address 27 of the enrollment safe 18, associating it with the address digital 13 from his vault 11 on the blockchain. Then, the deployment platform 9 can inform the administrator 10 that the recording has been made, for example by sending a notification 30 adapted to the platform 2 of the organization.

Once the enrollment safe 18 has been created, the administrator 10 can interact with the platform 2 to update various configuration variables of said safe, in particular the list of identifiers of the administrators 10 and/or other employees 39 of the organization authorized to interact with said safe, for example by sending an appropriate notification 31.

In relation to the , the user 1 accesses the enrollment safe 18 via a specific electronic address provided by the organization, for example an address of the URL (Uniform Resource Locator) type, to which is linked the digital address 23 of said safe. To do this, the terminal 5 comprises means for launching a procedure 32 for reading this electronic address, in particular in parallel with the authentication of the user 1 with the platform 2.

The method can provide for sending the user 1 an electronic document at the end of his authentication, so that the user 1 electronically signs said document and records a fingerprint of said signed document in the enrollment safe 18 for validate his agreement for his enrollment with the organization, before communicating additional electronic documents 16a, 16b, 16c.

For this purpose, the platform 2 comprises means for sending to the terminal 5 such an electronic document after authentication of the user 1, in particular after the sending of the notification 15 of confirmation / request.

Also, as shown in the , the terminal 5 comprises means for allowing the user 1 to:

• electronically sign the document, in particular by means of a suitable application installed on the terminal 5, for example with a signature certificate provided by an application of the Adobe Acrobat Reader® type; And
• record an imprint of said signed document in the enrollment safe 18, in particular by sending an appropriate notification 33.

At the end of this registration, the user 1 downloads electronic documents 16a, 16b, 16c onto his terminal 5, for example by capturing paper documents or by connecting from said terminal to a third-party platform providing such documents , and communicates these documents 16a, 16b, 16c and their fingerprints 16a', 16b, 16c' on the blockchain via a suitable notification 34, in order to allow both:

• the recording of the fingerprints 16a', 16b', 16c' of these documents 16a, 16b, 16c in the enrollment safe 18;
• sending these documents 16a, 16b, 16c to platform 2.

In particular, the terminal 5 comprises means for creating an imprint 16a', 16b', 16c' of an electronic document 16a, 16b, 16c by means of a suitable hash function, then for recording this imprint 16a', 16b ', 16c in Enlistment Vault 18.

In relation to the , to facilitate the identification of the documents 16a, 16b, 16c and of their user 1, the method provides for recording each fingerprint 16a', 16b', 16c' in the enrollment safe 18 with an alphanumeric sequence 35a, 35b, 35c which is specific to it, said sequence comprising:

• a head part 36 (for English “Header”) linked to the enrollment safe 18;
• a central part 37 (for English “Body”) linked to the user 1; And
• a tail part 38a, 38b, 38c (for English “Footer”) linked to the registration rank of said fingerprint in said safe for said user.

To this end, the terminal 5 comprises means for recording each document imprint 16a', 16b', 16c' with such an alphanumeric sequence 35a, 35b, 35c. In particular, when registering a document fingerprint 16a', 16b', 16c', the terminal 5 interacts with the enrollment safe 18 to check the number of fingerprints 16a', 16b', 16c' previously recorded for user 1, and uses this number to calculate the tail part 38a, 38b, 38c of the alphanumeric sequence 35a, 35b, 35c of said new fingerprint, in particular by incrementing said number by 1.

The method can also provide for adding metadata to each electronic document 16a, 16b, 16c communicated by the user 1 to finalize his enrollment, said metadata comprising:

• at least part of the alphanumeric sequence 35a, 35b, 35c for recording the fingerprint 16a', 16b', 16c' of said document in the enrollment safe 18, in particular the central part 37 linked to the user 1 and the tail part, 38a, 38b, 38c specific to said imprint; And
• the digital address 27 of said enrollment vault on the blockchain.

To do this, the terminal 5 includes means for adding such metadata to an electronic document 16a, 16b, 16c to be communicated to the platform 2 of the organization.

The terminal 5 may include means for displaying a window for setting these metadata, in order to allow the user 1 to add additional metadata and/or to select a predetermined option for certain metadata. For example, terminal 5 can display to user 1:

• a suggestion of a name readable by a human (href, for English "Human Readable Reference"), to facilitate the subsequent identification of this document by an employee 39 of the platform 2, said name possibly referring in particular to the administrative type of the document 16a, 16b, 16c (identity card, invoice, etc.); and or
• a suggested name readable by a machine (mref, for English "Machine Readable Reference"), corresponding to a file number assigned to user 1 by the organization's platform 2.

The terminal 5 can also add other metadata relating to its geographical position and/or to the time period corresponding to the moment of the communication of the electronic document 16a, 16b, 16c to the platform 2.

Once the metadata has been selected by the user 1, the method can provide for validation by said user to communicate the electronic document 16a, 16b, 16c. To do this, the terminal 5 can display a window to allow the user 1 to validate the communication of the electronic document 16a, 16b, 16c, in particular by entering a password and/or by interaction with an interactive button on said window.

In particular, the method provides for automatically assigning each electronic document 16a, 16b, 16c a predetermined file name when it is sent to the platform 2, in order to facilitate its identification by said platform and its subsequent comparison with the fingerprint. 16a', 16b', 16c' recorded in enrollment vault 18.

To this end, when the user 1 validates the sending of an electronic document 16a, 16b, 16c, the terminal 5 can assign said document a file name composed from:

• the digital address 27 of the enrollment safe 18;
• at least the central 37 and tail 38a, 38b, 38c parts of the alphanumeric sequence 35a, 35b, 35c for recording the imprint 16a', 16b', 16c' of said document in said enrollment safe.

Advantageously, the method also provides for recording each fingerprint 16a′, 16b′, 16c′ in the enrollment safe 18 with an interactive link, for example an electronic address of the URL type, to allow the document to be downloaded. electronics 16a, 16b, 16c corresponding to the platform 2 of the body. To do this, the terminal 5 includes means for recording such an interactive link with each document imprint 16a′, 16b′, 16c′ in the enrollment safe 18.

Thus, an employee 39 of the platform 2 can easily retrieve an electronic document 16a, 16b, 16c for later verification, in particular in the event of failure to send said document by the terminal 5 and/or loss of said document at the level from platform 2.

As shown on the , the platform 2 is arranged to allow verification of the electronic documents 16a, 16b, 16c communicated by the user 1, in particular by comparison with the fingerprints 16a', 16b', 16c' recorded in the enrollment safe 18, in order to finalize the enrollment of the user 1. At the end of this check, the platform 2 sends to the terminal 5 a notification 40 to inform the user 1 of the success or the failure of his enrollment.

Platform 2 can perform some of these checks automatically. To do this, the platform 2 may in particular comprise means for:

• process an electronic document 16a, 16b, 16c sent by the terminal 5 with a suitable hash function;
• compare the electronic document thus processed with the imprint 16a', 16b', 16c' of this same document 16a, 16b, 16c previously hashed by the terminal 5 and recorded in the enrollment safe 18, in order to be able to access the metadata linked to said document in the event of success of said comparison.

The platform 2 can also include means to allow a human employee 39 to perform some of these checks, in particular using suitable functionalities provided by said platform. In particular, the employee 39 can access via the platform 2 the enrollment safe 18, in order to check:

• the validity of the electronic signature of the document attesting to the agreement of user 1 for his enrollment;
• the validity of the electronic documents 16a, 16b, 16c communicated by said user to finalize his enrollment.

The method further provides for recording each fingerprint 16a', 16b', 16c' in the enrollment safe 18 at least one chronological list L1, L2 of the evolution of a status of the electronic document 16a, 16b, corresponding 16c. To do this, the terminal 5 and/or the platform 2 of the body comprises means for recording and updating at least one such list L1, L2 for each fingerprint 16a', 16b', 16c'.

On the , each document imprint 16a', 16b', 16c' is recorded in the enrollment safe 18 with a first time-stamped list L1 relating to the evolution of a status of said document vis-à-vis the user 1. This L1 list may indicate in particular:

• the date and time of recording of the fingerprint of the document 16a', 16b', 16c' in the safe 18;
• the administrative and/or temporal validity of said document, for example by displaying a "valid" status code if this document 16a, 16b, 16c corresponds to a recent version of an administrative document, or an "obsolete" status code if said document corresponds to an old version of this same administrative document, in particular with a postal address and/or an issue date that is too old.

In this same figure, each document imprint 16a', 16b', 16c' is also recorded in the safe 18 with a second time-stamped list L2 relating to the evolution of a status of said document vis-à-vis the 'body. This L2 list may indicate in particular:

• if the document has been consulted and/or approved by automatic functionalities of the platform 2 and/or by a human employee 10, 39 of said platform;
• the administrative and/or temporal validity of said document, for example with code values similar to those of list L1.

Claims (14)

Method for enrolling a user (1) of a chain of blocks by an organization present on said chain of blocks, said method providing:

• the communication by the user (1) of identity data to a platform (2) of said organization on the blockchain, as well as a digital address (3) of a digital safe (4) held by said user on the blockchain;
• the authentication of said user by said platform by comparison between the identity data communicated by said user and a digital fingerprint of said user recorded in said safe;

said method further providing, when the user (1) communicates electronic documents (16a, 16b, 16c) to finalize his enrollment:

• recording fingerprints (16a', 16b', 16c') of said electronic documents in a digital enrollment safe (18) held by the organization on the blockchain;
• sending said documents to the organization's platform (2), in order to allow verification of said documents by comparison with their fingerprints (16a', 16b', 16c') recorded in said enrollment safe.

Method according to claim 1, characterized in that it provides for recording each fingerprint (16a', 16b', 16c') in the enrollment safe (18) with an alphanumeric sequence (35a, 35b, 35c) including:

• a head portion (36) linked to the enrollment vault (18);
• a central part (37) linked to the user (1); And
• a tail part (38a, 38b, 38c) related to the registration rank of said fingerprint in said vault for said user (1).

Method according to one of Claims 1 or 2, characterized in that it provides for recording each fingerprint (16a', 16b', 16c') in the enrollment safe (18) with at least one chronological list (L1, L2) of the evolution of a status of the corresponding electronic document (16a, 16b, 16c). Method according to any one of Claims 1 to 3, characterized in that it provides for sending the user (1) an electronic document at the end of his authentication, so that the user (1) signs electronically said document and records an imprint of said signed document in the enrollment safe (18) to validate its agreement for its enrollment with the organization. Method according to any one of Claims 1 to 4, characterized in that it provides for recording each fingerprint (16a', 16b', 16c') in the enrollment safe (18) with an interactive link for allow the downloading of the electronic document (16a, 16b, 16c) corresponding by the platform (2) of the body. Method according to any one of Claims 1 to 5, characterized in that it provides for adding metadata to each electronic document (16a, 16b, 16c) communicated by the user (1) to finalize his enrollment, said metadata comprising at least a part (37, 38a, 38b, 38c) of an alphanumeric sequence (35a, 35b, 35c) for recording the imprint (16a', 16b', 16c') of said document in the safe (18) and the digital address (27) of said enrollment vault on the blockchain. Method according to any one of Claims 1 to 6, characterized in that it provides beforehand for the automatic creation of the enrollment safe (18) by a deployment platform (9) on the blockchain upon request from the organism. Architecture for a blockchain, said architecture comprising:

• a terminal (5) comprising means for allowing a user (1) to communicate identity data and a digital address (3) of a digital safe (4) held by said user on the blockchain;
• a platform (2) to allow an organization to enroll users (1) on the blockchain, said platform comprising means for:
  • receiving the identity data and the digital address (3) communicated by the terminal (5);
  • authenticating the user (1) of said terminal by comparison between the identity data communicated by said terminal and a digital fingerprint of said user recorded in said safe;

said terminal further comprising means for, when the user (1) communicates electronic documents (16a, 16b, 16c) to finalize his enrollment:

• recording fingerprints (16a', 16b', 16c') of said electronic documents in a digital enrollment safe (18) held by the organization on the blockchain;
• sending said documents to the platform (2), in order to allow verification of said documents by comparison with their fingerprints (16a', 16b', 16c') recorded in said enrollment safe.

Architecture according to Claim 8, characterized in that the terminal (5) comprises means for recording each fingerprint (16a', 16b', 16c') in the enrollment safe (18) with an alphanumeric sequence (35a, 35b, 35c) comprising:

• a head portion (36) linked to the enrollment vault (18);
• a central part (37) linked to the user (1); And
• a tail part (38a, 38b, 38c) related to the registration rank of said fingerprint in said safe for said user (1).

Architecture according to one of Claims 8 or 9, characterized in that the terminal (5) and/or the platform (2) comprises means for recording in the enrollment safe (18) at least one chronological list ( L1, L2) of the evolution of a status of the corresponding document (16a, 16b, 16c) for each fingerprint (16a', 16b', 16c') recorded in said enrollment safe. Architecture according to any one of Claims 8 to 10, characterized in that the platform (2) comprises means for sending to the terminal (an electronic document following authentication of the user (1), said terminal comprising means to allow the user (1) to electronically sign said document and record an imprint of said signed document in the enrollment safe (18) to validate his agreement for his enrollment with the organization. Architecture according to any one of Claims 8 to 11, characterized in that the terminal (5) comprises means for recording each fingerprint (16a', 16b', 16c) in the enrollment safe (18) with a interactive link to allow the downloading of the document (16a, 16b, 16c) corresponding by the platform (2) of the organization. Architecture according to any one of Claims 8 to 12, characterized in that the terminal (5) comprises means for adding metadata to each electronic document (16a, 16b, 16c) communicated by the user (1) to finalize his enrollment, said metadata comprising at least a part (37, 38a, 38b, 38c) of an alphanumeric sequence (35a, 35b, 35c) for recording the imprint (16a', 16b', 16c') of said document in the enrollment vault (18) and the digital address (27) of said enrollment vault on the blockchain. Architecture according to any one of Claims 8 to 13, characterized in that it further comprises a platform (9) for deploying safes (4, 18) on the blockchain, the platform (2) comprising means for requesting said deployment platform, so that said deployment platform automatically creates a digital enrollment safe (18) for the organization.