## 4 Testing and Result Discussion
### System Deployment in the Real Scenario
Status: this tab is used to visualize information about bandwidth usage over time and network traffic during a specific period. 2. Files: used to show the files that have been uploaded onto the node, along with what characteristics has each of them, like the IPFS link to access it or its identifying hash. 3. Explore: used to see the Merkle tree resulting from the application of the InterPlanetary Linked Data. 4. Peers: it is useful to explore the number of users present in the IPFS network where the information is being uploaded. 5. Setting: this tab is used for the IPFS node system settings, such as the public gateway used for data requests or the file pinning so it will not be garbage-collected. Figure 14: Appearance of the dashboard in the IPFS node. The four files that have been included in Figure 14, which are part of the testing activities carried out, can be accessed via IPFS public gateways. Due to the decentralized nature of IPFS, each of the nodes that make part of the network are servers themselves that share the available information among the peers that are part of the IPFS network. The public gateway that has been chosen to visualize the data is ipfs.io, so the four files that have been included as a test in this node will be accessed with the following Uniform Resource Identifiers (URIs):  
Monitoring cattle from the distance (Figure 12):  
[[https://ipfs.io/ipfs/QmU7](https://ipfs.io/ipfs/QmU7) YMxFUv6 bsD7 Em78 HvNm9 CS2 pP7 NW4 mmjeSfpgMr5 Tm]([https://ipfs.io/ipfs/QmU7](https://ipfs.io/ipfs/QmU7) YMxFUv6 bsD7 Em78 HvNm9 CS2 pP7 NW4 mmjeSfpgMr5 Tm)  
Monitoring cattle from the distance twice:  
[[https://ipfs.io/ipfs/QmZN6](https://ipfs.io/ipfs/QmZN6) hE4N9E6v1 KKsBJxshBkhrfc1 TJuDNyuW1m4v6 bp11]([https://ipfs.io/ipfs/QmZN6](https://ipfs.io/ipfs/QmZN6) hE4N9E6v1 KKsBJxshBkhrfc1 TJuDNyuW1m4v6 bp11)  
Monitoring cattle at a close distance: (Figure 13):  
[[https://ipfs.io/ipfs/QmXYZj9](https://ipfs.io/ipfs/QmXYZj9) zcjrlrlxzEQc2 Feryxq8 UM1 Mg1 jHutmV9 yPp2 gQ]([https://ipfs.io/ipfs/QmXYZj9](https://ipfs.io/ipfs/QmXYZj9) zcjrlrlxzEQc2 Feryxq8 UM1 Mg1 jHutmV9 yPp2 gQ)  
Figure 12 formatted to Base64 and included in blockchain data:  
[[https://ipfs.io/ipfs/QmZgpKxQdLiBjtzUPoWhsKWDc574](https://ipfs.io/ipfs/QmZgpKxQdLiBjtzUPoWhsKWDc574) Lh7 aFGb7 ujDBrV4 Vo]([https://ipfs.io/ipfs/QmZgpKxQdLiBjtzUPoWhsKWDc574](https://ipfs.io/ipfs/QmZgpKxQdLiBjtzUPoWhsKWDc574) Lh7 aFGb7 ujDBrV4 Vo)  
From the previous examples, the last one must be further discussed due to the objectives of the manuscript. As it can be seen in the piece that has been included below (the previous link shows that the Base64 formatted image is too long to fit it in this manuscript) it contains the information parts (hash, previous hash, data, timestamp and nonce) described before. Note that the image has been inserted right after the first block that has \"Genesis\" as data and \"0\" as the previous hash (since there is no previous hash to take the hash from). _[ ] /hash\": \"36b81a86281783 aa06 ad46b269b11a57 fe33c784f17888 ffc0a5674399c4b46\", \"previousHash\": \"0\", \"data\": \"Genesis\", \"timeStamp\": 1662373905696, \"nonce\": 0 ] /hash\": \"28174f1646973 ecbc25 ee6203579a74 ca595b13 aa0862 ac42d614 ce94 ac23\", \"previousHash\": \"431695 ec233 be553 bb6 afe3c9470764 bcb11d12978 ad7d91e9b9 cc8e701a\", \"data\": \"data\": \"data\": \"data\": \"[[http://png.base64,iVBORw0](http://png.base64,iVBORw0) KG0 AAAANSUhIElgAAAAocA]([http://png.base64,iVBORw0](http://png.base64,iVBORw0) KG0 AAAANSUhIElgAAAAocA) {...} ] /BJRUSErklggg\u003d\u003d\", \"timeStamp\": 1662373905728, \"nonce\": 0 ]node. In the case of this manuscript, a Public Gateway Cache website [51] was used for this purpose. After caching the information via this web site, the data was easy to access in an almost immediate manner. As for the experimental analysis, and as it has been previously described, there were several experiments that were run:  
1.