7. Architecture of successful POC of eKYC on Azure using Corda
• Root Network CA
• Doorman CA
• Node CAs
• Legal Identity CAs
Upcoming
8. Secure Networking: #1 VNET Peering
•High performance
•Minimal configuration
•Caveat: Requires subscriptions to
be associated with the same
Azure AD tenant
16. Traditional blockchain, each node with a copy of the whole blockchain
F x 16
Bank 1
F x 16
Bank 2
F x 16
Bank 3
F x 16
Bank 4
F x 16
Bank 5
F x 16
Bank 6
F x 16
Bank 7
F x 16
Bank 8
F x 16
Corp
Cust 1
F x 16
Corp
Cust 2
Quiz: does it make
sense for Enterprise
blockchain?
17. Corda storage and Azure cloud advantage
F x 11
Bank 1
F x 12
Bank 2 Bank 3 Bank 4 Bank 5 Bank 6 Bank 7 Bank 8
F x 10
Corp
Cust 1
Corp
Cust 2
CapEx based planning:
1. Probability of customer facts intersecting with
X number of banks?
2. Past frequencies?
3. For maximum replication, considering 20 KB
per customer, at 100 million customers across
8 banks + 2 customer nodes, storage
requirement is at 20 terabytes overall.
Cloud elasticity is more efficient, easier and faster
to action (also cheaper while ramping up)!
18. What is the best way to extend eKYC to retail customers?
Cool for Corporate customers,
what about retail?
20. Bigger Picture: Decentralized Identity
• Microsoft is actively collaborating with members of the Decentralized Identity Foundation (DIF), the W3C
Credentials Community Group, and the wider identity community.
• We’re working with these groups to identify and develop critical standards.
• We’re developing an open source DID implementation that runs atop existing public chains as a public
Layer 2 network designed for world-scale use.
• The purpose of this implementation is to establish a unified, interoperable ecosystem that developers and
businesses can rely on to build a new wave of products, applications, and services that put users in
control.