Autonomous exchange via entrusted ledger immutable distributed database

Abstract

An Autonomous Exchange via Entrusted Ledger (AXEL) blockchain is discussed herein. The AXEL blockchain enables users to perform transactions in a private setting while enabling the transaction records thereof to be verified by other network users without publicly divulging the contents or details of the transaction records. The token identification system and method allows the tokens to carry an immutable identification to prevent negative blockchain occurrences such as double spending. A payment methodology allowing integration of external financial institutions with user owned and managed wallet. The AXEL blockchain can also interface with and utilize a distributed database to create an immutable record of each transaction while providing a complete backup of the transactions that occur within the system and on the AXEL blockchain.

What is claimed is: 
     
         1 . A decentralized data storage system comprising:
 a plurality of storage devices storing one or more files at one or more locations, the one or more files having file activity information recording activity of the one or more files associated therewith;   one or more smart contracts that, when executed by one or more processors, generates one or more first hashes and one or more second hashes with at least a portion of the file activity information;   a blockchain that stores the at least one of the one or more second hashes in one or more new blocks of the blockchain; and   a database that stores the one or more first hashes and the one or more second hashes.   
     
     
         2 . The decentralized data storage system of  claim 1 , wherein one or more of the one or more second hashes stored in the database and the blockchain are compared one or more times to confirm integrity of one or more of the one or more files. 
     
     
         3 . The decentralized data storage system of  claim 2 , wherein, when a discrepancy is detected by the comparison, the one or more files are reverted to an earlier version. 
     
     
         4 . The decentralized data storage system of  claim 1 , wherein the one or more smart contracts generate one or more third hashes with one or more of the one or more second hashes, wherein the one or more third hashes are stored in one or more new blocks of the blockchain and in the database. 
     
     
         5 . The decentralized data storage system of  claim 4 , wherein one or more of the one or more third hashes stored in the database and the blockchain are compared one or more times to confirm integrity of one or more of the one or more files. 
     
     
         6 . The decentralized data storage system of  claim 1 , wherein the one or more first hashes are generated with at least a portion of the file activity information and the one or more locations. 
     
     
         7 . The decentralized data storage system of  claim 1 , wherein the database is a distributed database. 
     
     
         8 . The decentralized data storage system of  claim 1 , wherein one or more of the plurality of storage devices are connected via distinct networks. 
     
     
         9 . A decentralized data storage system for a plurality of node devices, the decentralized data storage system comprising:
 a smart contract that, when executed by one or more processors, generates one or more first hashes with at least transaction information;   a blockchain for verifying authenticity of one or more transactions between the plurality of node devices, wherein the blockchain stores the one or more first hashes in one or more blocks on the blockchain; and   a database that stores the one or more first hashes and one or more second hashes, the one or more second hashes generated with at least the one or more first hashes, wherein the one or more second hashes are stored in one or more blocks on the blockchain.   
     
     
         10 . The decentralized data storage system of  claim 9 , wherein one or more of the one or more first hashes stored in the database and the blockchain are compared one or more times to verify authenticity of the one or more transactions. 
     
     
         11 . The decentralized data storage system of  claim 10 , wherein, when a discrepancy is detected by the comparison, at least one of the one or more transactions is reverted. 
     
     
         12 . The decentralized data storage system of  claim 9 , wherein the one or more transactions comprise sending a blockchain token from one digital wallet to another digital wallet. 
     
     
         13 . The decentralized data storage system of  claim 9 , wherein one or more of the one or more second hashes stored in the database and the blockchain are compared one or more times to verify authenticity of the one or more transactions. 
     
     
         14 . The decentralized data storage system of  claim 9 , wherein the one or more second hashes are generated with at least the one or more first hashes and the transaction information. 
     
     
         15 . The decentralized data storage system of  claim 9 , wherein the one or more transactions comprise file transactions selected from the group consisting of data storage and retrieval. 
     
     
         16 . The decentralized data storage system of  claim 9 , wherein the one or more first hashes are generated with at least the transaction information and one or more locations of one or more files involved in the one or more transactions. 
     
     
         17 . The decentralized data storage system of  claim 9 , wherein the database is a distributed database. 
     
     
         18 . A method for confirming integrity of one or more files of a decentralized data storage system storing the one or more files at one or more locations, the one or more files having file activity information recording activity of the one or more files associated therewith, the method comprising:
 executing one or more smart contracts at one or more processors to generate one or more first hashes with at least a portion of the file activity information;   generating one or more second hashes with at least the one or more first hashes, wherein the one or more first hashes and the one or more second hashes are generated at different devices;   storing the one or more second hashes in a database and in one or more new blocks of a blockchain; and   comparing the one or more second hashes in the database and the one or more second hashes in the one or more new blocks of the blockchain one or more times to confirm integrity of the one or more files.   
     
     
         19 . The method of  claim 18 , wherein, when a discrepancy is detected by the comparison, at least one of the one or more files are reverted to an earlier version. 
     
     
         20 . The method of  claim 18 , wherein the one or more second hashes are generated with at least the one or more first hashes and the file activity information.