Machine and system for making liquid or semi-liquid food products

1. A production system for making liquid or semi-liquid products, comprising:

a machine for making liquid or semi-liquid food products, comprising:

a first processing container for processing a basic liquid or semi-liquid product and defining a processing chamber;

at least one sensor, configured to measure an operating parameter of the machine;

a processing and control unit, operatively connected to the at least one sensor and comprising a data transfer module configured for receiving and transmitting data captured by the at least one sensor,

a code reader;

a write module configured for writing information to a distributed architecture database having a distributed ledger configuration;

wherein the data transfer module is configured to transmit data captured by the at least one sensor to the write module;

wherein the data captured by the at least one sensor includes a parameter of a quantity of the basic liquid or semi-liquid product fed into, present in or derived from, the first processing container, wherein the data transfer module is configured to transmit to the write module at least the following information for writing on the distributed architecture database:

data relating to a code present on at least one feed container containing the basic liquid or semi-liquid product or other basic ingredients intended for supply to the first processing container and scanned by the code reader;

the parameter of the quantity of the basic liquid or semi-liquid product;

a plurality of processing nodes defining the write module as a function of the data received from the data transfer module.

2. The production system according to claim 1 , comprising a stirrer for mixing the product in the first processing container.

3. The production system according to claim 1 , comprising a thermal system, comprising a heat exchanger associated with the first processing container.

4. The production system according to claim 1 , wherein the write module is defined by a “smart contract” program.

5. The production system according to claim 1 , wherein the at least one sensor is a sensor configured to capture a weight of a quantity of basic, liquid or semi-liquid product contained in the first processing container.

6. The production system according to claim 1 , wherein the at least one sensor is a level sensor configured to capture a level of a volume of the basic, liquid or semi-liquid product contained in the first processing container.

7. The production system according to claim 1 , wherein the at least one sensor is a sensor configured to capture a quantity of the basic, liquid or semi-liquid product fed into the first processing container.

8. The production system according to claim 1 , wherein the at least one sensor is a sensor configured to capture a quantity of the basic, liquid or semi-liquid product withdrawn from the first processing container.

9. The production system according to claim 1 , wherein the at least one sensor is a flow sensor for measuring a flow of the basic liquid or semi-liquid product or the other basic ingredients into or out of the first processing container.

10. The production system according to claim 1 , wherein the processing and control unit comprises a processing module and a memory containing processing software which defines a smart contract program configured to implement a smart contract, the smart contract program being processed by the processing module.

11. The production system according to claim 10 , wherein the processing software defining the smart contract program is configured to store information received from the data transfer module to the distributed architecture database.

12. The production system according to claim 10 , wherein the processing software defining the smart contract program is configured to store information to the distributed architecture database, based on the data received from the data transfer module.

13. The production system according to claim 10 , wherein the processing software defining the smart contract program is configured to read and/or write information, as a function of the data received from the data transfer module, from and/or to the distributed architecture database, the distributed architecture database having a blockchain configuration.

14. The production system according to claim 10 , wherein the processing module defines a processing node of the distributed architecture database.

15. The production system according to claim 1 , wherein the processing nodes are defined by processors which are external relative to the machine.

16. The production system according claim 15 , wherein the write module is defined by a smart contract program, run by the processing nodes and configured to read and/or write information relating to the data captured by the at least one sensor from and/or to the distributed architecture database.

17. The production system according to claim 1 , wherein the distributed architecture database having the distributed ledger configuration has a blockchain configuration, and comprises information grouped in a plurality of interconnected information blocks.

18. The production system according to claim 17 , wherein the information blocks are interconnected by cryptographic algorithms.

19. The production system according to claim 17 , wherein the distributed architecture database comprises information about a presence of tokens to specific electronic addresses and the write module is configured to perform token transactions between predetermined electronic addresses, and wherein the write module is configured to perform the token transactions as a function of the data received from the data transfer module relating to the data captured by the at least one sensor.

20. The production system according to claim 17 , wherein the distributed architecture database comprises information about a presence of tokens to specific electronic addresses and the write module is configured to perform token transactions between predetermined electronic addresses, and wherein the processing nodes are configured to generate further tokens and to assign the further tokens to a selected electronic address as a result of adding a new information block to the distributed architecture database.

21. The production system according claim 20 , wherein the selected electronic address corresponds to an electronic address associated with one of the processing nodes which is first to verify and grant an enable to add the new information block to the distributed architecture database.

22. The production system according to claim 1 , wherein the distributed architecture database comprises information about a presence of tokens to specific electronic addresses and the write module is configured to perform token transactions between predetermined electronic addresses.

23. The production system according to claim 1 , wherein the distributed architecture database of the distributed ledger type is built on an Ethereum, Ethereum Classic, or Iota, or Eos, or NEO, or Waves, or Qtum, or NEM, or Multiversum or R3 Corda or R3 Corda enterprise or Hyperledger or Ripple or Stellar platform.

24. The production system according to claim 1 , wherein the processing nodes comprise a first set of processors which are configured to keep a complete copy of the distributed architecture database, and a second set of processors which are configured to keep a partial copy of the distributed architecture database.

25. The production system according to claim 1 , wherein the distributed architecture database having the distributed ledger type has a blockchain configuration and comprises information grouped in a plurality of interconnected blocks, each block of the plurality of blocks having a time-marking associated therewith.

26. The production system according to claim 1 , wherein the processing nodes are configured to define nodes of the distributed architecture database operating with a consensus protocol to enable writing to the distributed architecture database which is selected from the following types:

proof of work;

proof of stake;

Corda consensus protocols (configured to reach consensus on the specific “state object”);

CFT (Crash fault tolerant), preferably implemented with Kafka and/or Zookeeper;

Solo;

BFT (byzantine Fault Tolerance);

PBFT (practical BFT);

SBFT (simplified BFT);

Raft;

Sumeragi;

PoET (proof of Elapsed Time);

Permissioned Voting-based.