# How does BeefLedger interact with real world objects using IOT solutions? Digital ledgers need data feeds. One of those is the so called world of Internet of Things (IOT) solutions. ### Types of Sensors We are working with a diverse array of IOT solutions and sensors. These include: * Temperature sensors * Humidity sensors * Accelerometers * Weigh scales * In-Vehicle Monitoring Solutions * Smart ear-tags (animal health data etc.) * Standard animal ear tags (RFID) At present, we take data feeds from existing data systems. These function as Oracles. We are, however, very mindful of the data security implications of these kinds of centralised oracles, and will continue to work with IOT developers to progress strategies towards greater levels of decentralisation. ### RFID / NFC We've done a lot of work with RFID and NFC chip technologies. RFID are a very mature technology and is well-suited to asset identification and tracking, especially in large volume environments eg., boxed beef, packaged wine etc. Asset ERP systems utilising this technology is also relatively mature so we can bolt straight on if needed. BeefLedger has developed an RFID Scanner App (for Android), which sends data straight to the BeefLedger blockchain. The App is configured with its own Ethereum address to sign messages, and the setup supports the event ontology of the BeefLedger supply chain system. RFID's aren't so good for individual consumers. So, we also work with technologies more suited for use by individual consumers. NFC is one of those, as are QR Codes and Laava Smart Fingerprints (an optical scanning solution alternative to QR). ### Agnostic We are pretty much agnostic when it comes to the specific sensor or data capture interface. At the end of the day, it's about fitness for purpose and value for money. The fact that sensors and RFID chips all cost money really focuses businesses and consumers on what the value of data actually is for each of the actors involved. As the cost of IOT drops, we are sure many new use cases will be possible. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://beefledger.gitbook.io/beefhub/wip-how-does-beefledger-interact-with-real-world-objects-using-iot-solutions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.