Blockchain-based credential vault system

Abstract

Methods and systems for a blockchain-based credential vault system (CVS) are provided. In one novel aspect, the CVS identifies a set of credentials of a principal, validates each credential, and stores the validated credentials into a CVS blockchain database such that authorized beneficiaries can obtain the principal credentials from the CVS. In one embodiment, the CVS authenticates a principal request from a principal, wherein a principal record in the CVS is uniquely identified by a principal identification in a blockchain-based database of the CVS, processes a submission from the authenticated principal to generate a set of canonical credentials using a recurrent neural network (RNN) model, performs a credential validation for each generated canonical credential in the authenticated principal submission, and appends each validated canonical credential to the principal record in the blockchain-based database of the CVS.

Description

[0001] This application is a divisional application of Roxke Management Consulting Ltd., filed on January 7, 2021, with application number 202110018898.5, entitled "Blockchain-based Certificate Vault System". Technical Field

[0002] This invention relates generally to a credential verification system, and more specifically, to a blockchain-based credential vault system. Background Technology

[0003] Credential verification is a crucial part of the recruitment process. There is an over-reliance on credentials (such as academic qualifications) when determining hiring or promotion policies. Our society faces an imminent credential crisis. To understand this crisis, we must understand what credentialism and specialization are. Credentialism relies on formal qualifications or certifications to determine whether someone is permitted to perform a task, speak as an expert, or work in a specific field. Specialization is the social process of transforming any industry or profession into a truly “profession of the highest integrity and competence.” This process often involves establishing acceptable qualifications, creating professional bodies or associations to oversee the conduct of professional members, and drawing a certain line between unqualified amateurs and those who are not qualified. This creates a “hierarchical division between professional expertise and dignified citizens.” This division is often referred to as “occupational closure” because it means that the profession becomes inaccessible to outsiders, amateurs, and unqualified individuals: a “stratified profession” defined by occupational demarcation and hierarchy.

[0004] Diploma inflation (also known as academic inflation, degree inflation, and credential creep) is the inflation of the minimum credentials required to define a job, and the process by which diplomas and degrees simultaneously depreciate in value. Many jobs that traditionally did not require a college degree are now filled by college graduates. Diploma inflation has two drivers. First, for example, when the nature of a job changes and requires more education to enhance skills. Second, diploma inflation is caused by a mismatch between the supply and demand of educated workers. The Federal Reserve Bank of New York estimates that 34% of all college graduates are underemployed, meaning they are overqualified (in terms of academic qualifications) for current jobs. With so many graduates moving around, employers use degrees as a screening tool even when the jobs they are recruiting for do not require the knowledge an applicant acquired in college. There is growing criticism of education from society and industry, arguing that education is not sufficiently linked to work.

[0005] A direct consequence of diploma inflation is increased specialization. Regular secondary and higher education has been challenged by the rise of business and trade schools, business training courses, and the concentration of professionals. Furthermore, many professional certifications are established by law and are not offered in regular university courses. The scope of specialization ranges from physicians (MD, Specialization Committee) and engineers (IEEE, CPE) to vendor- or industry-specific qualifications such as accountants (CPA, CA), lawyers (lawyer qualifications), Certified Information Systems Security Professional (CISSP), Project Management Professional (PMI), Microsoft Azure Solutions Architect Certified Professional, Oracle Certified Professional, and so on. The last two are examples of vendor-specific and product-specific certifications. While university degrees and diplomas are permanent, many certifications have expiration dates. Certificate holders need to recertify through examinations, continuing education, or both.

[0006] Diploma mills and specialization are two thresholds employers use to hire the right candidates. Therefore, people exaggerate these to meet the growing demand for diplomas and professional certifications, leading to diploma inflation and certification inflation. Resume inflation is a generalization of both types of inflation. Resume inflation involves false or misleading information on a resume to make oneself a more attractive job candidate. Examples include adding degrees, certificates, awards never received, or jobs and positions never held.

[0007] Best practice is for companies to do their homework before hiring new employees. This due diligence doesn't begin with the interview process; rather, the best way to find the right person is to do research before granting them an initial interview.

[0008] Some improvements and enhancements are needed to provide a reliable credential verification system. Summary of the Invention

[0009] This invention provides a method and system for a blockchain-based Certificate Vault System (CVS). In one novel aspect, the CVS identifies a set of credentials belonging to a principal, verifies each credential, and stores the verified credentials in a CVS blockchain database, enabling an authorized beneficiary to obtain the principal's credentials from the CVS. In one embodiment, CVS authentication originates from a principal's request, where a principal record in the CVS is uniquely identified by a principal ID in the CVS's blockchain-based database. A recurrent neural network (RNN) model is used to process submissions from the authenticated principal to generate a set of canonical credentials. Credential verification is performed on each generated canonical credential from the authenticated principal's submission, and each verified canonical credential is appended to the principal record in the CVS's blockchain-based database. In one embodiment, the principal ID is at least one of a government-issued official identity card or a self-introduction video clip. In another embodiment, authentication is performed by image processing of a selfie of the principal and an official photo ID submitted by the principal via a CVS registration device. In one embodiment, the canonical credential is a verifiable credential based on an authenticated official record. In another embodiment, verification is performed based on the official record corresponding to the canonical credential in the submission. In yet another embodiment, there is no corresponding official record for the canonical credential in the submission, nor is there an authorization reference generated for the canonical credential. In one embodiment, the authorization reference is an instruction returned to the principal, which includes a direct link to obtain the corresponding official record for the canonical credential. In another embodiment, the authorization reference triggers bot verification by CVS. In one embodiment, bot verification by CVS uses at least one query process including automated email communication and chatbot voice queries. In another embodiment, bot verification also includes an RNN process that performs Natural Language Processing / Natural Language Understanding (NLP / NLU) on one or more responses to the query process. In one embodiment, the blockchain-based database includes a credential vault blockchain and a private InterPlanetary File System (IPFS). In another embodiment, the assets associated with the canonical credential are stored in the private IPFS, and the asset IDs of the assets are appended to the credential vault blockchain.

[0010] Other embodiments and advantages are described in the following detailed description. This summary is not intended to limit the invention. The invention is defined by the claims. Attached Figure Description

[0011] The accompanying drawings illustrate embodiments of the invention, wherein the same reference numerals denote the same components.

[0012] Figure 1An exemplary diagram is shown of a blockchain-based credential verification system (CVS) with interfaces to the principal, beneficiary, and issuer, according to an embodiment of the present invention.

[0013] Figure 2 An exemplary block diagram of the high-level architecture of a voucher system according to an embodiment of the present invention is shown.

[0014] Figure 3 An exemplary flowchart for a submission and verification procedure according to an embodiment of the present invention is shown.

[0015] Figure 4 An exemplary flowchart for a principal ID verification procedure according to an embodiment of the present invention is shown.

[0016] Figure 5 An exemplary flowchart for credential verification using CVS according to an embodiment of the present invention is shown.

[0017] Figure 6 An exemplary diagram illustrating the use of CVS to verify robot credentials with the issuer according to an embodiment of the present invention is shown.

[0018] Figure 7 An exemplary diagram is shown for an authorization process for issuing principal records and / or credentials using CVS, according to an embodiment of the present invention.

[0019] Figure 8A An exemplary block diagram of a credential vault blockchain database with IPFS according to an embodiment of the present invention is shown.

[0020] Figure 8B An exemplary block diagram of the data structure of asset records and request records in a CVS database according to an embodiment of the present invention is shown.

[0021] Figure 9 An exemplary flowchart of a credential verification procedure for using a credential vault system according to an embodiment of the present invention is shown. Specific Implementation

[0022] Reference will now be made in detail to some embodiments of the invention, examples of which are shown in the accompanying drawings.

[0023] Due diligence is a demanding and lengthy process that must be undertaken with every new job opening, especially for higher-level positions. Ideally, the person who obtains the credentials should be responsible for them. However, most of the time, applicants must rely on a third party (such as a university or employer) to retain, verify, and confirm their credentials. Job seekers must request official transcripts from university registrars and pay a fee for each requested copy. Employers and universities sometimes still need to call the issuing authority to verify the transcripts. This is complex and tedious and is one of the main factors contributing to fraud. Making credentials easy to verify and transfer is an advantage of digital systems. For job seekers, providing the authenticity of the items listed on their resumes can help expedite the due diligence process in the hiring process, thus leading to better interview opportunities. The advantage of a credential vault system is that it provides job seekers / principals and beneficiaries / requesters with a transparent, immutable, and secure repository of credentials from the issuer.

[0024] Figure 1 An exemplary diagram of a blockchain-based credential verification system (CVS) with interfaces to a principal, beneficiary, and issuer, according to an embodiment of the present invention, is shown. CVS 110 includes one or more network interfaces 111, one or more user interfaces 112, an authentication module 113, a processing module 114, a verification module 115, and a database interface 116. CVS database 120 includes a CVS blockchain 121 and an InterPlanetary File System (IPFS) 122, and interacts with CVS 110. A collection of verified, standardized credentials for a corresponding principal 130 is stored in CVS database 120. CVS 110 interacts with a principal 150, a beneficiary 160, an issuer 170, and a web / social media network 180.

[0025] Principal 150 comprises a group of principals who have created accounts and corresponding principal records in CVS 110. Principal 150 interacts with CVS 110 via a user interface and / or a network connection. Each principal in Principal 150 has a principal identifier (ID) associated with a corresponding principal record. Principals submit descriptions of credentials to CVS 110. Credential descriptions can be in various formats, including resumes, plain text files, images, and canonical credential descriptions in CVS format. CVS 110 processes the credential descriptions submitted by the principals and generates corresponding canonical credentials for verification. Principal 150 also interacts with issuer 170 to obtain validation for the corresponding credentials, such as certifications and diplomas. These validations are submitted to CVS 110.

[0026] Beneficiary 160 includes a group of beneficiaries who interact with CVS 110 via a user interface and / or network connection. Beneficiaries submit requests to access one or more authorized principal records and / or to verify one or more credentials of one or more principals. In one embodiment, a beneficiary submits a job description to CVS 110. CVS 110 processes the job description and generates a set of required, standardized credentials based on it. In one embodiment, CVS 110 uses a deep learning-based process to generate the set of standardized credentials based on the job description. Beneficiaries do not contact issuer 170 and can immediately obtain verification of the candidate's credentials through CVS.

[0027] In a novel aspect, a blockchain-based credential vault system verifies a principal's identity, credentials, work experience, and experience. Once verified, the information is stored in the blockchain as a single source of truth. The blockchain-based CVS allows a principal to publish their identity, credentials, and work experience (JHE) to an authorized beneficiary to obtain the entire credential record or a subset of verified credentials. In one embodiment, CVS 110 includes one or more network interfaces 111, an authentication module 113, a processing module 114, a verification module 115, and a database interface 116. One or more network interfaces 111 connect the system to social media networks. The authentication module 113 authenticates principal requests from principals, where the principal record in the CVS is uniquely identified by a principal identifier in the system's blockchain-based database. The processing module 114 uses a recurrent neural network (RNN) model to process submissions from authenticated principals to generate a set of canonical credentials. The verification module 115 performs credential verification on each generated canonical credential from the authenticated principal's submission. Database interface 116 attaches each verified, canonical credential to the principal record in CVS's blockchain-based database.

[0028] In one embodiment, the CVS database 120 and the verified, specification credentials 130 are components of the CVS 110. In another embodiment, the CVS database and the verified, specification credentials 130 run on different platforms. In still other embodiments, the CVS modules and components run on one or more processors or on different networked devices and communicate with each other via predefined network messages. In other embodiments, functionality may be implemented in software, firmware, hardware, or any combination thereof.

[0029] Figure 2An exemplary block diagram of the high-level architecture of a credential vault system according to an embodiment of the present invention is shown. The credential vault system has two main components: a principal module 210 and a verification module 220. The principal module 210 includes entities for identity submission 211, credential submission 212, credential retrieval 213, job history and experience submission 214, and authorization for issuance 215. In one embodiment, the principal module 210 receives input from one or more principals via a user interface or network connection. The principal module 210 processes the principal input and passes it to other components of the CVS. In one embodiment, entity 211 of the principal module 210 enables a principal to submit their identity to the CVS for verification. Entity 212 of the principal module 210 enables a principal to submit possessed credentials, such as photocopies of credentials. Entity 214 of the principal module 210 enables a principal to submit job history and experience (JHE). In one embodiment, entity 214 uses an RNN process that performs Natural Language Processing / Natural Language Understanding (NLP / NLU) to process the JHE submitted by the principal in plaintext or CV form. Entity 214 generates a set of canonical credentials based on the submissions from the principal. In another embodiment, entity 214 provides the principal with a formatted form to provide the JHE in a canonical credential format. In one embodiment, entity 213 of the principal module 210 provides the principal with a credential reference to obtain credentials, such as for payment and downloading a digital copy from the issuer. Entity 213 uses data mining to obtain the credential reference for verification based on the submissions provided by the principal.

[0030] In one embodiment, each principal's record has hierarchical settings for authorization to be published. Authorization includes publication of the entire record, publication of individual credentials, searchability level settings, and black / white lists. Entity 215, the principal, can also authorize the publication of his identity, credentials, work experience, and expertise to one or more beneficiaries. In one embodiment, the level of authorization differs for different beneficiaries. In another embodiment, the principal automatically matches authorizations based on one or more anticipated job vacancies.

[0031] The verification module 220 has three sub-modules / entities: the identity verification entity 221, the credential verification entity 222, and the work experience verification entity 223. The verification module 220 performs verification for each credential in the principal's record. The verification module 220 interacts with the CVS database to attach the verified credential to the corresponding principal's record.

[0032] The CVS blockchain 230, featuring the InterPlanetary File System (IPFS) 240, serves as the final storage for principal information. Three fundamental AI machine learning algorithms 250 are used to support specific operations. Module 251 is Automatic Speech Recognition (ASR) based on a Recurrent Network (RNN) deep learning model, trained to convert speech to text. Module 252 is another RNN deep learning model trained to perform NLP / NLU to understand text. Finally, a face recognition 253 based on a Deep Neural Network (DNN) / Convolutional Neural Network (CNN) is trained for facial recognition. These tools are used to automate the verification process.

[0033] Figure 3 An exemplary flowchart of a submission and verification procedure according to an embodiment of the present invention is shown. The Submit Identity process 311 allows the principal to submit their identity and personal information. A genuine identity is the backbone of CVS. The Verify Identity process 312 verifies the submitted principal's identity. Once the principal's identity is verified, it is stored in the blockchain. Only after the principal's genuine identity has been verified can other credentials be submitted, and work experience and experience for verification are submitted in Credentials & Work Experience and Experience (JHE) Verification 350. The Submit Credentials process 351 receives credentials submitted by the principal, such as university diplomas, certificates from professional bodies, etc. Since the credentials are uploaded by the principal, CVS will conduct a comprehensive process to verify the credentials in process 361. The Obtain Credentials process 352 facilitates the principal's acquisition of credentials. In one embodiment, the Obtain Credentials process 352 provides the principal with a credential reference. For example, the credential reference provides the principal with a paid download link to request a certificate for the credential. In one embodiment, the credential reference is obtained by the Obtain Credentials process 352 based on the credential specification to be verified. CVS will integrate with the most popular issuers for smooth integration. For example, if the issuer provides an API (Web service), the credential acquisition process 352 enables the principal to log in to the issuer's service and download credentials. Process 322 then attaches the acquired credentials and the verified credentials to the blockchain data storage.

[0034] Process 353 receives the JHE from the principal. In one embodiment, process 353 generates a set of regulated credentials based on the received JHE. For each JHE, or for each regulated credential generated from a JHE, process 362 performs verification. Process 323 appends the positive or negative verification result to the blockchain in the transaction / request record. Once a JHE is recorded in the blockchain, it cannot be altered. Any update to a JHE becomes a new transaction and is appended to the blockchain.

[0035] Figure 4An exemplary flowchart of a client ID verification procedure according to an embodiment of the present invention is shown. To ensure the client's identity, CVS employs a multi-faceted verification method. In step 410, the client's identity (e.g., a government-issued ID card, personal information, and a self-introduction video) is submitted to CVS. A device registered in CVS is used to associate the client's selfie and their official photo ID (410) with the client's account. In one embodiment, photos and videos from the client's social media are collected in process 430. In step 420, in addition to collecting the client's face from social media, image extraction algorithms such as image segmentation are used to extract the client's face from the selfie, self-introduction video, and photo on the government-issued ID card. These images are then passed to a facial recognition deep learning model 440. The facial recognition model authenticates the client and the submission made by the client. In one embodiment, the self-introduction video and audio are processed and stored in CVS as part of the client's account, for example, as login credentials via facial recognition and / or voice recognition.

[0036] Figure 5 An exemplary flowchart for credential verification using CVS according to an embodiment of the present invention is shown. Process 510 locates the issuer of the credential. In step 520, CVS determines whether a photocopy or other form of authentication of the credential is included in the principal's submission. If a photocopy of the credential is identified in the principal's submission, process 521 extracts the credential details from the photograph. Many issuers offer online verification processes. If step 520 determines "No," it means the credential is in some free text format, i.e., a canonical form. Then, in step 530, CVS determines whether the issuer provides an online service for verification. When the issuer's service is available, CVS interfaces with the issuer's service via the issuer's API. If step 530 determines "Yes," process 531 uses the obtained API to verify the credential. The verification results are sent to process 552 to be recorded in the blockchain. The verification result, whether verified or rejected, is appended to the request record in the database. If the credential is verified, the credential, along with the verification, is appended to the asset record in the database. If the issuer does not provide any verification API, contact the issuer through process 551 (i.e., the robot credential verification process) to further perform the verification process.

[0037] Figure 6An exemplary diagram illustrating bot credential verification with an issuer using CVS according to an embodiment of the present invention is shown. When verification is required by contacting the issuer, CVS provides bot verification for credentials based on identified specifications from official records. In process 613, one or more credentials based on official records are identified. Process 611 obtains credential details and creates a verification script and email. In one embodiment, a deep learning model 612 is used to generate the verification script. CVS determines one or more verification methods for bot credential verification, including a bot chatbot 621 and / or email 622. Bot program 631 enables the bot verification process based on the generated script. Email responses and / or chatbot audio responses are extracted by process 632 and analyzed by process 633. If the response is a phone message or chatbot dialogue, in step 634, the audio is converted to text using a speech-to-text RNN model. Then, in 633, the converted text is analyzed, where the RNN performs NLP / NLU on the text. The results from both the email and / or audio are combined. The result of verification or rejection is appended to the CVS request record. In step 650, one or more verified credentials are attached to the asset record in the CVS database.

[0038] In other embodiments, JHE credentials are verified using bot verification similar to that based on officially recorded credentials. Once the issuer, employer, or any verifier of the JHE credential is identified, a chatbot script and / or email script are generated. The response is analyzed using a DNN / RNN NLP / NLU model. In one embodiment, JHE verification is based on social media information and peer confirmation.

[0039] Figure 7 An exemplary diagram illustrating an authorization process for issuing principal records and / or credentials using CVS according to an embodiment of the present invention is shown. A principal may authorize the issuance of his credentials and JHE to a beneficiary. CVS provides two services: (1) authorizing the beneficiary to access the principal's profile if the beneficiary is granted privileges, and (2) sending a “notarized” or authenticated copy of the credentials to the beneficiary. Sending a copy of the credentials can be initiated by both the beneficiary and the principal. If it is initiated by the beneficiary, then it requires the principal's approval. Alternatively, a principal may directly authorize the issuance of a copy of the credentials to the beneficiary. For example, a principal authorizes CVS to send his university diploma and transcripts to multiple graduate schools for admissions.

[0040] Beneficiary 710 can request access to one or more delegator records by sending an access request in process 711. Beneficiary 710 can also request a copy of the delegator's credentials in process 712. Upon receiving one or more requests from Beneficiary 710, CVS identifies the requested one or more delegators and stores the corresponding request transaction in the request record of each corresponding delegator in the CVS blockchain database. After determining that the request from the beneficiary is authorized, CVS sends an authenticated copy of the credentials to the beneficiary in process 771.

[0041] Upon receiving a request from the beneficiary, in process 731, CVS 730 first appends the request transaction to the blockchain. In process 751, CVS 730 notifies the principal 720 of the request. In one embodiment, notification process 751 checks the principal's record with access / privacy settings. In another embodiment, CVS processes the request from the beneficiary and detects authorization information. In yet another embodiment, notification or response regarding the beneficiary's request is received from the principal 720. CVS 730 analyzes one or more access information for the request and determines whether the request is granted or denied, as in process 721. If CVS 720 determines that the beneficiary's request is denied, CVS 720 appends a request denial transaction to the blockchain in step 732 and sends a notification to the beneficiary in step 772. If the principal 720 determines that the beneficiary's request is granted, and if the request is a credential for accessing the principal in CVS, the approved request is appended to the blockchain in step 733, and CVS 720 sends a notification to the beneficiary in step 772. If the approved request is for a certified copy of the credentials, then in step 771, CVS720 sends the certified copy to the beneficiary and attaches the sending transaction to the blockchain.

[0042] Figure 8AAn exemplary block diagram of a credential vault blockchain database with IPFS according to an embodiment of the present invention is shown. CVS includes two main storage technologies, a referral blockchain 800 and a private InterPlanetary File System (IPFS) 810. IPFS is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content addressing to uniquely identify each file. It uses cryptographic techniques to provide decentralized and tamper-proof storage. In CVS, ledger 801 is used to maintain the identity of the principal, his / her assets, and requests from both the principal and the beneficiary. Smart contracts 802 are built on the distributed ledger 801. Because distributed ledgers allow multi-party and shared use, they can be equipped with multi-party business logic, which is more commonly referred to as "smart contracts". Requests 822 from the beneficiary to access the principal and the corresponding assets are maintained in the request record. The principal's identity data (including corresponding personal information, a copy of his / her ID card, a selfie, and an introductory video) is managed by the asset recording procedure 821.

[0043] Module 821 includes Attached Identity, Attached Certificate, and Attached JHE. When the principal's identity is verified, the module stores identity documents such as a photocopy of their official ID in IPFS 810. IPFS 810 returns the hash address of their official ID. The hash address is the principal's ID stored in the blockchain's ledger. Other supporting documents, such as selfies and introductory videos, are also stored in IPFS 810. In return, their hash addresses are stored as asset IDs in blockchain 800. For each verified credential, credential information (e.g., a photocopy of a diploma, certificate) is stored in IPFS 810. The corresponding hash address is the asset ID. Similarly, credential information for work experience and qualifications (JHE) is stored in IPFS 810. The hash address of each JHE credential is the asset ID. Module 822 records beneficiary request records in the CVS database. Module 822 executes Attached Request transactions, Attached Request Rejections, Attached Request Approvals, and Attached Sending Credentials.

[0044] Figure 8B An exemplary block diagram illustrating the data structure of asset records and request records in a CVS database according to an embodiment of the present invention is shown. The blockchain ledger is a linked list of transactions supporting CVS. The principal's data structure 851 supports different types of entries. The beneficiary's identity and profile can be included as needed. Depending on the type of transaction, such as identity, asset (e.g., credentials and JHE), and request, the structure will include relevant data. An exemplary asset record 852 includes an asset ID, status, and timestamp. The asset ID is a hash address of the asset data stored in IPFS. An exemplary request record 853 includes a request ID, asset ID, status, and timestamp. The requester ID is the beneficiary ID.

[0045] Figure 9 An exemplary flowchart of a credential verification procedure for using a credential vault system according to an embodiment of the present invention is shown. In step 901, CVS authenticates a principal request from a principal, wherein the principal record in CVS is uniquely identified by a principal identifier in CVS's blockchain-based database. In step 902, CVS processes the submission from the authenticated principal using a recurrent neural network (RNN) model with natural language processing / natural language understanding (NLP / NLU) to generate a set of canonical credentials. In step 903, CVS performs credential verification on each generated canonical credential from the authenticated principal submission. At step 904, CVS appends each verified canonical credential to the principal record in CVS's blockchain-based database.

[0046] Although the invention has been described in conjunction with certain specific embodiments for illustrative purposes, the invention is not limited thereto. Therefore, various modifications, adaptations, and combinations of the various features of the described embodiments may be practiced without departing from the scope of the invention as set forth in the claims.

Claims

1. A method for implementing a blockchain-based vault, comprising: A principal request from a principal is authenticated by a credential vault system (CVS), the CVS having one or more processors coupled to at least one memory unit, and the principal record in the CVS is uniquely identified by a principal identifier in the CVS’s blockchain-based database; A recurrent neural network (RNN) model with natural language processing / natural language understanding (NLP / NLU) is used to process submissions from an authorized client, the submissions being credential descriptions in various formats to generate a set of canonical credentials, which are verifiable credentials based on official records verified by the authorized official records, wherein there is no corresponding official record for the canonical credentials in the submission, and wherein an authorization reference is generated for the canonical credentials, wherein the authorization reference is an instruction returned to the client, the instruction including a direct link to the corresponding official record for the canonical credentials; For each generated, standardized credential submitted by the certified client, credential verification is performed based on the official record corresponding to the standardized credential in the submission. The client's identity is submitted to CVS, and a device registered in CVS is used to associate the client's selfie and official photo ID with the client's account. as well as Each verified, canonical credential is attached to the principal record in the CVS’s blockchain-based database, which includes the credential vault blockchain and the private InterPlanetary File System (IPFS). Assets associated with the canonical credential are stored in the private IPFS, and the asset IDs of the assets are attached to the credential vault blockchain. CVS identifies a set of delegator credentials, verifies each credential, and stores the verified credentials in the CVS blockchain database, enabling authorized beneficiaries to obtain delegator credentials from CVS. Each delegator record has hierarchical settings for authorization to be issued.

2. The method according to claim 1, wherein the client ID is at least one of an official ID card issued by the government or a self-introduction video clip.

3. The method according to claim 1, wherein the authorized reference triggers the robot verification of the CVS.

4. The method of claim 3, wherein the robot verification performed by the CVS uses at least one query process including automated email communication and chatbot voice query.

5. The method of claim 4, wherein the robot verification further comprises an RNN process that performs natural language processing / natural language understanding (NLP / NLU) on one or more responses to the query process.

6. The method of claim 1, wherein each principal record has hierarchical settings for authorization to be published, the authorization including publication of the entire record, publication of personal credentials, searchability level settings, and black / white lists.

7. A blockchain-based vault system, comprising: One or more network interfaces that connect the system to social media networks; An authentication module that authenticates client requests from clients, wherein client records in CVS are uniquely identified by client identifiers in the system’s blockchain-based database; The processing module uses a recurrent neural network (RNN) model with Natural Language Processing / Natural Language Understanding (NLP / NLU) to process submissions from an authenticated principal, the submissions being credential descriptions in different formats to generate a set of canonical credentials, the canonical credentials being verifiable credentials based on an authenticated official record, wherein there is no corresponding official record for the canonical credentials in the submission, and wherein an authorization reference is generated for the canonical credentials, wherein the authorization reference is an instruction returned to the principal, the instruction including a direct link to obtain the corresponding official record for the canonical credentials; The verification module performs credential verification on each generated, standardized credential submitted by the authenticated principal. as well as The database interface module appends each verified, standardized credential to the principal's record in the CVS blockchain-based database. CVS identifies the principal's set of credentials, verifies each credential, and... Verified credentials are stored in the CVS blockchain database, enabling authorized beneficiaries to obtain delegator credentials from CVS. Each delegator record has hierarchical settings for authorization to be published, including publication of the entire record, publication of individual credentials, searchability level settings, and black / white lists.

8. The system of claim 7, wherein the canonical credential is an officially verifiable credential based on an authenticated official record.

9. The system of claim 8, wherein the verification is performed based on an official record corresponding to the credentials specified in the submission.

10. The system of claim 7, wherein the authorized reference triggers robot verification of the CVS.

11. The system of claim 10, wherein robot verification further comprises an RNN process that performs natural language processing / natural language understanding (NLP / NLU) on one or more responses to the query process.

12. The system of claim 7, wherein the blockchain-based database comprises a vault blockchain and a private interplanetary file system (IPFS).

Images