Blockchainizing the Data
The following pages describe the process through which Airtrace stores the Evidences of the data sent by the user's sensors in the Blockchain.
Hash uploading
Instead of uploading crude data sent by the user to the Blockchain, Airtrace uploads that data's hash to the blockchain, making the contents of the data private, this process leaves a permanent trace of the user's data in the Blockchain.
Whenever the user needs to check the integrity of some data that was already traced, it is done via taking the hash of the data that that the user has, and comparing it to the hash that is found in the blockchain as a trace of the user's data.
Commit interval
While the user's sensors are the ones that upload the data to the links, the data is stored in groups and is periodically uploaded to the blockchain, this grouping of sensors can be done via Plain Projects or Deployments.
When creating either a Plain Project or a Deployment, the user will be asked to specify a commit interval for that entity from the list of valid intervals.
The selected value for the commit interval will be the number of minutes spent in between Blockchain transactions. All of the data the user sends to a link is stored, then zipped, then hashed, and lastly the hash of the data is uploaded to the Blockchain.
We recommend the users who want their projects more traceable select a lower value for the commit interval, as the larger the value the more time will pass in between transactions, and thus the less secure the project will be.
Valid intervals
The list of valid values for a commit interval in minutes is as follows:
[0, 1, 5, 10, 15, 30, 60, 120, 180, 240, 360, 480, 720, 1440, 2880, 4320, 5760, 7200, 10080]
Example
If a Deployment's commit_interval is set to 30, even though the sensors contained in that interval can upload data through their links around the clock, the data will only be traced every 30 minutes.
When it is time for that Deployment, it's commit interval will be triggered, and all of the data that was uploaded during the last 30 minutes will be traced. A Blockchain Transaction will be generated which the user can check the status of via the API.
More information on Traces can be found in Traces
Commit interval 0
If the user specifies 0 as the value of the commit interval during the creation of a Deployment or Plain Project, then the sensors inside that Deployment or Plain project will immediately trigger a Blockchain transaction every time they upload data through their links.
Last updated