Distributed ledger based distributed gaming system

Abstract

The technology teaches a distributed gaming system, comprising a server-side node configured to administer transactions for a gambling casino, selling and redeeming chips using a private database, and recording transactions on a distributed ledger using crypto-tokens for a house account, with a token vault wallet that has a unique identifier and private key to track transactions. Customer wallets, intermediary accounts and one-way redemption wallets track transactions on the distributed ledger. Client-side nodes accept token purchase messages and transfer tokens in the ledger and record in the database, accept token-to-chip messages from an intermediary account and transfer tokens on the ledger to the redemption wallet to extinguish and record the exchange, accept chip-to-token messages from an intermediary account and transfer tokens from the vault to the customer account and record the exchange, and accept token-to-fiat messages from an intermediary account and transfer tokens to extinguish, and record the exchange.

1 . A distributed gaming system, comprising:
 a server-side node or nodes, including one or more data processors, having access to a distributed ledger, the server-side node or nodes configured to:   maintain a crypto-token vault wallet having a unique house identifier and private key to track transactions on the distributed ledger that include the unique house identifier;   maintain user accounts for customers, including unique customer identifiers and private keys to track transactions on the distributed ledger that include the unique customer identifiers;   maintain intermediary accounts, including unique intermediary identifiers and private keys to track transactions on the distributed ledger that include the unique intermediary identifiers;   maintain a redemption wallet having a unique redemption identifier and private key to track transactions on the distributed ledger that include the unique redemption identifier; and   communicate with client-side nodes in a communication network to execute procedures:
 to accept crypto-token purchase messages from an identified customer account indicating confirmation of fiat payment by the identified customer account for crypto-tokens, and in response transfer crypto-tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a crypto-token purchase; 
 to accept crypto-token-to-chip exchange messages from an identified intermediary account indicating confirmation of exchange of crypto-tokens for chips, and in response transfer crypto-tokens on the distributed ledger to the redemption wallet to extinguish the crypto-tokens, and record a crypto-token-to-chip exchange; 
 to accept chip-to-crypto-token exchange messages from an identified intermediary account indicating confirmation of delivery of chips from a customer having an identified customer account to an intermediary having the identified intermediary account, and in response transfer crypto-tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a chip-to-crypto-token exchange; and 
 to accept crypto-token-to-fiat exchange messages from an identified intermediary account indicating confirmation of delivery of fiat currency to a customer having an identified user account, and in response transfer tokens from the identified user account to the redemption wallet to extinguish, and record a crypto-token-to-fiat exchange on the distributed ledger. 
   
     
     
         2 . The system of  claim 1 , the server-side node or nodes being configured to create a tranche of crypto-tokens in the crypto-token vault wallet. 
     
     
         3 . The system of  claim 1 , the server-side node or nodes being configured to assign crypto-tokens to the crypto-token vault wallet in response to a message confirming receipt of value. 
     
     
         4 . The system of  claim 1 , wherein the one or more data processors of the server-side node or nodes include logic for authentication and authorization of intermediary account holders and customer account holders at client-side nodes, including a first protocol for customer account holders on client-side nodes on the communication network, and a second protocol for intermediary account holders on client-side nodes on the communication network. 
     
     
         5 . The system of  claim 4 , wherein the second protocol for intermediary account holders includes
 receiving from a supervisor application a request to enable a dealer application;   generating a verification code for the request;   providing the verification code to the supervisor application in response to the request from the supervisor application to enable a particular intermediary account holder, the verification code being provided to a dealer outside the communication network; and   receiving a login request via the communication network from a dealer application to login the particular intermediary account holder by the dealer application using the verification code.   
     
     
         6 . (canceled) 
     
     
         7 . (canceled) 
     
     
         8 . (canceled) 
     
     
         9 . The system of  claim 1 , wherein the server-side node or nodes is configured to maintain a dealer wallet for intermediary accounts to track transaction on the distributed ledger for the corresponding intermediary account. 
     
     
         10 . The system of  claim 1 , wherein the server-side node or nodes is configured to maintain a customer wallet for customer accounts to track transaction on the distributed ledger for the corresponding customer account. 
     
     
         11 . A non-transitory computer readable memory storing computer instructions for administering transactions for a gambling casino in a distributed gaming system, including selling chips and redeeming chips using a distributed ledger, comprising computer instructions to:
 maintain a crypto-token vault wallet having a unique house identifier and private key to track transactions on the distributed ledger that include the unique house identifier;   maintain user accounts for customers, including unique customer identifiers and private keys to track transactions on the distributed ledger that include the unique customer identifiers;   maintain intermediary accounts, including unique intermediary identifiers and private keys to track transactions on the distributed ledger that include the unique intermediary identifiers;   maintain a redemption wallet having a unique redemption identifier and private key to track transactions on the distributed ledger that include the unique redemption identifier; and   communicate with client-side nodes in a communication network to execute procedures:
 to accept crypto-token purchase messages from an identified customer account indicating confirmation of fiat payment by the identified customer account for crypto-tokens, and in response transfer tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a crypto-token purchase; 
 to accept crypto-token-to-chip exchange messages from an identified intermediary account indicating confirmation of exchange crypto-tokens for chips, and in response transfer crypto-tokens on the distributed ledger to the redemption wallet to extinguish the crypto-tokens, and record a crypto-token-to-chip exchange; 
 to accept chip-to-crypto-token exchange messages from an identified intermediary account indicating confirmation of delivery of chips from a customer having an identified customer account to an intermediary having the identified intermediary account, and in response transfer crypto-tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a chip-to-crypto-token exchange; and 
 to accept crypto-token-to-fiat exchange messages from an identified intermediary account indicating confirmation of delivery of fiat currency to a customer having an identified user account, and in response transfer crypto-tokens from the identified user account to the redemption wallet to extinguish, and record a crypto-token-to-fiat exchange on the distributed ledger. 
   
     
     
         12 . The non-transitory computer readable memory storing computer instructions of  claim 11 , including computer instructions for authentication and authorization of intermediary account holders and customer account holders at client-side nodes, including a first protocol for customer account holders on client-side nodes on the communication network, and a second protocol for intermediary account holders on client-side nodes on the communication network. 
     
     
         13 . The non-transitory computer readable memory storing computer instructions of  claim 12 , wherein the second protocol for intermediary account holders includes
 receiving from a supervisor application a request to enable a dealer application;   generating a verification code for the request;   providing the verification code to the supervisor application in response to the request from the supervisor application to enable a particular intermediary account holder, the verification code being provided to a dealer outside the communication network; and   receiving a login request via the communication network from a dealer application to login the particular intermediary account holder by the dealer application using the verification code.   
     
     
         14 . (canceled) 
     
     
         15 . (canceled) 
     
     
         16 . The non-transitory computer readable memory storing computer instructions of  claim 11 , wherein the distributed ledger comprises a block chain. 
     
     
         17 . The non-transitory computer readable memory storing computer instructions of  claim 11 , including computer instructions to maintain a dealer wallet for intermediary accounts to track transaction on the distributed ledger for the corresponding intermediary account. 
     
     
         18 . The non-transitory computer readable memory storing computer instructions of  claim 11 , including computer instructions to maintain a customer wallet for customer accounts to track transaction on the distributed ledger for the corresponding customer account. 
     
     
         19 . A method of administering transactions for a gambling casino in a distributed gaming system, including selling chips and redeeming chips using a distributed ledger, comprising:
 maintaining a crypto-token vault wallet having a unique house identifier and private key to track transactions on the distributed ledger that include the unique house identifier;   maintaining user accounts for customers, including unique customer identifiers and private keys to track transactions on the distributed ledger that include the unique customer identifiers;   maintaining intermediary accounts, including unique intermediary identifiers and private keys to track transactions on the distributed ledger that include the unique intermediary identifiers;   maintaining a redemption wallet having a unique redemption identifier and private key to track transactions on the distributed ledger that include the unique redemption identifier; and   communicating with client-side nodes in a communication network to execute procedures:
 to accept crypto-token purchase messages from an identified customer account indicating confirmation of fiat payment by the identified customer account for crypto-tokens, and in response transfer crypto-tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a crypto-token purchase; 
 to accept crypto-token-to-chip exchange messages from an identified intermediary account indicating confirmation of exchange crypto-tokens for chips, and in response transfer crypto-tokens on the distributed ledger to the redemption wallet to extinguish the crypto-tokens, and record a crypto-token-to-chip exchange; 
 to accept chip-to-crypto-token exchange messages from an identified intermediary account indicating confirmation of delivery of chips from a customer having an identified customer account to an intermediary having the identified intermediary account, and in response transfer crypto-tokens in the distributed ledger from the crypto-token vault wallet to the unique customer identifier of the identified customer account, and record a chip-to-crypto-token exchange; and 
 to accept crypto-token-to-fiat exchange messages from an identified intermediary account indicating confirmation of delivery of fiat currency to a customer having an identified user account, and in response transfer crypto-tokens from the identified user account to the redemption wallet to extinguish, and record a crypto-token-to-fiat exchange on the distributed ledger. 
   
     
     
         20 . The method of  claim 19 , including assigning crypto-tokens to the crypto-token vault wallet in response to a message confirming receipt of value. 
     
     
         21 . The method of  claim 19 , including executing procedures for authentication and authorization of intermediary account holders and customer account holders at client-side nodes, including a first protocol for customer account holders on client-side nodes on the communication network, and a second protocol for intermediary account holders on client-side nodes on the communication network. 
     
     
         22 . The method of  claim 21 , wherein the second protocol for intermediary account holders includes
 receiving from a supervisor application a request to enable a dealer application;   generating a verification code for the request;   providing the verification code to the supervisor application in response to the request from the supervisor application to enable a particular intermediary account holder, the verification code being provided to a dealer outside the communication network; and   receiving a login request via the communication network from a dealer application to login the particular intermediary account holder by the dealer application using the verification code.   
     
     
         23 . (canceled) 
     
     
         24 . (canceled) 
     
     
         25 . The method of  claim 19 , wherein the distributed ledger comprises a block chain. 
     
     
         26 . The method of  claim 19 , including maintaining a dealer wallet for intermediary accounts to track transaction on the distributed ledger for the corresponding intermediary account. 
     
     
         27 . The method of  claim 19 , including maintaining a customer wallet for customer accounts to track transaction on the distributed ledger for the corresponding customer account.