Iota is intended to be deployed on IoT devices which have low resources: low CPU power, low storage, low bandwidth, and low energy.

How is it intended that the software is updated on nodes, given that the IRI is now 78.4MB and has been updated more than 12 times in the last year?

Take for example, automotive Telematics Control Units (TCUs). These will have 128MByte of flash and have a bandwidth budget of less than 50MByte/year. These will be challenged by such large updates.

  • Why would you assume the small IoT devices all run IRI?
    – Helmar
    Jul 15, 2018 at 19:46
  • I haven't assumed that. I've described a typical IoT device such as a gateway. Jul 15, 2018 at 19:59
  • Gateways are usually mains-powered and not restricted in any of the ways you describe.
    – Helmar
    Jul 15, 2018 at 20:03
  • Just because they are mains powered, doesn't mean they aren't power, storage, bandwidth and energy constrained. Jul 15, 2018 at 21:00
  • 1
    The IOTA protocol is really just a transaction format. IRI is the suggested logic for choosing two transactions to approve, which gets updated from time to time (and maybe forever will) in a way that helps to improve the network. If a node fails to update this logic, they may be running a sub-optimal implementation, but no one else in the network would ever know. A node can choose two transactions to approve in any way that they like, and the recommended way has a random outcome anyway.
    – user482
    Jul 25, 2018 at 18:56


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.