3 ms·

Unless state is replace by message handling https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md https://github.com/EOSIO/Documentation/bl

• AgentME 9y ago
  I've been reading through the paper. It looks fundamentally like Ethereum, but with a runtime environment with specific functionality baked in, and some kind of ongoing voting system for governance of the chain. It doesn't seem to have anything novel in way of privacy: the references to a user's "private database" seems to be using "private" in the sense that only the user can update their own database, not that their database is out of view of other users. This seems to support that: >All state communication among accounts must be passed via messages included in the blockchain. As far as I know, blockchain-based cryptocurrencies so far only seem to be able to achieve privacy through ring signatures or zk-snarks, and that link doesn't feature either. Additionally, it's prominently built around enabling arbitrary computation like Ethereum, and arbitrary communications that have to be executed by every node have to use something like fully-homomorphic encryption to be private from the nodes computing them, which is presently impractically-inefficient for this use-case and not featured in the link.