5. Get Started
This section will provide you with all the required information and tools to start developing your Dapp using verifiable IoT data from the IoTeX Real-world Data Oracle network.


Please make sure you read the Real-world Data Oracle Overview and Architecture to get a general idea of what are the key components. For any questions join the dedicated discord channel.


To build a Dapp based on verifiable data from real-world devices like Pebble Tracker, you are supposed to just fetch the device data you need from the Real-world Data Oracle network (using the dedicated GraphQL endpoint) and send it to your Dapp contract.
Below is the development workflow
In this case, you as the developer will get one or more simulated device identities (IMEI+Private key) from the IoTeX team
As a developer, you do that part too
As a developer, you do this step too: you use the portal, where you "add" new devices to your development "Owner account".
As a developer, you will use a web tool to simulate the devices sending data to TruStream. When devices send new data to TruStream, the owner account of those devices gets billed.
Finally, your Dapp will fetch the data messages from the GraphQL endpoint of the Real-world Data Oracle network, based on the device IMEI/Owner account, and use them for the frontend and the smart contract logic.
When fetching device data from the TruStream network, that data has already been verified in a decentralized way (i.e. the data has not been tampered with and the device that signed the data was actually a Pebble Tracker shipped by IoTeX).
However, depending on your Dapp, you have 2 options:
  1. 1.
    You (and your users!) trust your backend and the Data Oracle endpoint, so you consider the data "trusted" when it's received in your Dapp smart contract.
  2. 2.
    You do not trust your backend and/or the Data Oracle endpoint, and you re-verify the device data upon reception in your contract
Copy link