Systems and methods for personal identification and verification

A method for personal identification and verification for transactions involving cryptography-based electronic money, the method being executed by central approval servers and a computational server configured to operate a computer program functioning as a registration interface, the method steps comprising:

• providing, using the computational server, access to one or more potential or existing currency users;
• providing, using the computational server, a registration interface for one or more potential currency users to register a user account requiring authentication;
• requesting, using the computational server, the submission of documents for proof of the real personal identity of a registrant;
• verifying, using the computational server, the real personal identity of the registrant;
• rejecting, using the computational server, an account creation for registrants failing in personal identity verification;
• creating, using the computational server, a personal account for individual successful registrants with successful verification of personal identity;
• allowing, using the computational server, a successful registrant to create a credential that comprises an associated authentication;
• storing, using the computational server, all the submitted information in a client information database;
• sending, using the computational server, the credential to central approval servers;
• generating, using the central approval servers, a multisignature currency address for use in transactions;
• and
• mapping and storing, using the central approval servers, the multisignature currency address, credential, and personal identity of individual registrants in a database,
• wherein generation of the multisignature currency address includes:
• receipt, by one of the central approval servers, of the credential from a client wallet,
• checking, by one of the central approval servers, the credential is valid by matching of the credential to a valid and active credential stored in the database, and
• sending, by one of the central approval servers and on validating the credential, an approval public key to the client wallet for use in creation of the multisignature currency address, the creation of the multisignature currency address requiring use of the approval public key and at least one client public key, such that transactions can be made which are counter-signed by one of the central approval servers.

A method for creating a cryptography-based electronic money (CBEM), and its associated transaction network, the method being executed by central approval servers and a network of nodes, comprising:

• Connecting, via a central approval server, a plurality of nodes to form relay nodes of a peer-to-peer network through a data transmission network;
• protecting the ownerships of at least one unit of the CBEM by public/private-key cryptography;
• restricting only valid registered users to generate one or more valid currency addresses to receive at least one unit of the CBEM by verifying a submitted credential via one of the central approval servers;
• recording transactions of at least one unit of the CBEM into a public ledger;
• verifying transactions of at least one unit of the CBEM;
• restricting at least one transaction approval rule, to include at least one of:
• requisition of a valid credential from the sender and requisition of one or more approval private keys from one of the central approval servers;
• and
• creating a multisignature transaction requiring at least two private keys as signatures, wherein:
• all transaction requests are sent from client wallets to one of the central approval servers to obtain an approval private key for signing the transactions,
• the at least two private keys include the approval private key from the one of the central approval servers and the remainder of the at least two private keys are each a private key stored in a client wallet,
• the at least two private keys are required for the creation of multisignature transactions, and
• the approval private key is restricted to be from one of the central approval servers, such that transactions missing any one of the required private keys are rejected.