MatthewKernerMS

4 ms·

1.
by MatthewKernerMS 4y ago
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 use and performance, while providing decentr
2.
Microsoft Introduces Preview of Azure Managed Confidential Consortium Framework(techcommunity.microsoft.com)
4 points by MatthewKernerMS 4y ago|1 comments
3.
BlackRock and Microsoft Form Strategic Partnership to Host Aladdin on Azure(blackrock.com)
2 points by MatthewKernerMS 6y ago|0 comments
4.
by MatthewKernerMS 7y ago
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.
5.
by MatthewKernerMS 7y ago
As above, I've shared these points as well with teams who own these areas. Thanks again!
6.
by MatthewKernerMS 7y ago
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 these points fall directly into areas that I work on,
7.
by MatthewKernerMS 9y ago
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 otherwise) is integrated on top of it, the ledger decides wh
8.
by MatthewKernerMS 9y ago
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 confidentiality and integrity of the data. The data is only i
9.
by MatthewKernerMS 9y ago
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 ledger. The code running inside of TEE-protected enclaves on
10.
by MatthewKernerMS 9y ago
We were talking about this yesterday. We should call them Cokens :)
11.
by MatthewKernerMS 9y ago
Caesar consensus, which is referenced in the Coco technical whitepaper, seeks to address the problem you mention.
12.
by MatthewKernerMS 9y ago
We tried to address several distinct concerns with Coco: scalability, latency, confidentiality and governance. Scalability and latency are determined largely by the consensus model of the network. Our intent with Coco is to make consensus
13.
by MatthewKernerMS 9y ago
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. Databases offer more mature algorithms, implementations, too
14.
by MatthewKernerMS 9y ago
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 ledger partners who want to use Coco to address some but not al
15.
by MatthewKernerMS 9y ago
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 advantage of - and how much data to expose to the public,
16.
by MatthewKernerMS 9y ago
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 Coco team shares Richard&#x
17.
by MatthewKernerMS 9y ago
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 leveraging TEEs, we have hoisted that trust establishment o
18.
by MatthewKernerMS 9y ago
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 permissioned networks (as opposed to public n