Viewing profile — MatthewKernerMS
MatthewKernerMS
HN member- Joined
- Thu, Aug 10, 2017, 7:24 PM UTC
- HN karma
- 19
- Public activity
- 18 items
- HN profile
- View on Hacker News ↗
About MatthewKernerMS
Recent public activity
-
comment
Comment #33187623
The Confidential Consortium Framework ( https://ccf.dev/ ) is an open-source framework for building highly available stateful services that leverage centralized compute for ease of…
- story
- story
-
comment
Comment #21822156
Thanks very much for the product feedback. I've routed the points of feedback to the teams who own the components involved to take a look.
-
comment
Comment #21822142
As above, I've shared these points as well with teams who own these areas. Thanks again!
-
comment
Comment #21822129
Thanks much for providing specific feedback on areas where Azure could do better. This is really helpful and I've followed up with owners for the components you mentioned. None of …
-
comment
Comment #14996348
Coco doesn't use any underlying network - it forms the bottom-most layer of a permissioned blockchain network. When a ledger (could be any ledger, Ethereum as in the demo or otherw…
-
comment
Comment #14996339
There are three layers at work in the confidentiality demo. Coco is at the bottom of the stack. Coco handles replication of data across a network of TEE-enabled nodes, ensuring con…
-
comment
Comment #14991252
The technical whitepaper clarifies some of these points. To summarize, Coco networks are permissioned. Every authorized member can run a node, and all nodes see all data on the led…
-
comment
Comment #14991158
We were talking about this yesterday. We should call them Cokens :)
-
comment
Comment #14991106
Caesar consensus, which is referenced in the Coco technical whitepaper, seeks to address the problem you mention.
-
comment
Comment #14991054
We tried to address several distinct concerns with Coco: scalability, latency, confidentiality and governance. Scalability and latency are determined largely by the consensus model…
-
comment
Comment #14990886
Many use cases we encounter in customer discussions can best be solved by using traditional databases which benefit from academic and industry investment over more than 50 years. D…
-
comment
Comment #14990782
We tried to address several separate concerns with Coco: scalability, latency, confidentiality and governance. TEEs can be helpful in addressing each one. We are working with ledge…
-
comment
Comment #14990715
Coco enables the ledger to mask all data, including metadata precisely to prevent the leakage you ask about. When a ledger integrates with Coco it decides what capabilities to take…
-
comment
Comment #14984623
Richard Gendal Brown has a great post on the difference between a distributed database and a distributed ledger: https://gendal.me/2016/11/08/on-distributed-databases-and-di... The…
-
comment
Comment #14983537
You captured the basic idea of the TEEs well. One way of thinking about this is that proof of work and proof of stake consensus protocols establish trust on a per-block basis. By l…
-
comment
Comment #14983516
I work in Azure, and my team builds the Coco Framework. There is more information on the details in the technical whitepaper here: https://aka.ms/cocopaper Coco is designed for per…