Hi there. It's not because
Morning.
Group. We're going to wait a few more minutes for folks to show up and then there's a obligatory
Anti trust statement that
I'm going to have to read and then we
can kick off or meeting, so sit tight for a few minutes and looking for us.
Rows. Are you there john
John. Could you hear me. I was just talking we able to hear. Yep.
Yeah, great. You're here.
That you might not be here. I'm here.
I'm here because the ferry that I'm supposed to be on cancelled due to mechanical failure but Stephens gonna take the do the presentation for us. Oh.
I'm sorry about your
Life. I guess I know well
silver lining. I would insert it here.
But I'm not sure what that would be.
Great.
Are lining isn't here. Okay, that's great. We'll just
We'll just listen in. And you guys are in great hands with Stephen. Excellent. Okay, well,
We're looking forward to chiming in. And I'm sure it'll be very
Helpful.
So sorry about your fairy. We're going to wait a couple more minutes until about two past the hour and then I'll read the antitrust slide and then we can hop into everything
But collectors running
You know john does a really good job at reading that
We
Share on
Yeah.
And reading the anti trust side something
Somebody else to read this.
It's something I feel like somebody else could do a better job or if there's any volunteers to be the fly reader, please let me know.
Very good morning this Killian Murphy from our box just log in to this.
Call for the first time was introduced to it by Bobby local New Jersey meet up the other day.
I'm glad you joined us just about getting ready to start
Very good morning. Sure. Thanks very much.
Okay. Hi, everyone.
Who's that. Who's that oh, good morning. This is Danielle Barbosa with hyper ledger Daniela. Great to have you joining
Thank you.
This is rose
The chair of the group. And I was about to kick things off, but
If anybody wants to say anything before I kick things off actually not really supposed to talk it until I kick things off with this and to trust sites, how would I just jumped into it.
Other than again, opening the call that if anybody else would like to be the reader of the empty trust slider the future. This is an open position.
Okay anti trust policy. Notice Linux Foundation meetings involve participation by industry competitors and it is the intention of the Linux Foundation to conduct all of its activities in accordance with
Clickable anti trust the competition laws. It is therefore
Extremely important that
Attendees adhere to.
meeting agendas and
Any activities that are
prohibited under applicable US state, federal or foreign interest and competition loss.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation anti trust policy.
Available at www Linux Foundation org slash anti trust dash policy. If you have questions about these matters, please contact your company council or
If you are a member of the Linux Foundation and feel free to contact Andrew up the groove of the firm. Guess we're up to growth LLP which provides legal counsel to the Linux Foundation and with that exciting opening
We are now ray and able to formally kick
off our meeting. So hello everybody and excited to see all of you here, looks like we have a great crop of participants today.
I've sent around an agenda as a suggestion of how we can run the call today. But first,
Yeah, quickly tell you what the
Top highlights of the agenda and then
Think
Great. If everyone could quickly go around and introduce
Themselves just doing a piece here, the way we're looking at running the meeting today, which runs an hour is first to have an open chat.
Following up on Kumar's question at the end of the day, last call.
Which was when doing a proof of concept. How do you handle getting information from existing systems, as well as the mechanics of actually replacing that system.
So how do we how do we do succession between very different systems moving things over to a hyper ledger based system. So I think there will be quite an interesting open discussion.
After that we're going to have a great presentation from Bobby was scarf. Let your Academy, who's going to give a high level overview of the different hyper ledger frameworks out there.
After that will go into john and actually now it's going to be Steve who's going to tell us a bit about how hyper ledger in the actually work. So one of the things
We determined was that many people in the group would really appreciate an in depth primer on the various frameworks and tools of hyper ledger. So we're going to aim to have
One of these every color almost every call until we work them through so everyone's better informed by the end of the year. We've updates on the hyper ledger global forum and then opening the floor to other topics. And again, encouraging anyone who's got questions your
Use of support.
I would like to
Care a project.
They're thinking about are working on that this would be a great time to make that known so that we can schedule that in and 10s of attention to it. So without further ado, the folks who would like to introduce themselves could please do so. Go ahead.
Welcome
I'm Mark is from flies.
Self blockchain consultants and development.
Bobby ledger Academy
From the Federal Reserve Bank of Boston
Scott Snyder with inflammation builders.
Hi everyone.
Good morning. This is Karen Murphy from our blocks were blocked in consulting company and an oracle partner or interest is understanding what's going on in the hyper ledger fabric. This is my first call thanks to Bobby. We met at a meet up a day or two ago and she
Brought up this meetup that happens on the federal space. So there's a first call excited and thanks for joining.
Good morning everyone. Pete Teigen with IBM
Okay. Good morning, everyone. This is Roman Anderson. I'm with solid armor and I'm also the organizer of NJ that walk chain, which is based out of mostly newer we do
Programs. Thank you.
This is reindeer vivo. I'm an attorney in Illinois. I worked for the state of Illinois in a number of different
Areas, mostly in Medicaid and then I've also represented municipalities in private practice. So I'm just interested to learn more about how block chain can fit in with government
Hi, this is our introduced myself because others joined in business. Daniela Barbosa with hyper ledger. I'm part of the staff here at
Anyone else like to introduce themselves.
I'm gonna be talking a bunch later but I'm Steve current work with john Jordan that big government, British Columbia.
Great to have you see if in thanks
For taking the reins on that. Anyone else want to jump in and say who you are. You don't have to, but this is the best time to do so
Okay, well, then we're going to presume everyone who's wanted to introduce himself has and a warm welcome to everyone who's both introduced to not introduce themselves. Looks like we're gonna have a great group of people and a good discussion.
Before we get into the agenda.
If anybody would like to propose any changes to the agenda or additions.
This would be a good moment to chime in. Now, otherwise we'll just go is programmed and have that open space at the end of the call to go over miscellaneous issues. So if there's anything you'd like to see changed her add or suggest this would be a good moment.
Okay, great. So let's, let's jump into Kumar's question which was
Just an open discussion format on when doing a proof of concept. How do you handle getting information from existing systems, as well as the mechanics of actually replacing that system. So it's really looking at two phases here.
It seems that I think for many people, they see their limited or only theoretical experience about
How this transition might take place. And I think hunger and interest in hearing anyone's experience on how they handled that process from either a technical our operational or even
Human Interaction type of perspective. So if. Has anybody here had any experience doing this and perhaps what's maybe one or two key learnings that they had over the course of it that they didn't know what the outset.
So this is Canada. I can tell you what we've been trying and we're getting closer to connecting it to
Call it the mainstream network here for the time being. We've got a hit several religious fabric.
Concepts running but most of them are either Erica air gapped or tightly locked down at this point. And we're pushing towards getting
Getting the the platform mainstream tearing the environment and we're getting closer. And then once we get to that point, we have an internal platform as a service offering that will be able to to really start to look at it, but for the time being, we've been struggling a little bit here.
Was getting the technology and all of silicon see other things we've had great success with air gap. But as far as mainstreaming, it hasn't hasn't taken hold yet. So it's just kind of a little journey description about where we are.
Thanks for sharing that Ken. Does anybody have any questions for him about their experience or want more detail on his context.
I would like more detail in the context, actually. And how did, how can did this project actually get initiated. What was the driver.
So we've got we've got a working for the
Federal Reserve System. We've got a vested interest in
What does
What does blockchain technologies mean or
The financial services sector. So we really need to understand it, and with respect to, you know, bank, the bank.
Transaction and one of the capabilities. The other one of the other things that we're looking at is our one of our roles his advisor to our member base.
So we can go out and is buys as to what
The individual banks.
Should be looking at and policies and things like that. So not necessary regulator because necessarily working later. But how can we advise our member banks to do
So it's, you know, there's a woman. And there's a lot more as well and why we're interested in and blockchain technology and we've had some good success.
Getting a much, much better understanding. We also are. Are you active in our community was posted a meet up here as well.
That insurance and things were developing a White Paper, which will let you know when it's available with our journey. That's got much more details that we've been doing
Fantastic.
I really encourage others.
Can some questions, but
While there while you all are thinking about it and when do you think this White Paper might be
Ready.
Because it was
Or where we've gone through the process. Right now we're
Up on the executive level running feedback have been so we're hoping, hoping in the October timeframe, October, November.
That's great. I hope that you'd be willing to present it to the group here. If it wouldn't be too much of a burden on you. So I'm sure it will be very interesting and fascinating.
To learn about that experience. Yeah.
Yeah.
Great.
This is a fantastic
Example is
There. Anybody else who would like
to chime in with their own experience.
Again, it doesn't have to be a
perfectly formed are very advanced experience with anything at any part of the process, even if its preliminary about what you've encountered when doing a proof of concept.
In terms of getting information from existing systems or actually doing replacement. Is there anything that you've encountered that
Might be valuable learning for others, or have surprised you. This is an open question to everyone.
Rose. This is Pete Teigen, and
I think challenging the premise of that question altogether the replacement of legacy systems is something worth talking about are considering
You know, our perspective, of course, depending on the scenario or the situation we don't necessarily look at it as a replacement of a legacy system as much as a supplement to
So really, you know, when you're building a block chain on top of an existing process trying to improve a process.
You know, we start with just doing API calls to whatever that underlying legacy system, the data store of each of the network members.
And pulling that up into the block chain network. So I wouldn't look at it as much as a replacement of a legacy system as much as a supplement to
That's a very interesting comment and learning P. But anybody else like to ask Peter bit about
This position or their experience or contrast it with their own experience or corroborate
This is this is Kiran Lucy from or a block. Not sure if it's going to be strictly hyper ledger, but I'll, I'll tell you some experience from what we've been
Working on for the past few months, thanks to thanks to the team at hyper ledger.
Marta.
Knows about it. There was an FYI, that was sent are put out back in the day for
For record management and
They were there's an exercise that was put together where we joined the party as well and said, How do we respond to an hour for showcasing boxing as
An me as an enabling technology for interagency collaboration, so that that's that's an exercise we have done with hyper ledger on top of it. We feel it. Other conversation in the federal space.
Predominantly around collaboration from interagency systems. So the technicality of it boils down to this. Right. So there's two aspects of communicating with the with with the consortium inside out outside in inside out.
We think triggers is the way to go, are rather event as people see it. There's, there's also, there's an intermediate
intermediate layer that we can introduce via a concept of Oracle's and Oracle's as an articles in the blockchain ecosystem, but from outside in people talking about pushing data from legacy systems on to the chain itself.
I think I would concur with what Peter was talking about. I mean, it is your fabric itself and we being an oracle partner, they are exposed API rest endpoints and JSON is is the standard payload that had been very
Enabling for us. So if you're sitting in Enterprise Architecture ecosystem. There's a micro service that you have exposed internally, that is that is authenticated accurate and certified to transact and
There's that layer put together. I think
Now, pushing data into the onto the ledger itself from sitting inside a legacy system is not a big deal, Doc. But again, this is not going to be a snapshot where you you take a you take a million rows in the traditional systems and transfer system to system using using a tool or or or
Or an et al, or so on and so forth. So
Getting data from legacy system seamlessly in onto other ledger. I think the practicality of it. It's pretty pretty seamless the scalability side of it is something that we can all say that we got we got
My list.
So that's, I mean, and we've done. We've done at least three four conversations wise but more more more predominantly
It's, it's possible. It's, it's not going to be as scalable as you would want to at this point. But I think that design pattern is well a lot collated
Again, I'm strictly speaking, since this is a hyper ledger conversation about hyper ledger side of things and on the Oracle side of it that your partner.
And there's a REST API that makes it a little bit easier, but that's about it. So,
The sales to certain extent.
Thanks. Karen ups and hearing somebody backward. First thing so much Karen for this very practical inputs on your experience.
Going to open it up to one more comment but then being mindful of time we're going to move to the rest of our agenda and perhaps pick this conversation up again. It looks like it's getting a lot of activity, but I feel like is there somebody else who's trying to chime in. Now,
Hoops cliquish talking I, you, you're very, very quiet.
Very, very quiet.
I think it sounds like somebody's having a side conversation.
Okay, I'm like this is OK. I think you're probably right, Pete. Thank you. Okay, so this is, this has been a really excellent conversation.
I think we're ready to move on to Bobby, who has an excellent presentation to give people an overview of frameworks. So without further ado, Bobby, you ready to take it away.
Hi everybody, I'm just going to share my screen give you a little preface as to what this is.
This is a powerpoint presentation that goes over the frameworks and the tools under the hyper ledger products.
We're going to go over the frameworks today and I'm going to briefly just touch on them.
But this presentation is also going to service. Something I hope that will be stored on our Wiki as a resource for the people in the group if they ever have to give the presentation.
So I've added notes at the bottom with little you know dates and stuff that you might want to add if you're giving the presentation. But basically, let's see if I can share my screen.
Sure, which screen you're seeing
So again, this is the agenda, we're going to go over the
Presentation goes over the Linux Foundation and hyper ledger and then the frameworks and then next week we're going to touch a little bit on the tools.
And eventually also stored in here will be brief overview of use cases that we've gone over. So again, you can resource them when you resource this presentation.
So again, the Linux Foundation just goes over the nonprofit and then there's a link there to the projects. These are some of the projects that the Linux Foundation hosts on a broad sense, but this presentation, obviously, is about the hyper ledger project.
Yes.
All right, this is Rose, we see both hyper ledger. But then we see your next animal
Seeing another
Still Small we seem
To
Have ever that
Big. Thank you. Great.
Okay, sorry about that. OK. So again, hyper ledger is the fastest growing project and Linux history. I'll go over this quickly because this is just information for the presentation.
It talks a little bit about how it's the shared truth gets trust in their open source and it's a global collaboration again here we go for the actual hyper ledger frameworks. There's borough fabric indeed Rojas and sawtooth
Again, if it's yellow there an incubation. If it's green. They're actually moved out of incubation an active projects. So these go over a little bit about what each one is identified as and then again we go into the tools which we'll go over next week, so I'll do that very quickly.
Again, this is hyper ledger fabric.
It's a high performance permission block chain foundation developing applications and solutions in a modular framework approach.
On its features or plug and play components for consensus mechanisms and membership services.
It has a smart contract piece which is called chain codes and it's the logic component of the system. These chain codes can running side secure Docker containers so it leverages that Docker technology.
So it can host any mainstream language for the smart contract development. And then there's a list of a little bit of what each one of the segments of the product is written in
Again, some channels. Those are the features that lets different participants involved only see the transactions that are relevant to their individual
Transaction the channels are private Southern networks of communication between two or more network participants peers or nodes for private transactions.
There are roles each node that gets clearly defined it, the setup of the fabric application and they're committing peers endorsing peers and ordering peers.
And again, if you want more information on fabric I settled link at the bottom for the most current documentation coming out of the training and education worker.
Moving on, we're going to go to sawtooth
And sawtooth is a blockchain designed for versatility and scalability. So, it supports both permission and permission list deployments and doing so, it recognizes diversified blockchain requirements.
It includes a new consensus algorithm called proof of the last time or poet and its aim is to achieve distributed consensus as efficiently as possible.
So it targets, again, a large distributed validator population, but they try to use minimum resource consumption in their consensus.
It does this by using the Secure Enclave that is built into the Intel chip for a random wait timer so each of the validators get on the network and the validator from timer expires first generates the block. So it doesn't use that electricity like another block chains.
With the to burrow attached
can support this application for writing on the virtual on the IBM and the smart contracts can go on. Right on the virtual machine.
Again, the key characteristics on the pluggable census algorithms, the new consensus proof of elapsed time, the ability to write smart contracts and almost any language.
It supports borough and the integration of integration of the Imperium machine. It's a great example for supply chain, out of the box solutions.
And it has parallel transaction execution for additional throughput. And again, I get a link I left a link for the current sawtooth documentation. Moving on, we're going to go to burn
And burn boro is a modular block chain that was built again to work with the VM. It's licensed it uses a Byzantine fault tolerant permission ledger and tender moment consensus which is again working with the
It provides and a cap model and an internal token to meter, the consumption in the permission settings for transaction finale. So those things are in there forever. And again, tender moment is the consensus mechanism.
It's goal is to be compliant and friendly towards integrator such trying to do a little interoperability on it's going to be fast light and lean
And it's provide you know again a practical base for extensions for a multi chain world. It is not trying to be like sawtooth or fabric highly pluggable or hard to deploy.
Again, the documentation can be found at that link.
And then the last one that I'm really going to go over is a Rojas
And again, it's distributed for mobile application and mobile development and it's written in C plus plus its aim is to get reusable components so that users can perform common functions.
And as creating transferring digital assets. So it uses pre built commands that are earning in the system. So no need to write your own code and test your smart contracts, it's already been done. So it's faster and less risky.
It's, you know, added two different projects that are already fostering robust libraries. So it's basically a libraries.
Plugin play so you can get some of the hyper ledger technology into different projects, it supports javascript libraries and it's working for both Android and IOS operating systems design kids.
Here again, or some key characteristics simple deployment libraries role based access control modular design.
And assets and identity management. It uses a new consensus algorithm called Suma Ravi. It's permission network. It's written in c++ and Java.
Chain code and their special libraries and again the documentation for a row hot can be found at that blank.
And finally, very quickly. The last one is indie and all I'm going to say about it is that it
Provides digital identity rooted on the block chains of individuals can own their own information and only share pieces of it.
So we're going to go over indie in a presentation next. So thank you very much for listening to me. And again, I will get with Kumar to get this up on our Wiki library so that you can access this. Thank you for letting me discuss this with you.
Thanks so much, Bobby, this is awesome and
Really helpful consolidated overview and thanks to both you in of course Kumar for getting the wiki in really great shape so everyone can peruse this on their own time and really absorb all these
Characteristics, as well as resources, but this is fantastic. And we're looking forward to your next presentation on our next call which will go into the tools, but thanks so much. Bobby, this is great.
No problem.
Awesome. Okay.
So after this really very useful overview. We're going to go a bit more into hyper ledger in D. So, I believe, Steve, you're going to go into that also just before you start. Steve, do you have a sense of your target time length for this just so
We can
I can direct traffic properly.
Yeah, I was just thinking that same thing I was thinking like, excuse me 15 minutes maybe
Too much
No, no, that's actually perfect 15 years
So,
Let's aim for that.
And take it away. Then
Alright, I'm going to share my screen. Thanks to of course have to have a
Proto presentation.
Because it's much easier to talk to. So, and this is a Google. Google Spreadsheet or Google Slides. So you can take a look at it and people can
Look at it after there's some links in it and so on. So, Introduction to hyper ledger indie so we've been using Hyper ledger in the DC gov for about a year, year and a bit now today could be Last day we go live in the next few days with our first production application.
So, and I didn't john talked about that john Jordan talked about that in the last week or something like that on this call me previously so little bit about what I'm going to talk to
So I wanted to start with, you know, sort of grounding. The problem of what is
The identity problem. So I'll just summarize a little bit from that I think everyone's aware of it. I'll just focus on on on what in the attempt to deal with in that it really is about trust. It's about who it is we're talking about when we're online, the famous New Yorker.
Cartoon captures it. Well, you don't know who you're talking to. And as well. Can you trust what they tell us and and that
The fact that people can type in and say, you know, what is your social security number and you can type a number and really doesn't give you any ability to reduce the risk
Or doesn't sufficiently reduce the risk that you can actually conducted online transaction based on that information. And it turns out it's a really hard problem. We've been trying to fix. People have been trying to deal with this for 30 years on the internet and
We're still not all the way there and and we think indie can take it an awful long way to actually fixing the problem.
So,
The information that's the basis of that lots of identifier so user IDS and passwords are everywhere. You've got your government ID that they issue your
Emails
Organization gives you an address or your organization gives you an email address all of those are substitutes for who we are when we're talking online.
But as well. Not only do we want to know that ID and be able to prove that you know you're the person behind the ID. There's all sorts of attributes about us that we need to know to to be able to do online things
You know, you know, know your customer and things like that for just the ability to present that you represent a company, for example, we're focused on company space and who are who are you, or do you have permission from the organization that you represent to actually conduct a transaction.
On paper, it works fairly well there's there's known patterns, basically a holder has some sort of piece of paper. Some passport or driver's license, a
Permit and they use them to show somebody and they look at that and they say yeah that's that's real. So that proves you have that that was already to act.
Online as
Somebody told me yesterday, just to transactions work advertising, which uses us as the as the product and shoes.
Which is because we physically ship it somewhere we can trust that you know they're going to give us a good credit card and and and we can trace them down if if they don't. Other than that, we haven't really accomplished a lot online of
Beyond advertising and selling
I'll skip by the encryption. But basically, we've got some encryption that allows us to have conversations have, you know, web sessions that are encrypted. So we can face we transmit. For example, credit card numbers and things like that. But it's actually one sided
I'll skip by that for now.
ramifications. These are things you'll all recognize passwords. I have over 700 passwords in my last pass account.
We try to fix that by having identity providers provide our identity. So we have login through Google and login to face book and then they share a little bit about you with whoever whoever site, you're logging into, but it really is silos and not in our control.
Correlation is a huge issue. If anyone if you haven't read about this exact this data breach worth looking up, there's a link here. They had a big data breach was a big problem.
340 million identities, I found the more fascinating thing about that data breach was they had basically 400 data attributes about every person that they were selling to
Anyone that would buy it. That basically had things like you know your name, your email address typical things like that but they'd also through correlating your data with all sorts of website had, you know, religion, where you live, how many kids you had race, you know, all of that information.
They had just collected through back basically backdoor approach is to aggregating your, your profile and then providing it to others, so they can target your advertising target their advertising.
So identity fast.
And then attributes.
attributes are so susceptible to faff social security number, you know, your passwords and things like that.
But as well even offline in person proofs are becoming problematic and more and more people are looking at the in person proofs and saying, you know, those are forged documents. Those are becoming harder to make sure
When I go to bank, for instance, they asked him, prove my address by giving them a utility bill that would take me at least 12 seconds in Photoshop to to create a substitute
Probably wouldn't even need to use Photoshop, I could use Powerpoint.
So hyper ledger, Andy. How does it deal with it. So that's, that's the introduction to it.
First, it starts with decentralized identity. So instead of a central authority, giving you an identifier.
You create your own identifier and you provide and and there are mechanisms hyper ledger India's one to resolve those identifiers. So this thing I've got up here did colon solve
And a number that's what did looks like a decentralized identifier. So they're obviously random they're ugly, not easy to deal with.
Next that identify or has associated data with it, public keys and you control the private key associated with a did that you create.
And a service endpoint away that someone who has that did and has that did document the associated data. So with the dead can find you and connect with you.
Those did our exchange between identities even consumers in business, so they become peers. So, so when you exchange it did you create one and your peer creates one you both exchange. Now you both have a public key to talk to one another.
So that's that gives some pretty powerful capability.
And we'll talk about those. But each identify has a different did for each of relationships. So it gets rid of this correlation capability so
When I set up a relationship with my bank I created did when I set up a relationship with my spouse for online discussions I set up a dead and they're all different. And they all look kind of ugly and the same. So basically, that means that
Each organization that I that I connect with can't use that piece of data and exchange it with another company and then correlate that data between an
End to end encrypted messaging and by this that it does include I ams and notifications.
And it could include email, but it also includes other types of transactions, when we think that's the dream, but basically what this says is if I have a dead. I can resolve that did that gives me a public key.
That you that that person owns and an endpoint and so that I can send a message encrypted and the only person that can decrypt it is the owner of that. And that's pretty powerful.
Again email addresses are the number one.
Method of correlation you you have to register your email address so they can contact you. But that's, of course, your number one connection across all these services. That's the correlation factor.
So decentralized identifiers that the cornerstone, number one, decentralized gives you a key that there's a blockchain in bowl so
Some days, and we'll talk about that in a band are published on the blockchain. So because they're published on the blockchain. Basically you create a dead.
That gives you that identifier. You create the public key associated with it. You have an endpoint, somehow, and we'll talk a bit about that.
And then you publish that to a block chain and now it's on this immutable place that you've published and when people get that did
That magical identifier that you've created. They can resolve it by looking it up on the on the block chain and they can connect with you. And so indie has a blockchain.
Implementation. It's called any node in in the public ledger part and it creates a decentralized key management system. So basically, for those who know excuse me anything about PK
That's a centralized one
Distributed means that decentralized. One is, is just a safe way of distributing public keys that can be reused.
And there's actually not supposed to be a question mark around
Actually, no. This is the question mark is that there are they tried various methods over the past to create it became mass and what enabled by hyper ledger indie and a couple of other
Open source.
Identity systems really create that first method.
For those familiar with fabric and a couple of others. Those are private permission block chains indie is designed to be a public
Public blockchain. So it's available in the public in the public space, but it's permission only certain people can write to it. And we'll talk a bit about how that gets control. But basically,
Unlike bitcoin in the theory. I'm you cannot just start up a node and right to the block chain or create blocks on the blockchain. You have to be permission to do that. That allows for a very efficient.
Block creation and consensus algorithms and things like that. So it's a it uses pretty fast capabilities for writing
The third Cornerstone agents and wallet. So I'll go over this quickly, but basically to manage did and things like that, obviously you need a bunch of software.
The dads are big and ugly and you need and you have, you know, thousands of them as a consumer, you would have thousands of them.
So you need software running on a on a phone. Often, you need a wallet, which is where your keys and other data gets stored and I keep referencing other data, you'll see that in a bit.
But that's secure data that's got to be locked down and helps purely and that is one of the challenges of getting this out is making sure that we come back with both
secure way of implementing a mobile app, for example, or a or a desktop app, but that combined usability with the security you need of having a wallet that contains keys that you need to control
Basically this is sort of the picture of the generic world you have an edge agent, which is something like a phone you talk to a cloud agent, it talks to the did layer of
The blockchain piece and that allows you to talk to other identity owners could be enterprises, in this case, and people on the other side could be whoever you want to talk to
The K is the core of agent and there's a whole raft of people, including us working hard at coming up with the protocols that allow agents arbitrarily created agents to talk to one another. So that's a big area of of progress right now in the indie world.
Now the last piece is really the magic that really lets it this technology is really important to the technology and that's verifiable credential so verifiable credentials and you'll sometimes see as a term verifiable claims is Wi Fi standards.
Based on a working group.
That is allows for the exchange of of those same sort of paper documents that you've got in.
In the paper world but done in a digital form so data about you is issued by somebody they give you the credential that you hold and then every once in a while, you need to show that to somebody to prove something. And so you
Hand that to another verify or to show that you indeed have that information.
Underlying all that is this is the blockchain is indie and the identity registry. So the model is the same as you're familiar with, with walking into a bank and showing them a piece of paper that proves something about you.
But in this case, we're doing a digitally, and we're doing in the same way, though the issuer provides it to you as the holder and when you want to as the holder. You give it to a verified.
So what does it mean to say proven, I said that in this picture that I can hand this to verify and it proved certain things. So what are those proves
What does that prove
So this is where the magic cryptography comes in, so I won't say a whole lot about that, but there is it. This is all
Handled by the cryptography underneath and the and the keys associated with with the bids and things like that. They're going forward. So what I can prove his who issued the claim. So if I have a claim that it's a driver's license.
claims that are from a credential driver's license, the issue, or is the government entity that issues driver's license. I can prove that they that that was the issue.
And I don't have to ask the issue or that that that very key crucial part I'm not actually asking the issue or to prove that just the holder proving this and giving it to the verifiers proves that
The claims were issued to you. So because of some data embedded within the credential, you can actually prove that the issue or issued the claim to you and your now proving that you are in control of the
proof of ownership of that data associated with the clients.
You can prove the clients have not been tampered with. That's fairly easy in cryptography world. There's a signature on it and of course if you change any of the data that's going to break the signature.
And finally, this is the addition that you really can't do with paper at all, which is you can actually do real time proof of non revocation. So you can prove that the credential that was issued by the issue or has not subsequently been revoked.
So again, pretty powerful stuff.
The last thing that is the caveat is exercise for the verifiers who issued it. Note that I said that you know who the did have the issue or
So you can use the blockchain to trace back who that verify or is but you still want to decide, do I trust them. And so this comes back to, for example,
Your transcripts, you can have
Transcripts that that are issued to you and that show that you are you you know you have a degree, but do you trust to that issue or wise, you know, the WHO, the issue, or is of that of those transcripts, is that Harvard University, or is it
To bit university that sells them on the Internet sales transcripts are in sales degrees on the internet. So it is an exercise to verify or to figure out who issued that credential and whether you trust them.
But it does take that to a different level. So instead of saying, Do I trust.
The person who's giving me that did they force that or whatever you actually no, they did not fortunate. They couldn't afford it. It was issued to them. There's no question of that.
The question is who do you trust that person that that issue. And that's where a lot of these credentials will come from.
From people you trust. There's a couple of magic pieces that India ads that are pretty cool, which is
Selective disclosure and zero knowledge proof. So the two things. Those are our when you get a credential. You don't have to present the entire credential. You can just present the correct the information that's relevant to the transaction, you're trying to do.
So you can block off these things and you can add a bar just say this was issued by BC. This is my picture and I'm overnight and zero knowledge proof is that last bit overnight so without exposing my date of birth, I can prove that I'm older than a certain age.
These are the ramifications and probably, I think this is where I wrap up, but
You hold your data and you share it as necessary by approved so you don't have others holding it for you and sharing it on your behalf. You actually hold the data and you distribute it when you want to
Security become harder to force the paper credentials over time as this gets accepted.
Simple data strings of data become useless.
You can have a forum today that says enter your SF and and you have no idea whether the person that they're as or just a number that they bought off the dark web, as they call it, that is your SSN if you have to prove you have an SSL issued by the US government
That's a different question.
All sorts of online transactions because becomes possible because you have you're able to prove things necessary to conduct that online.
Last thing always want to talk about on Indie. It is a public blockchain. There is no private data on the blockchain. So there is the did there's some data around
The verifiable credential that enables us to share and do cryptography on the credential that you've been given, but there is absolutely no private data. The
Credentials themselves are not. They are given to you and stored in your wallet. They are not put on the blockchain. So that's incredibly important.
This is a detail that are probably don't need to to discuss. And then the last thing to talk about is
The sovereign foundation is very tied to indeed because the sovereign Foundation is a nonprofit that
Is going to is is operating a global deployment of hyper ledger indie. So these are, this is the foundation that drives an actual the actual implementation that will probably be used. So it's a BLT a business and legal and technical framework.
That outlines
How, how it can be used what the role of the note operators are called stewards. So I remember I said that they are permission. So stewards are the people that are permission to create blocks and reach consensus on blocks.
There's about 40 of those in all sorts of industries and across the world right now and that will grow significantly over time. So sovereign foundation operate and an instance of hyper ledger indie across the globe.
And provide the structure for
infusing trust into this permission to block chain.
And we always have Mary who's tried to do run a bakery and so she can do best, because we've taken care of her identity and fix the internet for her.
And that's that. And I probably talked a lot longer than 15 minutes, I'm sorry.
That's okay. Steve this is Rose. This was great.
Okay, doing some traffic direction here. I know that many people are probably going to want to ask you.
Questions.
And also,
show appreciation for this terrific presentation.
It would be great, you could share
The link to
Yep.
Through the email list or the
Chat so that Kumar.
Might be able to put it up.
On the wiki. So thank you, Mr.
Before we get into questions. It would be great if everyone considers their questions and notes them, but we're going to jump.
Forward. So we cover our agenda before and have time to Marta, who is going to give us an update on the global forum and apologies Marta for the compressed time but I'm sure that we'll all be fine over
Thank you, Rose and I'm sorry for the background noise.
So we have submitted at panel proposal.
For the hyper ledger Global Forum. This was a discussion.
About
Privacy and governments. We've had scheduled to have three panelists and rose moderating a panel.
However, due to the fact that we had a lot of submissions that were quite similar. And actually, economists who decided that or submitted their talks to
Hyper ledger global forum so that agreed to be on the panel also submitted their own helps to hyper ledger global forum and in order to accommodate as many people as possible.
In fact, we, I think we hit something like 7%
Submissions we're only
Accepted
Because of the
Amount of submissions and high quality of them. So we had to be very selective so Utah that we have decided to create a panel that will help on blockchain. So all the people that were scheduled to give a talk we'll have a sloth.
I believe
At the
Global Forum and they have been notified. However, they were notified separately, not, not the officially our panel was rejected, but participants that wanted to give a talk at Global Forum will have a salt. I hope that makes sense.
Thanks Mark to for the overview. Would anybody here like to ask some more questions.
And get clarification.
Yes, this is Karen tram loss. I just have a question.
Great presentation you
The question is in your implementation today that you're talking about going live
The, the entity that is going like, are they running a dedicated node on the solid foundation himself or are they leveraging the public infrastructure that's been run by you said for the other participants.
So when so we're doing a two part live we're publishing. So we're going live on our own instance or the next couple of weeks while we work everything out and then we will go live on the sovereign instance, we don't run a node.
We're considering becoming a steward, the DC gov is but not particularly crucial.
We're comfortable with how sovereign is running it. So we would use their
To operate the node or to operate as the blockchain backing for our launch
Okay, great. Thank you. And the second question is in in your integrated development exercise that you've done internally.
Unlike the public side of things where there's the test net and the men that and all on all kinds of stuff out there.
What kind of infrastructure, have you leverage to see the things that working the way you see, you see them or intend to see them working in on the public side of things.
So it's really easy just to spin up your own network for casting and things like that. So we've spun up. So most development work is done, just with a local instance, but then we've spun up a couple of
More available instances as well that we make available to others to us. And then there's also a sovereign test network. So there's a range of places you can you can run
applications that use different Ledger's ultimately you want to obviously have to be on one ledger to have a production system and and we would use the sovereign, we would always use I think sovereign public network.
Great. Excellent.
That's exactly what I was hoping to hear. Thank you very much. So
Does the governing entity itself from from NBC perspective. Do they have an intention, because now that they're putting their entire
And demographics to be identified on on the dead side of things on on sovereign side are they taking any measures to make sure
The sustainability of the sovereign network itself. I know you said, eventually, you might cut your own blogs, run your own node. But at this point, you're leveraging the public side of things, but
Having investment made at that
Integral level and does the does the governing authority or the governing the government itself see a need for running their own infrastructure to support the larger network.
At this point, you know, as I say, there are a number of entities in Canada, as well as globally that are running node. So we're feeling good about that.
There's also a couple of other networks that are building up with the same sort of idea. So as as a government. We just want to enable what we find that meets the privacy standards.
And the identity standards to the government. So there's privacy by design. And there's an organization that that has an identity trust framework in Canada, and as long as as as those entities meet that
In and of course we'll look at sustainability and so on sovereign looks. Looks good to us now, but it's early days. So it's exciting times to figure that out. Excellent.
Thank you very much.
Hey everyone this is Rose here interjecting that we're getting some really great momentum around Q AMP. A noting the time that we're at the hour.
Those who would like to stay on and continue to talk. We can do that. But let's do just a little bit of preparation for our next call so that we have something equally interesting and engaging would
Anybody be interested or or in a position to give an overview of another tool or framework for hyper ledger for two weeks time from now.
While you're thinking about that. Would anybody like to share some thoughts, they're having about a project, they're working on are considering or problem, they'd like to work through or pose a question to the group that we can discuss
All right, yes.
I see.
Marvin. Are you trying to say.
Comment
I am. My question is more about distributed storage as it relates to this.
ID.
Is there any thought to do a distributed storage that block chain in case
Like one or two blocks got attacked or something. Are you going to all have it sitting on their infrastructure or container. I think of that nature.
Okay.
I think that would be a question just to give a sense of
How it might run
Sentence in the chat.
That is part of our agenda for today.
As organizing discussion.
Yes, yes, I can do that. I cannot put it in a no, that's
Okay, if you wouldn't mind either emailing it
Or putting it in the chat. Then we will use that as a
Discussion for two weeks.
That you could show
Hyper ledger composer or explorer.
I think that would be fantastic. Marcus, perhaps you could pick the one that you would like to showcase the most and we could bleed off of that, unless the crowd here has a strong preference for composer versus explorer.
For two weeks time
School
It's markets.
Quite basic and quickly shown. So I think I can make something within a short time frame which which
Demonstrates boss of the two
Fantastic. That would be excellent. Thank you. Marcus for volunteering to share information to everyone about that. All right.
So we have a. We have a question from Marvin who much appreciated for you to just type that up.
In a sentence and Marcus.
Okay.
Does anybody have a project, either that's in the middle of being launched or that's being conceptualized or some questions that they're trying to think through that they would be willing to share with the group.
It can be really could be hypothetical
Okay, well, we'll leave that as an open opportunity, but we have a presentation for next week and we also have Bobby, who's going to go over the
Years.
I think we have a pretty good sketch bell shaped
Let's just go back to
Questions, I don't know, Stephen, how much time you have
Cool.
Okay, so let's just open this up.
The floor to anyone who would like to discuss the Indian presentation or anything else that's relevant.
This is Marcus. Thank you for you in the presentation is quite interesting. I was wondering how you solve like the issue of the wallet and the usability and because when people start to use like search on the browser always have this issue of how to handle the keys.
So that it is a challenging piece so
There is sort of layers of keys involved with wallet.
There's been a lot of work done. So the, the main driver of how that being handled is
Based on work that DHS in the US funded that company names ever in him has done so there's a paper.
Basically call decay MS itself, which covers things like backup and recovery. But the idea is, is largely where it's likely to go is
Sort of what's called social recovery, where you can basically split a recovery T. Share it amongst
A group of people or companies and together that would allow the creation, the recovery of a loss wallet and things like that, but
It's not. It's not. Absolutely not a slam dunk thing yet that's going to take some work in that that's where that agent work that I talked about.
Is going and we're pushing a lot in that area because what from DC gov perspective, we want to see interoperability and
And things that we can recommend our citizens us and our and our organizations use and that's got to be a big piece of it not easy, but we think there's there's some really good things coming out of
This, I want to use the service you're about to deploy, how can how does this look to me in terms of user interface to have a regular a regular like login and password and some key management behind that I do, actually.
I
Think so we're starting with public data so that there's not a risk. We wanted to be safe and doing this so production is based on public data so
There's actually ways to log in or not login just Access the site and browse it
John went over. I think the theory of the project we're working on, so
It's it's a bootstrap for it for a two sided market, but you can just log in or not even login you can just access the site live
Does anyone else have any more questions for any of the presenters today.
Okay. Well, it seems that we've covered at least the first round of questions on the presentations. And again, many thanks to Stephen, as well as Bobby and also Martin for the update
As well as Marvin, who were looking forward to please typing up your question in one sentence and sharing
Either through the rocket chat or the email so that we can use that as part of our agenda for next week, but this has been a good discussion. Thanks also can for sharing your experience as well in the informal discussion, but I think we learned a lot and utterly productive.
Session so many things to everybody. If anyone would like to send any feedback or add anything to the agenda for two weeks time from now.
Please just get in touch. But again, many thanks to everyone's participation and really looking forward to the next one in two weeks. So thank you everyone and wishing you a very nice weekend.
Thank you.