AUTONOMOUS EXCHANGE VIA ENTRUSTED LEDGER IMMUTABLE DISTRIBUTED DATABASE

• US 20190324958A1
• Filed: 02/08/2019
• Published: 10/24/2019
• Est. Priority Date: 04/24/2018
• Status: Active Grant

• Current Assignee: Duvon Corporation
• Original Assignee: Duvon Corporation
• Inventors: Ow, Benedict, Stiles, Richard, Tan, Anthony
• Granted Patent: US 11,126,613 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/137 Hash-based content-based indexing of textual data G06F16/31
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• 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/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• 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/3247 involving digital signatures
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

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.

Claims

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;

a database storing one or more first hashes and one or more second hashes, the one or more first hashes generated with at least a portion of the file activity information, the one or more second hashes generated with at least a portion of the file activity information, wherein the database sends at least one of the one or more second hashes to a blockchain; and

a blockchain that stores the at least one of the one or more second hashes in one or more new blocks of the blockchain.

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 the 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 when activity occurs for the one or more of the one or more files.

4. The decentralized data storage system of claim 1, wherein the blockchain generates one or more third hashes with one or more of the one or more second hashes, and stores the one or more third hashes, the one or more third hashes sent to and stored 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 activity of the one or more files comprises file transactions selected from the group consisting of access, storage, transfer, and sharing of the one or more files.

7. 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.

8. The decentralized data storage system of claim 1, wherein the database is a distributed database.

9. The decentralized data storage system of claim 1, wherein one or more of the plurality of storage devices are connected via distinct networks.

10. A decentralized data storage system comprising:

a blockchain that verifies authenticity of one or more transactions between two or more nodes, wherein the blockchain generates one or more first hashes with at least transaction information, stores the one or more first hashes in one or more blocks on the blockchain, and sends the one or more first hashes to a database; and

a database that receives the one or more first hashes from the blockchain and stores the one or more first hashes.

11. The decentralized data storage system of claim 10, 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.

12. The decentralized data storage system of claim 11, wherein the 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 whenever a transaction occurs.

13. The decentralized data storage system of claim 10, wherein the database generates one or more second hashes with at least the one or more first hashes, stores the one or more second hashes, and the one or more second hashes are sent to and stored in the blockchain.

14. The decentralized data storage system of claim 13, 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.

15. The decentralized data storage system of claim 13, wherein the one or more second hashes are generated with at least the one or more first hashes and the transaction information.

16. The decentralized data storage system of claim 10, wherein the one or more transactions comprise file transactions selected from the group consisting of data storage and retrieval.

17. The decentralized data storage system of claim 10, 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.

18. The decentralized data storage system of claim 10, wherein the database is a distributed database.

19. A method for confirming integrity of one or more files at 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:

generating 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;

generating one or more third hashes with at least the one or more second hashes, wherein the one or more second hashes and the one or more third hashes are generated by different devices;

storing the one or more third hashes in a database and in one or more new blocks of a blockchain; and

comparing the one or more third hashes in the database and the one or more third hashes in the one or more new blocks of the blockchain one or more times to confirm integrity of the one or more files.

20. The method of claim 19, wherein the one or more third hashes in the database and the one or more third hashes in the one or more new blocks of the block chain are compared one or more times to confirm the integrity of the one or more files whenever activity occurs for the one or more files.