...
- Ingo Friese, Deutsche Telekom (Convenor)
- Matteo Signorini, Excalibur
- Lancen Lachance, GlobalSign
- Keith Uber, GlobalSign
- Ivan Klimek, Excalibur
- Scott Shorter, ElectroSoft
- Jeff Stollman
- Frank Mildner, Deutsche Telekom
- Sal D'Agostino - IDMachines
Blockchain special
Matteo: We prepared some slides - depends how deep you want to go
...
Brief introduction to the topic
There are many approaches, so the The slides will show somereview varying approaches.
The easiest way to see the blockchain technology is as a trusted history.
Each transaction is linked to another transaction with the peers. For each transaction you have input and output.
Each transaction is signed. Each will have a hash that can be used to link and follow the history.
This was the first design, now we have more advanced technology that we will look at in a few minutes.
Q; If we believe that blockchain is a trusted piece, how can we resolve issues about identifying the right “Thing”?
- A: We have the history and some transactions - not necessarily money.
- It could be for exam unloading and loading a truck.
- It would be possible to examine the history for a given truck and its unload and load history.
I can define and retrieve also from the blockchain what is the current state of the truck.
I can see that there is an empty truck,
The technology that was designed after the blockchain is named etherium.
Architecture, data model:
...
We can see the material transactions as a meta coin
The problem is with scalability
if , however, scalability is a challenge.
If there is one device in my room, i have to access the global blockchain.
A light bulb could not handle the entire blockchain
Hyper cubes, multi-layer graphs and distributed databases where all the peers nodes interact with the blockchain.
Even if we hade the distributed blockchain, everyone could see the transactions of other parties.
This is unsuitable for B2B operations. there must a way to use a blockchains in such a way that “adept” is an IBM project to handle this. they
They define different blockchains
- a global network that cooperates with lower networks
...
Problems:
- Even though the solution is close to what we designed, we still have a strong cooperation - there is no privacy.
...
- IoT devices don’t use the blockchain for the data
...
- They use it to determine which peers can continue with which peers
Our solution can be used to identify the devices and examine their purposes also when we look for a device, we can’t say to look for a device, but we could look for a device and examine which features the device has.
...
- A: It depends on the technology that is used.
IBM uses the history after an initial registration (physical registration for example). This prevents unauthorized use.
The blockchain gives you trusted history and information about how valid the transaction may be. Relies on the ephemeral storage system
Concrete Example:
Concrete example: A sensor is transmitting a temperature value from time to time.
...
- A: IBM defined 2 types
- low power computing device: lightweight peer and
- high power: powerful peer
- A: Lightweight peer can offload work to a trusted high power peer to do the work, for example after a pairing operation.
...
if you want to encrypt data, if you don’t want to expose the transactions to the outside
...
What IBM designed was that the trust was formed at the beginning at making of the devices
We propose that you could analyze.
you need a bootstrap
- Bootstrap - a pin or password
...
- Pair two devices or nodes
these These two devices can keep in touch over time and keep their trust
if you loose the connection, you could define that it needs to be re-paired
Q: Is that based on the complexity or size of the blockchain? What’s driving the requirement that the trust needs to be re-paired?
...
- A: The device has an owner of the device.
- When a mobile phone is sold at retail, it could be notified to a blockchain to inform that the owner has chained.
- There could a different blockchain for ownership.
Q: Do you have a paper about this?
- A: Yes, we are working on a paper.
Q: Sal: this is distinct from the zero knowledge proof work in the past?
- A: Matteo: This is not connected to this work at this stage.
- We may look at it. Zero knowledge proof and blockchain has been looked at by IBM.
- Ingo: Looking forward to whitepaper with specific examples
Q: Sal: do you see the scale of the IoT to be a challenge? Big chains might be a challenge.
- A: Matteo: sure it is, that’s why we propose a distribute approach, to set limits on the size of the blockchain, for example 100 devices.
- E.g. if you have a big company with small devices that can’t handle large blockchains, you could establish mutual.
...
The protocol is irrelevant. You could rely on other nodes. It depends on the storage capabilities of a device. Is there enough memory to store? There is no standardization for the protocol level. The most productional example is bitcoin example.
Links related to our discussion
...
References:
- https://forum.ethereum.org/discussion/1634/tutorial-1-your-first-contract
- http://public.dhe.ibm.com/common/ssi/ecm/gb/en/gbe03620usen/GBE03620USEN.PDF