Service Contract

In this section, we will explain how to integrate our ZKP scheme into an IoT devices integration

Background:

Service Contract:

A program designed to automate interactions between various IoT devices within a decentralized network.

Unix time:

Unix time is a widely used system for representing date and time in computing. For more information, please read https://en.wikipedia.org/wiki/Unix_time

Adversary Model:

This system operates in a decentralized environment, meaning that device owners are independent and do not trust each other. However, they do trust that the programs developed by the IoT device manufacturers (e.g., camera or drone manufacturers) are secure. Trust is not extended to individuals who have purchased the devices from the manufacturers.

Example Scenario:

Assume there are four IoT devices, each with distinct functionality and firmware. The Zero-Knowledge Proof (ZKP) scheme discussed in the previous section ensures that each device performs its designated functions reliably.

• Device 1 provides functionality 1 by executing program 1.

• Device 2 provides functionality 2 by executing program 2.

• Device 3 provides functionality 3 by executing program 3.

• Device 4 provides functionality 4 by executing program 4.

These devices are integrated into an automation scenario as follows:

An alarm is triggered upon receiving inputs from both a drone and a camera device, with each device obtaining data from a GPS module.

Sample code in FidesInnova:

The Service Contract code for the above scenario can be created using FidesInnova Blockly,

This code can be created through the web panels of every FidesInnova Node.

• zk-IoT

• TrustSense

• EnergyWise

• MotionCertified