[OpenTRV-dev] Blockchain for anti-tamper and non-repudiatiot of valuable IoT data

Bruno Girin brunogirin at gmail.com
Mon Sep 28 10:13:24 BST 2015

On 28 September 2015 at 09:49, Damon Hart-Davis <damon at opentrv.uk> wrote:

> >
> > In a chat with Viv today (helping us with out business plan, but also a
> blockchain whiz) the possibility of using a blockchain mechanism to provide
> at least these two features in the long-term data store came up.
> >
> > I've been trying to understand blockchain to see if we could use it for
> our own purposes and I can't see how it would be used for that particular
> use case. If I understand things correctly, blockchain is a distributed
> ledger where every transaction is signed and all nodes have a full copy of
> the ledger. I think there are also variations to allow some nodes to only
> have a partial copy of the ledger.
> The data would be authenticated from node to concentrator and then signed
> there.

OK, that makes sense. That said, is there a risk of MitM attack between the
node and concentrator that could circumvent that or should that be dealt
with by the authentication mechanism?

> > I'm not sure where this ledger would go: it can't be stored on the
> sensors nodes as they don't have the capacity for it and even concentrators
> would be hard pressed to deal with it. That leaves a data platform but
> doesn't that go against the OpenTRV principle of having something that can
> work without that data platform?
> The long-term data store would be blockchain.  One copy with the
> factory/canteen/etc, one with auditors and one with (say) the H&SE.
> This has various neat features about soft real-time alerts, multiple
> copies off-site and un-tamperable.
> There are some issues of the speed of blockchain operations but there are
> possible solutions to that such as some simple batching.

OK so that raises other issues about data privacy and differentiated data
access. Considering use cases like this:
1. Customer has buildings in multiple jurisdictions with multiple H&S
enforcement agencies,
2. Customer changes auditors at some point in time,
3. Some of the data gathered should not be shared with external parties,
4. Customer leaves one location and moves to another one (they need to have
access to historical data at the old location until the date they left for
some time after that date, and access to historical and live data at the
new location the date they move in).

This means that you need to make it possible to share different parts of
the blockchain with different entities. How would that work?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opentrv.org.uk/pipermail/opentrv-dev/attachments/20150928/251fd67f/attachment-0001.html>

More information about the OpenTRV-dev mailing list