Privacy of business transactions is what enterprises are demanding from every blockchain project. So far EOSIO has not addressed that yet.
I wrote a design proposal on how the transaction privacy could be achieved. This design is a result of many months of thinking, experimenting, and collaborating with fellow colleagues in our telegram chat.
In short, the design proposes a 3-layer architecture:
The document is only a rough outline of what needs to be built, and there’s a lot of work ahead of us.
There has been a lot of discussion on why enterprises select Ethereum or Hyperledger or Corda when choosing a platform for their applications, and why EOSIO software is not on their list.
A simple answer is, because they are informed this way. Ehtereum Foundation, IBM and R3 are doing a lot to push their technology to the enterprises. A lot needs to be done to spread awareness of EOSIO protocol. Also a lot needs to be done to promote its features.
I published a new design draft outlining a pretty simple idea: X.509 client certificates are broadly in use for digital signatures and identification, and we can utilize them to generate blockchain private keys.
Security implications are yet to be explored, but this design is potentially opening new opportunities in blockchain usage: