Identity verification using computer-implemented decentralized ledger

A system comprising:

• at least one data processor;
• and
• memory storing instructions which, when executed by the at least one data processor, result in operations comprising:
• receiving data encapsulating a request to verify an identity of a user, the request including user-provided identification data;
• hashing the user-provided identification data;
• traversing a decentralized ledger including a data structure comprising a plurality of linked segments to identify a match of the hash of the user-provided identification data;
• and
• providing verification data either (i) confirming the identity of the user if the hash of the user-provided identification data has a match in the decentralized ledger, or (ii) rejecting the identity of the user if the hash of the user-provided identification data does not have a match in the decentralized ledger;
• wherein:
• hashes forming part of the decentralized ledger that have been verified by one of a plurality of verifiers have, within a same segment of the decentralized ledger, an associated verification of hash comprises the corresponding hash, a signature of the corresponding hash signed with a private key of the verifier, and a public key of such verifier;
• and
• hashes forming part of the decentralized ledger not having an associated verification of hash indicate that the identity of the corresponding user has not been verified.

A non-transitory computer program product storing instructions which, when executed by at least one data processor forming part of at least one computing device, result in operations comprising:

• receiving data encapsulating a request to verify an identity of a user, the request including user-provided identification data;
• hashing the user-provided identification data;
• traversing a decentralized ledger including a data structure comprising a plurality of linked segments to identify a match of the hash of the user-provided identification data;
• and providing verification data either (i) confirming the identity of the user if the hash of the user-provided identification data has a match in the decentralized ledger, or (ii) rejecting the identity of the user if the hash of the user-provided identification data does not have a match in the decentralized ledger;
• wherein:
• hashes forming part of the decentralized ledger that have been verified by one of a plurality of verifiers have, within a same segment of the decentralized ledger, an associated verification of hash comprises the corresponding hash, a signature of the corresponding hash signed with a private key of the verifier, and a public key of such verifier;
• and
• hashes forming part of the decentralized ledger not having an associated verification of hash indicate that the identity of the corresponding user has not been verified.