Amazing patent describes the use of quantum dots for all security concerns of a DLT Blockchain application.
The patent describes a fully integrated hack-proof ecosystem.
IMO, an ultimate use case would be securing any cryptocurrency such as Bitcoin.
Below are 20 practical use cases from the bottom of the patent:
0046] Hereinafter are exemplary use cases that further illustrate the functionality and operations of the systems and methods of the present disclosure. The use cases are best described from a role-based perspective, where a company can be an owner, vendor, distributor, and/or reseller of a product, and a person can be a buyer, agent, seller, and/or owner. FIG. 4 is a logical diagram of roles and persons that can participate in the systems and methods of the present disclosure. Further, the following rules are observed: [0047] Products are assigned objects (QDX.TM. "dotted"
. [0048] Identification, authentication and authorizations transactions are written to the QDX.TM. Ledger. [0049] Product metadata is stored in the quantum dot database (QD). [0050] QDX.TM. dot manufacturing information is stored in the QD. [0051] Transactional information for assigned objects (products) is stored in the QL. [0052] Certification is through authentication. [0053] Validation is through authentication. [0054] Identity is through identification. [0055] Transfer of products, funds (or any other product to person or location) is authorization.
[0056] Use Case 1: A buyer wants to authenticate her product so that she knows it is really from the proper company. A buyer can use the systems and methods of the present disclosure to validate a product to ensure the product is authentic and not counterfeit.
[0057] Use Case 2: A company wants to authenticate its products through its supply chain to prevent counterfeiting. The company can use the systems and methods of the present disclosure to authenticate the entire supply chain so that its product can be verified to be authentic and not counterfeit.
[0058] Use Case 3: A company wants to connect its products to customers so that it can provide brand value and understand customer preferences. The company can use the systems and methods of the present disclosure to connect customers to its product to build company good will and customer loyalty. The company may also tap into or understand customer preferences so that it can tailor its offerings and sales strategy accordingly.
[0059] Use Case 4: A company wants to identify its products so that it can protect itself from product liability events. Products sold by a company can be identified to avoid becoming liable for inferior counterfeit products.
[0060] Use Case 5: A vendor wants to identify products so that it can make sure they are certified from the manufacturer. A manufacturer can use the systems and methods of the present disclosure to certify its products. A vendor can use the systems and methods of the present disclosure to identify the products it plans to buy and resell to ensure it is dealing with certified (authentic) products.
[0061] Use Case 6: A buyer wants to associate his identity with a product so that he can prove his ownership. The owner of a product can use the systems and methods of the present disclosure to become associated with a product to demonstrate ownership of the product.
[0062] Use Case 7: An official wants to identify a product to determine ownership. An official can use the systems and methods of the present disclosure to verify the identity of the product's owner.
[0063] Use Case 8: A buyer wants to authorize the transfer of ownership of a product. The buyer can use the systems and methods of the present disclosure to transfer ownership of a product to itself. A chain of ownership can be established in this manner.
[0064] Use Case 9: A company wants to authorize the transfer of ownership of a product. The company can use the systems and methods of the present disclosure to transfer ownership of its product to a buyer.
[0065] Use Case 10: A company wants to authorize the value of a product so that it can sell it. The company can use the systems and methods of the present disclosure to establish the value of a product to ensure that the marketplace can be aware of attempts to under-value the product by counterfeits or grey market products.
[0066] Use Case 11: An owner wants to authorize the value of a product so that she can sell it. The owner can use the systems and methods of the present disclosure to establish the value of a product it owns.
[0067] Use Case 12: A seller wants to authenticate the buyer of a product. The seller can use the systems and methods of the present disclosure to authenticate the buyer and proper payment before transfer of the product.
[0068] Use Case 13: A buyer wants to authenticate a product before buying it. A buyer can use the systems and methods of the present disclosure to authenticate a product to avoid inadvertently buying a counterfeit product.
[0069] Use Case 14: A buyer wants to authorize funds to buy a product. A buyer can use the systems and methods of the present disclosure to authorize the transfer of currency to buy a product.
[0070] Use Case 15: A seller wants to authenticate buyer funds before selling a product. A seller can use the systems and methods of the present disclosure to validate the buyer's payment before the ownership of the product transfers hands.
[0071] Use Case 16: A manufacturer wants to assign a manufacturers BatchID (MBID) to a QuantumID for an assigned object.
[0072] Use Case 17: A vendor wants to authenticate a manufacturers BatchID (MBID) for a product (AO).
[0073] The following rules may be associated with Quantum Dot manufacturing: A QDX.TM. production license (QPL) can be assigned to all dot manufacturers (DMs). All dot manufacturers will be assigned QDX.TM. Reactor ID (QRID) which are registered to each quantum reactor (QR). A dot manufacturer has a specification (SPEC) for the creation of the QDO (Quantum Dot Object). A specification contains a QD recipe (QR) for the reactor process (RP) which contains materials, materials processes (MP), and expected output (EO). Each materials process (MP) contains process stages (PS) which include temperature, pressure, time, and state). Expected outputs contain the measurement data (MD) to allow for validation and authentication of the quantum dot object (QDO) to allow for assigning the quantum dot identifier (QID) for each reactor production batch (RPD).
[0074] The following exemplary use cases for the systems and methods of the present disclosure are associated with quantum dot manufacturing.
[0075] Use Case 18: A dot manufacturer (DM) wants to manufacture quantum dots using the QDX.TM. reactor (QDR) to a specification.
[0076] Use Case 19: An original dot manufacturer (ODM) wants to assign QID to every batch of dot database (QD) made by any dot manufacturer (DM).
[0077] Use Case 20: An original dot manufacturer (ODM) wants to monitor and perform analytics on all original dot manufacturer (ODM), quantum database recipe (QR), and quantum database (QD)
The patent describes a fully integrated hack-proof ecosystem.
IMO, an ultimate use case would be securing any cryptocurrency such as Bitcoin.
Below are 20 practical use cases from the bottom of the patent:
0046] Hereinafter are exemplary use cases that further illustrate the functionality and operations of the systems and methods of the present disclosure. The use cases are best described from a role-based perspective, where a company can be an owner, vendor, distributor, and/or reseller of a product, and a person can be a buyer, agent, seller, and/or owner. FIG. 4 is a logical diagram of roles and persons that can participate in the systems and methods of the present disclosure. Further, the following rules are observed: [0047] Products are assigned objects (QDX.TM. "dotted"
. [0048] Identification, authentication and authorizations transactions are written to the QDX.TM. Ledger. [0049] Product metadata is stored in the quantum dot database (QD). [0050] QDX.TM. dot manufacturing information is stored in the QD. [0051] Transactional information for assigned objects (products) is stored in the QL. [0052] Certification is through authentication. [0053] Validation is through authentication. [0054] Identity is through identification. [0055] Transfer of products, funds (or any other product to person or location) is authorization. [0056] Use Case 1: A buyer wants to authenticate her product so that she knows it is really from the proper company. A buyer can use the systems and methods of the present disclosure to validate a product to ensure the product is authentic and not counterfeit.
[0057] Use Case 2: A company wants to authenticate its products through its supply chain to prevent counterfeiting. The company can use the systems and methods of the present disclosure to authenticate the entire supply chain so that its product can be verified to be authentic and not counterfeit.
[0058] Use Case 3: A company wants to connect its products to customers so that it can provide brand value and understand customer preferences. The company can use the systems and methods of the present disclosure to connect customers to its product to build company good will and customer loyalty. The company may also tap into or understand customer preferences so that it can tailor its offerings and sales strategy accordingly.
[0059] Use Case 4: A company wants to identify its products so that it can protect itself from product liability events. Products sold by a company can be identified to avoid becoming liable for inferior counterfeit products.
[0060] Use Case 5: A vendor wants to identify products so that it can make sure they are certified from the manufacturer. A manufacturer can use the systems and methods of the present disclosure to certify its products. A vendor can use the systems and methods of the present disclosure to identify the products it plans to buy and resell to ensure it is dealing with certified (authentic) products.
[0061] Use Case 6: A buyer wants to associate his identity with a product so that he can prove his ownership. The owner of a product can use the systems and methods of the present disclosure to become associated with a product to demonstrate ownership of the product.
[0062] Use Case 7: An official wants to identify a product to determine ownership. An official can use the systems and methods of the present disclosure to verify the identity of the product's owner.
[0063] Use Case 8: A buyer wants to authorize the transfer of ownership of a product. The buyer can use the systems and methods of the present disclosure to transfer ownership of a product to itself. A chain of ownership can be established in this manner.
[0064] Use Case 9: A company wants to authorize the transfer of ownership of a product. The company can use the systems and methods of the present disclosure to transfer ownership of its product to a buyer.
[0065] Use Case 10: A company wants to authorize the value of a product so that it can sell it. The company can use the systems and methods of the present disclosure to establish the value of a product to ensure that the marketplace can be aware of attempts to under-value the product by counterfeits or grey market products.
[0066] Use Case 11: An owner wants to authorize the value of a product so that she can sell it. The owner can use the systems and methods of the present disclosure to establish the value of a product it owns.
[0067] Use Case 12: A seller wants to authenticate the buyer of a product. The seller can use the systems and methods of the present disclosure to authenticate the buyer and proper payment before transfer of the product.
[0068] Use Case 13: A buyer wants to authenticate a product before buying it. A buyer can use the systems and methods of the present disclosure to authenticate a product to avoid inadvertently buying a counterfeit product.
[0069] Use Case 14: A buyer wants to authorize funds to buy a product. A buyer can use the systems and methods of the present disclosure to authorize the transfer of currency to buy a product.
[0070] Use Case 15: A seller wants to authenticate buyer funds before selling a product. A seller can use the systems and methods of the present disclosure to validate the buyer's payment before the ownership of the product transfers hands.
[0071] Use Case 16: A manufacturer wants to assign a manufacturers BatchID (MBID) to a QuantumID for an assigned object.
[0072] Use Case 17: A vendor wants to authenticate a manufacturers BatchID (MBID) for a product (AO).
[0073] The following rules may be associated with Quantum Dot manufacturing: A QDX.TM. production license (QPL) can be assigned to all dot manufacturers (DMs). All dot manufacturers will be assigned QDX.TM. Reactor ID (QRID) which are registered to each quantum reactor (QR). A dot manufacturer has a specification (SPEC) for the creation of the QDO (Quantum Dot Object). A specification contains a QD recipe (QR) for the reactor process (RP) which contains materials, materials processes (MP), and expected output (EO). Each materials process (MP) contains process stages (PS) which include temperature, pressure, time, and state). Expected outputs contain the measurement data (MD) to allow for validation and authentication of the quantum dot object (QDO) to allow for assigning the quantum dot identifier (QID) for each reactor production batch (RPD).
[0074] The following exemplary use cases for the systems and methods of the present disclosure are associated with quantum dot manufacturing.
[0075] Use Case 18: A dot manufacturer (DM) wants to manufacture quantum dots using the QDX.TM. reactor (QDR) to a specification.
[0076] Use Case 19: An original dot manufacturer (ODM) wants to assign QID to every batch of dot database (QD) made by any dot manufacturer (DM).
[0077] Use Case 20: An original dot manufacturer (ODM) wants to monitor and perform analytics on all original dot manufacturer (ODM), quantum database recipe (QR), and quantum database (QD)
