Live data from Hacker News

Viewing profile — MatthewKernerMS

MatthewKernerMS

HN member
Joined
Thu, Aug 10, 2017, 7:24 PM UTC
HN karma
19
Public activity
18 items

About MatthewKernerMS

I work on Microsoft Azure, on the financial services vertical and on the blockchain workload.

Recent public activity

  1. 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…

  2. story
  3. story
  4. 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.

  5. comment
    Comment #21822142

    As above, I've shared these points as well with teams who own these areas. Thanks again!

  6. 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 …

  7. 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…

  8. 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…

  9. 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…

  10. comment
    Comment #14991158

    We were talking about this yesterday. We should call them Cokens :)

  11. comment
    Comment #14991106

    Caesar consensus, which is referenced in the Coco technical whitepaper, seeks to address the problem you mention.

  12. 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…

  13. 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…

  14. 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…

  15. 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…

  16. 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…

  17. 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…

  18. 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…