Search iota tangle8/13/2023 Including TAG of transaction in the advertisement data for zero configuration on receivers.Cryptocurrencies have been rising in popularity since the inception of Bitcoin in 2009. What's next for Storing encrypted sensor data to the IOTA Tangle. The system works end-to-end, although it's not robust against malformed data etc. The usual silliness when working with crypto RNG and bitwise operations with several languages and platforms. Setting up a full node would require a rather high-performance VPS and manually contacting people to set up the neighbor nodes. IOTA's example for doing proof-of-work has been broken, as it relies on some FFI libraries which won't compile after a recent update to Chrome's V8 engine. Like serverside, the code is done with NodeJS. The receiver code is likewise available on GitHub and npm. Serverside code is available on GitHub and npm. Ask Otso for a demo.ĭata is interfaced to the Tangle with a VPS running on DigitalOcean. The application is built on top of Nordic Semiconductor SDK 12.3 using C. AES encryption was added for this hackathon. On sensor side RuuviTag-fw v1 is used as a base. The BLE advertisements could contain a tag which would be broadcasted to the Tangle to let owner of the data to search for their data.įinally the owner of the data searches for transaction incoming to his analytics address, downloads transactions and decrypts the data. In this hackathon the server is configured to attach advertisements with matching headers to the Tangle and send every transaction to specific address, but in production the server could attach all incoming data and payment for data delivery could be arranged over the Tangle. Gateway sends data to the server, and server converts hex to IOTA's trinary format which is then attached as a message to the IOTA transactions. A gateway has to send BLE advertisement data to a server which attaches the data to Tangle, but the gateway doesn't have to care about owner of sensor or target IP address of the server. The broadcast data format has trailing 24 bits all zeroes, so chance of forged transmission being decrypted into something reasonable with matching tail is miniscule.ģ) Delivering data is solved via IOTA Tangle. Random nonce prevents attacker from mapping cryptographic outputs to known conditions.Ģ) Since the data is encrypted with unique key known only by owner of the device, authenticity can be verified by decrypting the data. Unique ID has to be read via NFC, which means that attacker requires physical access to the device. Finally each message is salted with additional 32-bit random nonce. The tag has encryption key which is salted with the Unique ID. Problem 1) is solved with RuuviTag's in-built AES-ECB-128 hardware, true HW RNG and a random 64 bit ID burned in the silicon. Sending and storing sensor data over untrusted network has three big issues:ġ) Confidentiality of the data, how the data can be kept private.Ģ) Authenticity of the data, how receiver can trust the readings.ģ) Delivering the data, how the data can be sent to intended receiver. The challenge is to get data from a tag in unknown location to owner's servers, while maintaining the confidentiality and integrity of the data. RuuviTags are used in logistics applications where the tags move outside the owner's infrastructure.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |