METHODS AND SYSTEMS OF PROVIDING VERIFICATION OF INFORMATION USING A CENTRALIZED OR DISTRIBUTED LEDGER

• US 20170317834A1
• Filed: 04/28/2017
• Published: 11/02/2017
• Est. Priority Date: 04/30/2016
• Status: Active Grant

• Current Assignee: Civic Technologies, Inc.
• Original Assignee: Civic Technologies, Inc.
• Inventors: Smith, Jonathan Robert, Lingham, Vinodan Karthikeya, Driscoll, John, Fraser, Iain Charles
• Granted Patent: US 10,333,706 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/065 using e-cash
• CPC Class Codes: G06Q 20/308 using the Internet of Things
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G06Q 20/407 Cancellation of a transaction
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 9/0637 Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/0891 Revocation or update of secret information, e.g. encryption key update or rekeying
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 : Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3066 : involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
• CPC Class Codes: H04L 9/3236 : using cryptographic hash functions
• CPC Class Codes: H04L 9/3239 : involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3242 : involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04L 9/3271 : using challenge-response
• CPC Class Codes: H04L 9/50 : using hash chains, e.g. blockchains or hash trees

Abstract

A method and system of providing verification of information of a user relating to an attestation transaction is provided, and includes sending a request for information of the user, wherein the information has been previously attested to in an attestation transaction stored within a centralized or distributed ledger at an attestation address; receiving at a processor associated with a verifier the information of the user; sending a cryptographic challenge nonce; receiving at the processor associated with the verifier the cryptographic challenge nonce signed by the user'"'"'s private key; verifying user identity with the cryptographic challenge nonce signed by the user'"'"'s private key; deriving a public attest key by using the information of the user; deriving an attestation address using the public attest key; and verifying the existence of the attestation transaction at the attestation address in the centralized or distributed ledger.

Claims

1. A method of providing verification of information of a user relating to an attestation transaction, the method being implemented on a computer system having one or more physical processors configured by machine-readable instructions which, when executed perform the method, comprising:

sending a request for information of the user, wherein the information has been previously attested to in an attestation transaction stored within a centralized or distributed ledger at an attestation address, the centralized or distributed ledger providing a record of transactions;

receiving at a processor associated with a verifier the information of the user;

sending a cryptographic challenge nonce;

receiving at the processor associated with the verifier the cryptographic challenge nonce signed by the user'"'"'s private key;

verifying user identity with the cryptographic challenge nonce signed by the user'"'"'s private key;

deriving a public attest key by using the information of the user;

deriving an attestation address using the public attest key; and

verifying the existence of the attestation transaction at the attestation address in the centralized or distributed ledger.

2. The method of claim 1,

wherein sending a request for information further comprises sending a request for the user'"'"'s public key;

and

wherein receiving the information further comprises receiving the user'"'"'s public key.

3. The method of claim 2,

wherein verifying user identity further comprises checking the user'"'"'s public key and the cryptographic challenge nonce signed by the user'"'"'s private key.

4. The method of claim 2,

wherein deriving a public attest key further comprises using the information and the user'"'"'s public key to derive the public attest key.

5. The method of claim 1, further comprising providing a processor associated with an attestor for generating the attestation transaction.

6. The method of claim 5,

wherein sending a request for information further comprises sending a request for the attestor'"'"'s public key and a third party cosigner'"'"'s public key.

7. The method of claim 5,

wherein using the information to derive the public attest key further comprises using at least one of the user'"'"'s public key, an attestor'"'"'s public key and a third party cosigner'"'"'s public key to derive the public attest key.

8. The method of claim 5, wherein deriving a public attest key comprises deriving the public attest key using an application or website of the attestor.

9. The method of claim 5, wherein the processor associated with the verifier sends the information received by the user to the processor associated with the attestor and receives the public attest key from the processor associated with the attestor.

10. The method of claim 9, wherein the processor associated with the verifier sends the user information and the user'"'"'s public key to a third party application or website and wherein the processor associated with the verifier receives the public attest key and the attestation address from third party application or website

11. The method of claim 9, wherein the processor associated with the verifier uses a third party digital wallet provider application or website to verify the existence of the attestation transaction at the attestation address.

12. A system for providing verification of information of a user relating to an attestation transaction, the system comprising

a computer system having one or more physical processors configured by machine-readable instructions to:

send a request for information of the user, wherein the information has been previously attested to in an attestation transaction stored within a centralized or distributed ledger at an attestation address, the centralized or distributed ledger providing a verifiable record of transactions;

receive at a processor associated with the verifier the information of the user;

send a cryptographic challenge nonce;

receive at the processor associated with the verifier the cryptographic challenge nonce signed by the user'"'"'s private key;

verify user identity with the cryptographic challenge nonce signed by the user'"'"'s private key;

derive a public attest key by using the information of the user;

derive an attestation address using the public attest key;

verify the existence of the attestation transaction at the attestation address in the centralized or distributed ledger.

13. A method of providing attestation of information by an attestor, the method being implemented on a computer system having one or more physical processors configured by machine-readable instructions which, when executed perform the method, comprising:

receiving at a processor associated with the attestor the information and a public key generated for the information;

applying a hash function to the information to create a hash;

combining the hash of the information with the public key generated for the information to generate a public attest key;

generating an attestation address based on the public attest key; and

communicating a signed transaction to a centralized or distributed ledger for storage at the attestation address.

14. The method of claim 13, wherein elliptic curve addition is used to combine the hash of the information with the public key generated for the information to generate the public attest key.

15. The method of claim 13, wherein combining the hash of the information with the public key generated for the information comprises using the hash of the information as an offset and using the public key generated for the information to generate the public attest key.

16. The method of claim 13, wherein generating the attestation address for a single signature transaction comprises applying a second hash function to the public attest key.

17. The method of claim 13, wherein generating the attestation address comprises combining two or more public keys of potential signers utilizing a multi-signature script.

18. The method of claim 17, wherein one of the public keys of potential signers is one of a public key of a wallet provider, a public key of the attestor, and a recovery public key of a user.

19. The method of claim 17, wherein generating the attestation address for a multiple signature transaction comprises generating a redeem script using the public keys of the multiple signatories, serializing the redeem script to create a serialized output, applying a second hash function to the serialized output to create a second hash, and applying a third hash function to the second hash.

20. The method of claim 13, wherein the centralized or distributed ledger is the bitcoin blockchain.