End devices identities in an IoT BC network

Nikos Karamolegkos


I want to build a smart building IoT BC network and I am working to the network architecture. At this point I have built the IoT infrastructure and I am looking to integrate the BC idea. Specifically, the end devices (EDs) are equipped with sensors (these device can not run fabric) and the data are transmitted via 802.15.4 to IoT GW (raspberry) which sends them to the DB. In order to integrate the BC concept I am thinking to use a fabric client app in the IoT GW which will send (update) the date to ledger. Is this a good approach? I was wondering how the EDsĀ  can prove their identity through the GW in order to match with the information defined in smart-contract? I can use fabric-ca to create ED identities but these identities would be in the IoT GWs which will match the ED ID with the fabric identity (through the client app running in GWs). Is this the best I can do?

Also, in the BC network would be users which will have access to the sensor data written by the EDs. As I have understood these user will be fabric client application too with specific right policies (read &/or write). Should I make a different organization for them?

I have experience in IoT but not in BC so any idea, example, application or use case are welcome in order to design my BC architecture.

Thank you for your time,

Nikos Karamolegkos
R & D engineer at ICS-FORTH
Telecommunications and Networks Lab (TNL)

Join fabric@lists.hyperledger.org to automatically receive all group messages.