Presentation: https://wyocast.uwyo.edu/WyoCast/Play/05352b17b10143e494dbed5c85aea8c71d?playFrom=19380000

Slides: https://docs.google.com/presentation/d/1pOFwxMeQA_PvRu75yV2uHilA0rF571IpQ9TXWL8XSKo/

Inspiration

A Colorado company (http://flynorthgroup.com/en/home/) is building solutions on top of mesh presently to do surveillance and surveying of remote locations. Use of AI to identify keep events and report them. Our system is a large value add as it enables an outside auditor to permission any companies device and drastically improves key data integrity by removing all doubt as to it's origin and immutability.

A demos of the product

Fire: http://flynorthgroup.com/360/DeepRed-ForestryREV9/

Power: http://flynorthgroup.com/360/DeepRed-ItuangoREV3/

Industrial: http://flynorthgroup.com/360/DeepRed-IndustrialREV4/

Why incentive based mesh?

  • Remote/obscure locations connected easily, cheaply, and robustly
  • Economic insensitive to provide network connection allows for a remote location to only need the "last mile" or point-to-point long range connects to get to a IoT device
  • DLT (at present) needs low latency to submit and verify an event on chain within a few blocks - offline recording is not an option.
    • If audited data is time sensitive, then capture time and block time must be within some reasonable allotted time
    • Monitor oil wells, mines, livestock, crops, and more remotely and in real time Key infrastructure for Wyoming
  • Provide or use connections with other mesh devices
    • Sell extra bandwidth to remote people or towns with low population density to make a profit from extra bandwidth.
    • Pay pre-existing nodes to be a relayer - VERY cheap on-going cost. No infrastructure cost
    • Hybrid - install nodes where signal is needed and use preexisting. Seamless integration and easy infrastructure maintenance
  • Proof of location ready
    • Approach like Helium or FOAM projects
  • Fault tolerant
    • Robust against network failures/outages
  • Built in encryption (https://altheamesh.com)
    • All traffic is guaranteed to be private and untampered with. Only way to spoof would be direct physical access to IoT device (and we can guard against this too using a HSM (Hardware Security Module) and HAB (High Assurance Boot))

What it does

A system to securely request, obtain, and store immutable data that is easily and potentially publicly auditable. Built on incentivized mesh networking, this will enable cost effective and robust capture of critical IoT device data.

Smart contract to verify and indelibly lock mission critical data

  • Contract must be issued/owned by a know verified oracle that permissions devices to write to the contract:
    • Permissioner has public identity known with Ethereum Name Service - ens.domains
    • Auditor is the owner / permission source. Those roles can be seporated
    • Store hash of data & metadata in standard format to retrieve.
    • Thus you only need the DLT to store one IPFS hash
    • Public Call to fetch data hash (data stored on the peer storage - NOT stored on chain…?)
  • Public Call to retrieve the oracle’s / IoT device info - (public keys, meta data for keys).
  • Record IoT data on P2P storage and proof of authenticity for audit on a DLT - - ** All IoT devices run light client for DLT and IPFS node**
  • Monitor IoT device realtime & control from base stations - each watches DLT contract for new submissions from device with a full node
    • Pins data from IoT device to local / cloud storage
    • Others peer pins would be those interested in IoT data authenticity - auditors, consumer, etc.

How we built it

Ethereum blockchain, IPFS data storage, Raspberry Pi + Arduino + Sensors for IoT Demo, Ubiquity point-to-point long range wireless connection.

We built a smart contract to lock auditable data hash

  • Contract must be issued/owned by a know verified oracle that permissions devices to write to the contract:
    • Permissioner has public identity known with Ethereum Name Service - ens.domains
    • Auditor is the owner / permission source. Those roles can be seporated
    • Store hash of data & metadata in standard format to retrieve.
    • Thus you only need the DLT to store one IPFS hash
    • Public Call to fetch data hash (data stored on the peer storage - NOT stored on chain…?)
  • Public Call to retrieve the oracle’s / IoT device info - (public keys, meta data for keys).
  • Record IoT data on P2P storage and proof of authenticity for audit on a DLT - - ** All IoT devices run light client for DLT and IPFS node**
  • Monitor IoT device realtime & control from base stations - each watches DLT contract for new submissions from device with a full node
    • Pins data from IoT device to local / cloud storage
    • Others peer pins would be those interested in IoT data authenticity - Eg. auditors:
    • Walmart who bought the cattle that had a photo taken by a drone proving location in Wyo

Challenges we ran into

  • Hardware challenges and
  • 6 people with little experience came together to make a great project - this was not easy - but worth it!
  • getting trapped in rabbit holes and dead ends along the way, and loosing focus as a group at times.

Accomplishments that we're proud of

  • An MVP smart contract (on github)
  • A live web interface to retrieve contract data and view IPFS files (on github)
  • A functional mesh network hardware demo for IoT devices
  • a real use case with real customers interested in our product.

What we learned

Ethereum intricacies and optimal tools to start with. Great team building and agile methods to crush it :)

What's next for WyoMesh

This specific product is one of many that mesh enables. We plan on seeking further interest

Built With

Share this project:
×

Updates