Secure transaction controller for value token exchange systems

Abstract

Systems and methods that provide improved security and scalability in digital token exchange are disclosed. A secure transaction controller may include an exchange request module, exchange matching module, and exchange execution module to facilitate the exchange of different classes of value tokens.

1 - 74 . (canceled) 
     
     
         75 . A system for issuing cryptographically signed digital tokens of a first class as part of an exchange of digital tokens of different classes, comprising:
 a processor;   a memory in communication with the processor;   a secure memory storing a mint key;   instructions stored in the memory and executed by the processor, to
 (a) responsive to a first client device requesting from an exchange server an exchange of a first set of cryptographically signed digital tokens of the first class for a second set of digital tokens of a second class,
 receive a message from the exchange server including the first set of digital tokens, 
 confirm the validity of the first set of digital tokens, 
 cause the first set of digital tokens to be placed in an escrow state, 
 send an acknowledgement message to the exchange server indicating the first set of digital tokens are valid and have been placed in an escrow state, 
 
 (b) subsequent to sending the acknowledgement message, receive an instruction from the exchange server to swap the first set digital tokens for a new set of coded digital tokens of the first class and second client device information, 
 (c) responsive to receiving the instruction, cryptographically sign, using the mint key, each of the new set of coded digital tokens, each of the new set of coded digital tokens including information sufficient to confirm the second client device is the original recipient of that token, and 
 (d) send the new set of signed coded digital tokens to the second client device. 
   
     
     
         76 . The system of  claim 75 , wherein each of the new set of coded digital tokens is encoded with information with sufficient information to identify the second client device. 
     
     
         77 . The system of  claim 75 , wherein each of the new set of coded digital tokens is not encoded with sufficient information to determine the identity of the second client device but does contain sufficient information to confirm the second client device is the original recipient of that token when that token is presented for use by the second client device. 
     
     
         78 . The system of  claim 75 , wherein the instructions executed by the processor are further configured to
 receive information from an escrow finalization message sent to the second client device by the exchange server, and   responsive to receiving the information from the escrow finalization message, to permit the second client device to retrieve the new set of coded digital tokens from the system.   
     
     
         79 . The system of  claim 75 , wherein the instruction received from the exchange server further includes a complex exchange transaction identifier. 
     
     
         80 . The system of  claim 75 , further comprising:
 a spent token repository, wherein confirming the validity of each of the first set of digital tokens including checking the spent token repository for information regarding that token.   
     
     
         81 . The system of  claim 75 , further comprising:
 a valid token repository, wherein confirming the validity of each of the first set of digital tokens including checking the valid token repository for information regarding that token.   
     
     
         82 . The system of  claim 75 , further comprising:
 an escrow unit, the escrow unit configured to place each of the first set of digital tokens in an escrow state.   
     
     
         83 . The system of  claim 75 , further comprising:
 a spent token repository, wherein the escrow unit is configured to place each token in the first set of digital tokens in an escrow state by adding a temporary escrow coded entry corresponding to the that token to the spent token repository.   
     
     
         84 . The system of  claim 83 , wherein the instructions are further configured to cause the temporary escrow coded entries for each of the first set of digital tokens to be changed to a spent token entry before the new set of digital tokens is sent. 
     
     
         85 . The system of  claim 75 , wherein determining the first set of digital tokens is valid includes determining the first client device is the original recipient of each of the first set of digital tokens. 
     
     
         86 . A method of issuing new cryptographically signed digital tokens as part of providing a secure token exchange transaction for cryptographically signed digital tokens of different classes, comprising:
 responsive to an exchange server receiving a first digital message including a first request from a first client device to exchange a first set of digital tokens of a first class for digital tokens of a second class, receiving a message including the first set of digital tokens from the exchange server;   after receiving the message, confirming the validity of each of the first set of digital tokens;   after receiving the message, placing each of the first set of digital tokens in an escrow state;   sending an acknowledgement confirming that all of the digital tokens in the first set of digital tokens are valid and have been placed in escrow;   subsequent to sending the acknowledgement, receiving an instruction from the exchange server to swap the first set digital tokens for a new set of coded digital tokens of the first class and second client device information;   responsive to receiving the instruction, cryptographically signing using a mint key each of the new set of coded digital tokens, each of the new coded tokens including information sufficient to confirm the second client device is the original recipient of that token; and   sending the new set of signed coded digital tokens to the second client device.   
     
     
         87 . The method of  claim 86 , wherein each of the new set of coded digital tokens are encoded with information which can be used to indicate the identity of the second client device. 
     
     
         88 . The method of  claim 86 , wherein the each of the new set of coded digital tokens are not encoded with sufficient information to indicate the identity of the second client device but do contain sufficient information to confirm the second client device is the original recipient that token when that token is presented for use by the second client device. 
     
     
         89 . The method of  claim 86 , further comprising:
 receive information from an escrow finalization message sent to the second client device by the exchange server, and   responsive to receiving the information from the escrow finalization message, permitting the second client device to retrieve the new set of coded digital tokens.   
     
     
         90 . The method of  claim 86 , wherein determining the first set of digital tokens is valid includes determining the first client device is the original recipient of each of the first set of digital tokens. 
     
     
         91 . The system of  claim 86 , further comprising:
 wherein confirming the validity of each of the first set of digital tokens including checking a valid token repository for information regarding that token.   
     
     
         92 . The system of  claim 86 , further comprising:
 placing each token in the first set of digital tokens in an escrow state by adding a temporary escrow coded entry corresponding to that token to a spent token repository.   
     
     
         93 . The method of  claim 92 , further comprising:
 changing the temporary escrow coded entries for each of the first set of digital tokens to a spent token entry before the new set of digital tokens is sent.   
     
     
         94 . A non-transitory machine readable medium storing a program, configured to, when executed by a processor, to cause a processor to
 responsive to an exchange server receiving a first digital message including a first request from a first client device to exchange a first set of digital tokens of a first class for digital tokens of a second class, receive a message including the first set of digital tokens from the exchange server;   after receiving the message, confirm the validity of each of the first set of digital tokens;   after receiving the message, place each of the first set of digital tokens in an escrow state;   send an acknowledgement confirming that the first set of digital tokens is valid and has been placed in escrow;   subsequent to sending the acknowledgement, receive an instruction from the exchange server to swap the first set digital tokens for a new set of coded digital tokens of the first class and second client device information;   responsive to receiving the instruction, cryptographically sign using a mint key each of the new set of coded digital tokens, each of the new set of coded tokens including information sufficient to confirm the second client device is the original recipient that token, and   send the new set of signed coded digital tokens to the second client device.