Proxied cross-ledger authentication

Abstract

Proxied cross-ledger authentication techniques are disclosed. In various embodiments, a verifier presentation requirement is determined, the verifier presentation requirement indicating a set of elements required to be provided by a client to authenticate the client. An authentication contract instance is created on a market maker ledger not associated specifically with the verifier, the authentication contract instance including at least a subset of the elements required by the verifier presentation requirement. A verifier system associated with the verifier presentation requirement is configured to read information from the authentication contract instance, obtain from an issuer associated with the client an issuer revocation data associated with the authentication contract instance, and use the information read from the authentication contract instance and the issuer revocation data to authenticate the client.

What is claimed is: 
     
         1 . A system, comprising:
 a communication interface; and   a processor coupled to the communication interface and configured to: 
 read information from a market maker ledger an authentication contract instance; 
 determine that the authentication contract instance includes a set of the elements 
   required by a verifier presentation requirement; 
 obtain from an issuer an issuer revocation data associated with the authentication contract instance; and 
 use the information read from the authentication contract instance and the issuer revocation data to authenticate the client, 
 wherein the authentication contract instance is written to the market maker ledger by a client seeking to be authenticated and the market maker ledger is configured facilitate cross-ledger transactions including by facilitating zero knowledge contingent payments between buyers and sellers of information. 
   
     
     
         2 . The system of  claim 1 , wherein the information read from the authentication contract instance includes an issuer handle and the processor is configured to use the issuer handle to obtain the issuer revocation data. 
     
     
         3 . The system of  claim 1 , wherein the information read from the authentication contract instance includes an authentication security deposit. 
     
     
         4 . The system of  claim 3 , wherein the authentication security deposit is backed by the client upon timeout. 
     
     
         5 . The system of  claim 3 , wherein the authentication security deposit is backed by the client upon contract completion. 
     
     
         6 . The system of  claim 1 , wherein the verifier presentation requirement includes a refundable deposit the client is required to make. 
     
     
         7 . The system of  claim 6 , wherein the processor is further configured to verify the deposit has been provided in connection with the authentication contract instance. 
     
     
         8 . The system of  claim 6 , wherein the verifier presentation requirement includes a security deposit currency for the refundable deposit. 
     
     
         9 . The system of  claim 1 , wherein the verifier presentation requirement includes an off-ledger address associated with a verifier. 
     
     
         10 . The system of  claim 1 , wherein the verifier presentation requirement includes a liveness requirement for the issuer revocation data. 
     
     
         11 . The system of  claim 1 , wherein the issuer revocation data pertains to a client public key associated with the client. 
     
     
         12 . The system of  claim 1 , wherein to use the information read from the authentication contract instance and the issuer revocation data to authenticate the client, the processor is configured to construct validity proof. 
     
     
         13 . The system of  claim 12 , wherein an authentication of the client is determined to be successful in response to a determination that the validity proof is valid. 
     
     
         14 . The system of  claim 1 , wherein the client is associated with a first ledger having associated therewith a first ledger cryptocurrency denominated in first ledger tokens, the system is associated with a second ledger having a second cryptocurrency denominated in second ledger tokens, and the issuer is associated with a third ledger having a third cryptocurrency denominated in third ledger tokens. 
     
     
         15 . The system of  claim 14 , wherein to obtain the issuer revocation data the processor is configured to use a cryptocurrency service associated with the market maker ledger to obtain a quantity of market maker ledger tokens equivalent in value to a quantity of third party tokens required by the issuer as an issuer fee to provide the issuer revocation data. 
     
     
         16 . The system of  claim 15 , wherein the processor is configured to pay the issuer fee and obtain the issuer revocation data via a zero-knowledge contingent payment transaction made via the market maker ledger. 
     
     
         17 . A method, comprising:
 reading information from a market maker ledger an authentication contract instance;   determining that the authentication contract instance includes a set of the elements required by a verifier presentation requirement;   obtaining from an issuer an issuer revocation data associated with the authentication contract instance; and   using the information read from the authentication contract instance and the issuer revocation data to authenticate the client,   wherein the authentication contract instance is written to the market maker ledger by a client seeking to be authenticated and the market maker ledger is configured facilitate cross-ledger transactions including by facilitating zero knowledge contingent payments between buyers and sellers of information.   
     
     
         18 . The method of  claim 17 , wherein the information read from the authentication contract instance includes an issuer handle and the processor is configured to use the issuer handle to obtain the issuer revocation data. 
     
     
         19 . The method of  claim 17 , wherein the information read from the authentication contract instance includes an authentication security deposit. 
     
     
         20 . A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
 reading information from a market maker ledger an authentication contract instance;   determining that the authentication contract instance includes a set of the elements required by a verifier presentation requirement;   obtaining from an issuer an issuer revocation data associated with the authentication contract instance; and   using the information read from the authentication contract instance and the issuer revocation data to authenticate the client,   wherein the authentication contract instance is written to the market maker ledger by a client seeking to be authenticated and the market maker ledger is configured facilitate cross-ledger transactions including by facilitating zero knowledge contingent payments between buyers and sellers of information.