Quote from: Luckybit on May 25, 2016, 05:47:12 PM

Quote from: lfloorwalker on May 25, 2016, 02:02:35 AM

Quote from: Alao on May 25, 2016, 01:13:04 AM

Quote from: lfloorwalker on May 25, 2016, 12:52:58 AM

Quote from: Alao on May 25, 2016, 12:50:23 AM

Quote from: lfloorwalker on May 25, 2016, 12:18:59 AM

Hi everyone,
I just connected a kWh data-logger from a solar panel, battery to an ARM wallet node.
Some more stuff to do but this is exciting. Been working on this for over 1.5 yrs.
Best,
-lfloorwalker

It's awesome to this unfolding. When will the final results from the experiment be released? There are some big names in this project!!!!

That is after the presentation next week.
We are still early days in testing/prototyping. To get to minimum viable product (MVP), that takes to end of the year because all of the security features/attack vectors need to be studied. That is one purpose of the chain-of-things event with a lot of security experts attending. But definitely a positive step forward.

Best,
-lfloorwalker

I'm not an expert on these things but I was thinking about the security aspect of it. If one person was to chage the input of the data-logger the other nodes would need to be able to detect fraud. The only way I see that happening would be some type of proof of code algorithm where the code exist on the blockchain and the nodes would verify transactions by also verifying that the node sending the data has the same code as at least 50% of the other nodes. Just a thought....

It's a good thought, we are working on this Due-diligence (DD) verification algo right now. It will be a trusted nodes job possibly.
We need to define the SWOT around that.

Best,
-lfloorwalker

Maybe I can give some suggestions.
Be very careful in the selection of hardware. Be mindful and wise in the programming language you choose. If you have the resources go with a correct-by-construction approach to your software development or smart contracts (which is similar to the approach taken by NASA). If your software portion is verified then you know with 100% certainty that it is mathematically correct as a proof, and when you implement it take the most correct approach. Langsec formal proof will result in perfect bug free code.

If you go with C then use well known highly trusted standard libraries, if you're going with Ethereum then formally verify and test your code if you have the human resources and expertise to accomplish this. Do not rely on human error. Finally if you're dealing with hardware while this is the hardest part to secure it's likely for an MVP or prototype you really only have to get the software really secure. The hardware is something else entirely.

For more:
http://c2.com/cgi/wiki?CorrectByConstruction
https://intelligence.org/2014/03/02/bob-constable/
http://www.nuprl.org/

Thanks Luckybit, will definitely listen to this advice.