Researchers Submit Patent Application, “Autonomous Exchange Via Entrusted Ledger Immutable Distributed Database”, for Approval (USPTO 20220004538): Duvon Corporation

2022 JAN 25 (NewsRx) -- By a News Reporter-Staff News Editor at Insurance Daily News -- From Washington, D.C., NewsRx journalists report that a patent application by the inventors Ow, Benedict (Las Vegas, NV, US); Stiles, Richard (Las Vegas, NV, US); Tan, Anthony (Las Vegas, NV, US), filed on September 20, 2021, was made available online on January 6, 2022.

The patent’s assignee is Duvon Corporation (Las Vegas, Nevada, United States).

News editors obtained the following quote from the background information supplied by the inventors: “

“Field of the Invention

“This invention relates to the use of a distributed database function in conjunction with a blockchain and the capability of immutably storing transactions between a blockchain and a database.

“Related Art

“Blockchain or distributed ledger technology provides a decentralized architecture for validation of records. Traditionally, the blockchain or distributed ledger and the information therein is shared across participating network nodes.

“From the discussion that follows, it will become apparent that the present invention addresses the deficiencies associated with the prior art while providing additional advantages and benefits not contemplated or possible with prior art constructions.”

As a supplement to the background information on this patent application, NewsRx correspondents also obtained the inventors’ summary information for this patent application: “An Autonomous eXchange via Entrusted Ledger blockchain (hereinafter “AXEL”) is described herein. AXEL is a distributed blockchain network that utilizes a suite of unique smart contracts to facilitate the transfer, storage, sharing, and streaming of digital content through the network enabling trust to be established between nodes while providing private transaction capabilities for participants within the AXEL blockchain. While the following disclosure provides an example of the AXEL blockchain in a decentralized network configuration, the AXEL blockchain can easily be configured to support centralized architectures in both public, private, and hybrid deployment configurations.

“AXEL is intended to provide a networking environment wherein transactions that occur between parties can be done in a private setting while still enabling the network trust element of a publicly available ledger. AXEL utilizes a unique public and private chain (ledger) approach to decentralized computing wherein the details of transactions that occur between parties remain hidden from public view. In one preferred embodiment, a file can be transferred between a first and a second user. The transaction record of the file transfer will appear in detail on the private ledger of both the first and the second user. Witnesses to this transaction can execute the consensus algorithm to ensure that the transaction has occurred and has been verified, but the user hosting a node that is a witness will not know or have visibility to the details of the actual transaction. This enables the first and second user to maintain the privacy of their transaction while still enabling the blockchain to witness and verify the transaction to ensure authentication and accuracy.

“AXEL provides participants with the capability of managing digital content in a blockchain environment. In this example, the storage, transfer, sharing, and streaming capabilities are controlled directly by the user and not through a centralized control mechanism.

“The AXEL blockchain may include a utility token mechanism that enables users to create a commerce capability wherein they may trade access or download rights to digital content they own and manage within AXEL in exchange for utility tokens.

“In one embodiment, the AXEL blockchain enables a user of a computing device (e.g. personal computer, smartphone, tablet, etc.) to access and manage any digital content located on the subject device (either from that same device or through another device) and provide access to the content through the AXEL blockchain. This embodiment may, in one advantageous configuration, work in conjunction with the PINApp (Pervasive Intermediate Network Attached Storage Application) platform, which is described in U.S. Pat. No. 9,792,452 to enable access and management of digital content.

“As one example of the use of AXEL, an AXEL user such as a healthcare provider may wish to transfer patient records privately and securely through AXEL to a health insurance provider. The healthcare provider may select the patient records they wish to transfer and initiate the exchange to the insurance provider. The insurance provider would receive the subject patient records and acknowledge receipt through AXEL.

“The transaction in the scenario above is witnessed by a randomly selected group of nodes running a witness consensus algorithm against the subject transaction. Using a consensus algorithm, witnesses reach a consensus and resolve the transaction. As the consensus is completed, the healthcare providers’ private blockchain (ledger) will be updated with a block showing the transaction that occurred with the insurance provider. In a similar fashion, the insurance providers’ private blockchain (ledger) would also be updated with a block that mirrored the block created for the healthcare provider. These mirror blocks would appear on the subject blockchains (ledgers) of each party participating in a transaction. The witness parties’ private blockchains (ledgers) would also contain a mirror block reflecting the transaction that they witnessed.

“At the conclusion of the subject transaction in the example above, each participating party (healthcare provider, insurance provider, and witnesses) would automatically update their private blockchains (ledgers) to their alpha blocks associated with each user. The updates to the alpha blocks would contain a verification that the transaction was witnessed and that it was successfully authenticated and verified, validating the subject transaction. In the interest of privacy, the updates to the alpha blocks associated with the transaction would not contain any details of the transaction that took place that are visible to users outside of the immediate transaction other than that the transaction was witnessed, authenticated, and verified.

“The details of the transaction in the above sequence will be available and visible only to the parties that were directly involved in the transaction (in this example, the healthcare provider and insurance provider). Since the transaction is of a private nature, the transaction details will not be made available to parties outside of the immediate transaction.

“The devices used by the witness pool executing the consensus algorithm against the transaction will have access to the details of the subject transaction during the consensus process, but these details will not be visible to the user(s) whose devices are executing the consensus algorithm. These details will be hidden from view to maintain the privacy of the transaction. Once the transaction is completed and digitally signed by the witness pool, each witness will have a mirror block of the subject transaction added to their private ledger (chain). The mirror blocks created for the witnesses will contain, but will not enable visibility to, the details of the subject transaction. The mirror blocks are a key component of the AXEL blockchain as they provide a safeguard against parties who may try to alter or otherwise compromise the conditions or details of a transaction. By making the transaction details invisible to users outside of the immediate transaction, the AXEL network can protect the integrity of the transactions that occur within the AXEL blockchain while still providing an accurate account of the transaction verification on the public blockchain.

“In order to assist with providing adequate storage to facilitate a desirable environment for transactions, the AXEL blockchain can include a distributed network storage capability that allows nodes participating in AXEL to sell storage space that is attached to their local area network devices. In one preferred embodiment, a user may create a node with a personal or home computing device such as a personal computer. The user may attach a one terabyte external storage drive to that personal computer and make the space on that storage drive available for use by other participants within the network.

“Unlike existing distributed and decentralized storage methods, in a preferred embodiment, AXEL stores the key codes for both encryption and decryption of the content destined for the network storage on their gateway device such as a personal computer. This ensures the privacy and security of the content being stored as the keys required to access and execute the stored content resides with the user who owns the content.

“AXEL can also utilize a redundant storage algorithm that distributes the encrypted parts of the digital content being stored and places them on multiple (participating) devices throughout the AXEL blockchain. In this embodiment, AXEL may routinely request ID and storage information from the network to ensure that the content being stored is both available and accessible to the user. Should a node go offline rendering the stored content unavailable, AXEL may notify the gateway device that the content is no longer available and create additional backup copies of the content that is no longer available. These copies could be gathered from other repositories within the network storing identical encrypted fragments of the subject digital content throughout the AXEL blockchain.

“AXEL can also incorporate mechanisms to comply with identification and anti-corruption due diligence requirements, such as regulations directed at money laundering activities. For example, to comply with current regulations AXEL may include an “anti-money laundering” (AML) and “know your customer” (KYC) mechanism to ensure positive identity of the participants on the AXEL blockchain. At account creation, users will disclose information about themselves during the sign up process, as well as information about the devices they are utilizing to connect to the AXEL blockchain.

“If PINApp is used with AXEL, device information can be collected through the PINApp and stored in the users’ private chain. Information about the device such as the MAC code will be kept in the users’ private ledger (chain) to ensure that if someone were to steal their login and access information, they would be unable to access the AXEL network because the device they are utilizing is not registered to the network. In a like fashion, a person using a registered device may not access the AXEL network without the proper login and authentication information.

“The AXEL blockchain can utilize functional components of the PINApp, and it may also include functional components of the Digital Certification Analyzer (“DCA”)-as set forth in U.S. Pat. Nos. 9,419,965; 9,565,184; and 9,723,090-to prevent unauthorized access of digital content. For example, the PINApp could be utilized to perform device unification capabilities allowing AXEL participants to access the AXEL blockchain from remote devices such as smartphones, tablets, and the like. The DCA functional components could be utilized in support of the AML/KYC implementation as well as the multi-factor authentication mechanisms.”

There is additional summary information. Please visit full patent to read further.”

The claims supplied by the inventors are:

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

For additional information on this patent application, see: Ow, Benedict; Stiles, Richard; Tan, Anthony. Autonomous Exchange Via Entrusted Ledger Immutable Distributed Database. Filed September 20, 2021 and posted January 6, 2022. Patent URL: https://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PG01&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.html&r=1&f=G&l=50&s1=%2220220004538%22.PGNR.&OS=DN/20220004538&RS=DN/20220004538

(Our reports deliver fact-based news of research and discoveries from around the world.)