This project seems to hinge on: &quot;Cryptomove  renders futile  any  attack  on  the  data  store even  before the  attack  begins – the  attacker just can  never  find  the  data&quot; and talks about how high-entropy it is.<p>Except, attacks on the actual cipher are doomed to failure anyways unless terribly implemented. So what exactly is it defending from?<p>The whole &quot;continuously encrypts&quot; stuff is also a bit suspect - does that not mean the key must be in memory on those devices all the time?<p>At best I&#x27;d guess this is some sort of traffic analysis prevention system. But if you can read&#x2F;write data on-demand, then it&#x27;s just adding noise. The word &quot;traffic&quot; doesn&#x27;t appear in the concepts PDF so they aren&#x27;t using a common term for it, if that is indeed what they are preventing. Edit: It seems to be much more than that, including a language, an encrypted distributed protocol for the language, storage systems, etc. Which sorta makes me wonder even more what it&#x27;s aimed at: Was it not possible to achieve the goals (what are they?) while re-using existing tech?<p>The site should really, really, spell out clearly exactly what this is really preventing, beyond what e.g. a cloud-sync&#x27;d TrueCrypt volume provides. Otherwise it looks a lot like a fishy product. (Not saying it is; not trying to be negative. Just that there&#x27;s zero clear info on what attacks this prevents.)<p>But there&#x27;s a ton of work done here, all detailed documented (if light on the purpose&#x2F;overview). That&#x27;s very well done as a lot of projects skimp on that part.<p>Edit: It links to Hello language. Which has a pretty SF-startupy-looking page. But very little info. I&#x27;d expect at least a prominent link to some example code, showing how Hello does stuff better. Or why, if the goal is distributed systems, a new language is needed, instead of libraries. (Or how it constrasts with Erlang.) Is it safe? I see one mention of pointers, saying no pointer arithmetic is allowed. How does that mesh with seamless C++ interop? (Is it even possible to have seamless C++ interop and still be memory safe?)