Refine
Year of publication
- 2019 (86) (remove)
Document Type
- Conference Proceeding (86) (remove)
Conference Type
- Konferenzartikel (71)
- Konferenz-Abstract (9)
- Konferenzband (3)
- Sonstiges (3)
Keywords
- Heart rhythm model (5)
- Modeling and simulation (5)
- Education in Optics and Photonics (3)
- RoboCup (3)
- Cryoballoon catheter ablation (2)
- Ecodesign (2)
- Gamification (2)
- Hochschuldidaktik (2)
- Human Computer Interaction (2)
- Human Resources (2)
Institute
- Fakultät Elektrotechnik, Medizintechnik und Informatik (EMI) (ab 04/2019) (42)
- Fakultät Medien und Informationswesen (M+I) (bis 21.04.2021) (18)
- Fakultät Wirtschaft (W) (17)
- Fakultät Maschinenbau und Verfahrenstechnik (M+V) (14)
- ivESK - Institut für verlässliche Embedded Systems und Kommunikationselektronik (9)
- ACI - Affective and Cognitive Institute (4)
- CRT - Campus Research & Transfer (3)
- INES - Institut für nachhaltige Energiesysteme (3)
- WLRI - Work-Life Robotics Institute (3)
- IMLA - Institute for Machine Learning and Analytics (2)
Open Access
- Closed Access (54)
- Open Access (31)
- Bronze (6)
Blockchain frameworks enable the immutable storage of data. A still open practical question is the so called "oracle" problem, i.e. the way how real world data is actually transferred into and out of a blockchain while preserving its integrity. We present a case study that demonstrates how to use an existing industrial strength secure element for cryptographic software protection (Wibu CmDongle / the "dongle") to function as such a hardware-based oracle for the Hyperledger blockchain framework. Our scenario is that of a dentist having leased a 3D printer. This printer is initially supplied with an amount of x printing units. With each print action the local unit counter on the attached dongle is decreased and in parallel a unit counter is maintained in the Hyperledger-based blockchain. Once a threshold is met, the printer will stop working (by means of the cryptographically protected invocation of the local print method). The blockchain is configured in such a way that chaincode is executed to increase the units again automatically (and essentially trigger any payment processes). Once this has happened, the new unit counter value will be passed from the blockchain to the local dongle and thus allow for further execution of print jobs.