# Overcoming the Technological Barriers in the Blockchain Supply Chain for Small Carriers
## 3 Methodology and Materials
### Testing the Blockchain  
In our case, this ecosystem is not dependent on only one platform; the aim is to make it universal and usable for multiple platforms. Therefore, the final consensus may differ. The challenge will be enabling data sharing and validation across multiple blockchain-based platforms. In our case study, we have used the Hedera platform our own account. A Hedera account is a discrete entity, a specific sort of item, maintained in the ledger, which is responsible for holding tokens. Accounts have the ability to store three types of tokens on the Hedera network: the native Hedera fungible token (HBAR), custom fungible tokens, and custom non-fungible tokens (NFTs). Stakeholders engage with the network by submitting transactions to alter the state of the ledger or query requests to retrieve data from the ledger. The majority of transactions and inquiries incur a transaction fee, which is denominated in HBAR or another cryptocurrency. While users can generate custom tokens on the Hedera network, the native HBAR token does not have a corresponding token ID. To be able to confirm the transaction, each stakeholder should also have an electronic wallet. A basic requirement for the implementation and use of this network is the creation of a user account. The Hedera platform itself enables testing of its network within the so-called testnet. Each stakeholder or player in the supply chain should have an account on a distributed ledger platform with a unique Account ID. This ID, together with the HEX and DER keys, is crucial during the processing of the transaction, see Figure 13.  
Figure 12: Principles of measuring data processing to transaction into a blockchain.  
Figure 13: The account information with private and public keys.  
The transfer information was subsequently verified in the Hedera network, and this information is already stored there and unchanged, see figure.  
Since no consortium network was created for supply chain and blockchain in our case, we used the test network of the Hedera testnet platform, where we tested the transaction of the outputs of a file containing information about the required temperature from a vehicle transporting perishable food or temperature-sensitive goods.  
The client application will generate a transaction, enabling it to incorporate a message and subject. The message may encompass a particular operation, solely consisting of a hash, or be any other byte array pertinent to the client program. Every application must utilise one or more subjects. The transaction can be delivered to one or more mainnet nodes, similar to other services. The mainnet node will verify that the transaction contains the required information, such as signature(s), payments, and inputs. It will then confirm to the client application that the transaction has passed the precheck stage.  
The example output of file creation in the Hedera network is:  
* Account Id: 0.3994950
* fileCreateTxId: [EMAIL_ADDRESS]
* txExplorerUrl: [[https://[EMAIL_ADDRESS]](https://[EMAIL_ADDRESS])]([https://[EMAIL_ADDRESS]](https://[EMAIL_ADDRESS])) 49011113 (accessed on 10 April 2024)
* localFileContents: The required temperature during transport was 5.2 Celsius. This is to the requirements.
* networkFileContents: The required temperature during transport was 5.2 Celsius. This is to the requirements.  
The transaction is possibly verified in the ledger explorer (see Figure 14); in this case, we have used Hashscan.io.  
This example has shown that technologically, it is not a problem to apply blockchain technology; rather, we see the problem in the necessity of creating such an ecosystem for technologically limited stakeholders (e.g., small carriers), which could be called blockchain-ready after meeting the requirements that will be imposed in terms of the aforementioned standardisation.