 Great, so we are alive if you'd like to Get started if you're on please feel free awesome. Okay. Thanks everyone for joining us and welcome To our meetup So I'm excited. I'm ecstatic. I'm a little bit nervous To have you all join us here today. It's been a long time to get us to this point I think it's been two years. I only joined last year. I am the community manager for a taller But you'll see the weight was well worth it I come from a corporate background and when joining this team It was really uplifting to see the passion this team has for building identity tools So the team has been countless hours building this and they really put their heart and souls into this So I'd like to give a shout out to the team if you are online And also like to give a special shout out to someone that I haven't seen in a while I see is on the call dad or Donald. You'll you've also been experiencing the mental industry. So thank you for that Okay, so let's get to it as you may have heard the open enterprise agent It's a software agent designed for building Decentralized identity applications as well as services. I think what's super important to note here is that it has been built in alignment with WP standard WPC standards and hyperlegious RFCs such as the exchange Out of bond protocol issue credential protocol as well as present proof Protocol so what can you expect during the session? Let me show you here we go So we'll do a little bit of a tech deep dive and explore the inner workings of the open enterprise agents with part and then we'll follow That up with a demo from Harvey and Curtis You'll also be able to see how we empower developers with the agents develop a friendly approach that makes innovative tech Accessible to all and I think there's no better way than to demonstrate this than a demo again So special shallow to see sign and block the rest of them for joining us from the community They'll be giving us that demo and then to wrap things up We will have no one's piece presented on the roadmap So we'll be looking at the now and what's in store for the future and I think what's the sense What's extremely important to mention here is we're all about community So we want you guys to join the conversation share insights ask questions and come in network with like-minded individuals I will be posting a link with the discord in the chat a little bit later Be in mind this is a life-hearted Presentation before I hand over to the next person. I just have to have one small request Please guys don't mention anything about the recent rugby World Cup finals to this presenter He's a little bit iffy about it But again without further ado, I'd like to hand over to Bart You'll be taking us through what is the opening to class agent and its origin story Yeah, thanks for you had to go there it hurt it hurts almost as much as when I was in the stadium anyway So, yeah, great to see great to see all of you here. I see some unfamiliar faces I see some very familiar faces and some some familiar faces from from the past So shout out to to all of you For being here this like fiat said is it's quite an exciting day I got the boring part of the of the show The talking about sort of hey, what is what is open enterprise agent? So I'll quickly go through that and then we'll get to the good stuff which is which is the demo so What is open enterprise agents? At this point It is a multi-tenant Scala based cloud agents with an easy to use rest API But the goal is a little bit bigger than that because we aim to offer Like a full suite of decentralized identity products. So that means that early next year We will also be putting our wallet SDKs for the web in TypeScript and for mobile as well as a dedicated Scala based mediator into This hyper ledger lab Supporting all sorts of key standards Which sort of sit between the W3C and hyper ledger ecosystems be kind of cherry-picked a little bit and and the purpose is really to sort of build interoperability between sort of the large ecosystems that are out there Which sometimes have very interesting philosophical debates We try to be pragmatic, but at the same time we also try to bring in the web 3 community There so so we've we've originated from the card on a blockchain as a as a VDR But if you sort of realize where we come from if you can go to the next slide if I add You'll you'll notice that In our repos you you see a lot of atala prism reference Because that's how life started So so this this code base is built by the boys and girls at input outputs They also developed the card on a blockchain. So really is this web 3 ecosystem that that we come from and The intention has always been to create sort of this two-way bridge between Real-world identity so we have a number of people in our team that are really expert on like the real-world identity side And the web 3 ecosystems Which is which is kind of interesting given sort of where where they Come from and and we hope that sort of what we build enables developers to get the best of both worlds. So We have a few sort of principles in in our foundation saying hey if we want to be Sweet of of products or a platform if you if you want to call it It needs to be easy to appropriate for all sorts of different use cases for all sorts of different languages And all sorts of different ecosystems so so that sort of really lies at the heart of our design It lies at the heart of sort of our rest api So you can basically pick any language that you're comfortable with and sort of start working with with the agent We also Tried And we're still getting better every day To make it as loosely coupled as we can So there's a lot of interfaces In in the design Hoping that it's sort of easy to maintain over time. We've seen that the number of agents that are that are out there have really sort of gotten themselves into a little bit of a Between a rock in a hard place Do we do did come to do we do did peer for those kinds of things? And we're trying to make something which is easily maintainable over time and some of the decisions that we've made sort of reflect that I'm coming out of Cardano has Upsides and and downsides Which which funnily enough are the same We're big on being peer reviewed. We're big on security So that means that we can't ship anything unless it's audited and and we've taken that on board even if we sort of go from from steward to maintainer or from owner to to maintainer We want to bring that with us and I think lohan is going to tell us a little bit more about that But the code that we put into the hyper lecture lab Has been audited by Kudalski and it has undergone internal IO security audits. So that's I think a very good thing for Platforms that sort of aim to provide foundational pillars of identity And then scalability we hope to be scalable we've we've seen a number of Products out in the market That are very well for proofs of concepts But are hard to scale beyond that into real production cases and we've taken some choices Scala as a language being one of them to really try to ensure that this is going to scale and sort of have a high degree of use In production We're also bringing some IOR and E I've let the term here universal anonymous signatures, you're going to be hearing a lot about that next year It's really cool because it's based on all sorts of standards But it allows you to do selective disclosure by a third party Provided it meets certain Sort of immutable governance needs and that's a really really cool thing which we feel unlocks a whole lot of use cases where On the one hand you want to have anonymity Mostly in like the web three cases and on the other hand you want to have auditability and making sure that people Are compliant with whatever the use case requires so that's that's sort of our foundation and then The last one which I think this this whole move towards hyper ledger reflects as well We're building this for the community, but we're also community members ourselves And we really want to sort of bring it together and make sure we build with the community Next slide please So talking about communities We're trying to bring these different communities together right which is really really interesting Because web three communities They're all about self-management and privacy or anonymity And the goal is really lofty in a way to say we want to build like more equitable system for society It can go a little bit in the anarchistic spectrum. It can also be a little bit more Realistic when it comes to sort of like current systems And SSI communities have really been building solutions for years Which have a lot of Complementarity in terms of the types of problems that they saw And what was funny because I started out in the real world identity community then moved into the SSI community and then moved to the web three community Was that the web three community was talking about a lot of things that the SSI community had no idea of sort of existed and vice versa So when I joined there were a lot of talks and in some cases with other teams That I see there still talks about like on-chain identity I said guys the SSI community has solved this problem like seven years ago So we feel quite strongly that combined They really could offer like the next step in building this next generation of what we call software defined trust infrastructure So we tend to ask ourselves like a lot of questions and think hey, what is what is it that digital identity can bring to web three? Especially if it goes beyond like the KYC use case that sort of everybody keeps talking about But also what is it that web three can bring to digital identity? There's there's lots of interesting governance structures in web three That really could be helpful for for digital identity in the next generation if I look at For example, yeah, it us to which is which is going on right now What you see what has started out as like this really? forward and progressive Movement towards self-suffering identity Is really being caught in a net of like traditional Trust providers and sort of industries that have a lot to lose And and I feel a little bit more of the web through web three ethos Could could bring a whole lot. So We hope that jointly they really can bring significant change to the world next like this And in a way, if I had mentioned this, this is this is really a continuation of our journey So bear with us Because yes, we've been working on this for close to two years And credits go out to to a lot of people Many of which are in this call But it also started inside of this company. So For us moving towards working in the open It's not as straightforward It's super easy to begin an open source project if you started as an open source project If you started as a project in a company, there's lots of dependencies when it comes to Hey, we use JIRA to track our issues How's that going to work with the community? And so we're trying to figure out a lot of those things as we go And we thought the best way to sort of figure that out just to get started And try to have rapid feedback loops and then sort of learn from that and improve So you'll also find references to atala prism in our code base and documentation Those will be updated As we sort of progressively transition everything into the open enterprise agent lab But we thought it was more important to just get it out there and get start getting feedback and start getting people to work on it Then it was to wait and make sure that like everything is perfect And then there's like this one neat package and everybody was like, oh, well, great. But now what do we contribute? So bear with us Call it out if you see something if you want if you think it needs improvements We have bi-weekly maintainer and contributor calls We have a discord. There's a hyperledger discord as well And otherwise just just raise issues and PR us via the repository that we have on github You're all very welcome This is the moment where I sort of being technically responsible Get a little bit anxious about The issues and things that are getting raised that are going to totally derail our planning But don't let that hold you back Let's Let's get in the conversation and let's make sure we we make this a good continuation of our journey And now for this stuff Thanks a lot Yeah, now for the good stuff. I'd like to hand over to Javi and Curtis Yes, so I would like to start by thanking obviously the whole team because it is a little bit unfair that there's only Curtis and myself showing Showing what we are about to show and it is worth mentioning that without the rest of the team that it would have been impossible and This is a success of the whole squad not not on individuals And stuff like that. So yeah, having that said, let me just try to share my screen Hopefully everything will be as we expected Cool, then I will start initially by sharing our Documentation portal because I think it is one of the first things that you guys are going to land on and I wanted to make sure that It is properly explained and shared so Yeah, in the presentation pdf you guys have the url for these doc sites but in general we have a lot of tutorials and documentation about the simple concepts and the different components that we have Together with that we have simple tutorials that are speaking about concrete Flows like issuance establishing a connection verifying creating a credential definition creating schemas and so on As a third step Or a third block we have api documentation, which is describing Like a swagger api docs or something like that And then yeah, we are planning to to even improve this even further So you guys can run the api calls from here directly But meanwhile, this is the this is what will help you understand what input fields you need to be sending to create in this case The verification policy and in the other case how to receive or what data you would expect to get in exchange Then getting into a little bit more detail if you want to know about The ADRs, ADRs are the architecture decisions that we are taking and you guys can see the reference and the backtrack of all the decisions that we took Since we started and also the presented spec, which is Already approved in the repository and yeah, it's also documented there Then lastly, I would say that As I was saying, this is for the the open enterprise agent Which you can see in this side here a prism mediator the prism node and the cloud agent If if we would understand What is the typical interaction in self-sovereign identity? We would have the verifier We would have the holder and we would have the He said it in the opposite order, but it doesn't matter We would have an issuer, a verifier and a holder. The holder is the one that obviously receives the credential The issuer is that entity that has been registered in a publicly verifiable place So that whatever that person or that issuer is issuing you as a customer or as a holder Some other verifier is able to verify that Without having to to reinvent the whole wheel So, yeah, having that said, there is the open enterprise agent, which is what we already presented Its role is to become an issuer or a verifier in the self-sovereign identity flows Then how how do SDKs communicate or how does the holder communicate with the prism agent? Keep in mind that a browser is something that you can turn off in five minutes So we need the mediators to be able to capture messages for that web wallets or that mobile applications while they are Charging their phones or whatever they are doing That's the role of the mediator. It's the the prism mediator, which is its own repository and its self-document Then okay, we know that the prism the open enterprise agent speaks With the holders through ditcom protocol and through the mediator But also the different holders can speak between each other by only using the mediator Okay, having that said, I think we are going to directly jump into Into the main entry point of this whole documentation While we are constantly trying to improve and minimize Some errors. I think that yeah, it is in a good shape right now Again with some constraints on the mediator, but overall things are working really well and I will just go through The different steps that we have So Yeah, it is basically explaining your scenes So starting from cloning the repository deploying and instantiating your own environment declaring your variables here Then if it's telling you what command you need to be running It is also guiding you on the API calls that you need to run to issue verify or Connect with the whole the holder and the the the open enterprise agent And now without wanting to bother you with like boring stuff like the one not boring But you know what I mean? I think that we want like visual stuff to be happening so What I'm going to do is basically go through this demo But myself and a little bit faster because if not it it would wouldn't We wouldn't have enough time So yeah, here I have all the API calls already prepared just as a single click I will send the API call that I need And then in this command, I have the open enterprise agent with the specific command of the quick started guide I am going to basically There deploy and download the images right now And meanwhile what we are going to do is to To save us a little bit of time we are going to be using A mediator that we already have deployed Which is the beta mediator And together with this while the thing loads I am going to start The browser demo cool as soon as this builds This is like a reference wallet implementation Okay And here the first step is establishing the connection with the mediator and establishing the mediation exchange and knowing In order for the mediator to know how to deliver you the message So we are going to just start the connection Then the first thing that we should see here as we as this is confirming is that Every time we start the agent I am sending myself a message So this basically confirms that the mediation has been done correctly And now I am going to go through the creation of each one of the steps So Yeah, the first thing that we are going to do is Establish a connection with that mediator With that prism agent, sorry That is done Through this api call Okay I'm going to just clone the invitation URL And paste it here to establish that connection Then this is the first step where we are storing then some things are happening behind the scenes The mediator Sorry, not the mediator the prism agent has detected that we accepted connecting with them And this is the message from the open enterprise agent confirming that the connection has been properly established Then you would use this ad that you that the prism agent has the open enterprise agent has returned you To know where do you want to issue that credential to Again, apologize as Bart has said earlier. It's still difficult for each one of us to not say prism But yeah, I swear I'll I'll do an effort on that So the next thing that we are going to do is start sending the credential offer Okay, there's one step that we need to do before I don't like Demo effect, I guess um We need to have a publish it present it And because I started with an empty environment that present it is not properly configured so Yeah, let me first create that one. I created a long format Present this is something that if you start a local environment that you will need to do anyways So it is good to To specify it. Okay. We have the deep reference here And I bet that we can now go to the credential offer that we tried to send earlier and as you see now it's not failing anymore Then well what will happen here as you see is that we are receiving a credential offer through ditcom And then automatically and to speed up things the user has virtually accepted that he wants to receive that credential And has responded to the open enterprise agent. Yes I want that credential the open enterprise agent has then checked Whatever needs to check and has sent me The credential in a jwt In the prism jwt format So this is basically the credential then the credential is not what you would usually share Right when a very very fire is asking you something or to prove something What you do is you use this piece of code or this credential to generate the proof So you would never share the credential Then next step this would be a very fire a very fire wants to ask me if I Have a credential with this email address for example So that's what we are going to do here then the request pending As as soon as I understand we should receive the presentation request The user then would choose if he wants to share this information with the verifier or not So the holder always has the power to reject sharing this credential And then in this stage there is no message in response. So right now if we went and checked That presentation ad it's probably already resolved. I do not have postman properly configured here But yeah, we have proven it works So here the verifier it's already capable to determine that this credential is valid or not Then this is just one of the examples. It's prism jwt We are about to integrate unencredited really soon, which means that we're including selective disclosures. You don't know let's prove and privacy preserving credentials So yeah, that's where the the whole demo ends Again, I want to to thank and make sure that we understand that This is not about the wallet SDK in typescript. There is so much effort that every single of us have done in the past year That it's really worth thanking everyone and repeating that if we need three times or four, it's okay So yeah open to questions feedback or any other comment that you guys need Maybe just one addition to what you just showed I've had demos in the past where sometimes you get the feedbacks like yeah, yeah, it's a shame that it's sort of like I didn't see what was actually happening But what you saw was live And and one of the things that we set out two years ago and Tony and Darryl if you're listening We wanted to go to like to first credential issued in under five minutes. I think you did it in three And but I think it it shows as well that There's a lot of care gone into things like their quick start guides to help you get started really quickly There's a lot of heavy lifting in the reference implementations and in the SDKs But there's also an ability to dig deeper and sort of make changes if you if you want so Yeah, that's off Harvey to you and the team Jim you have your hand rest um Yeah, so real quick question. So I've worked With I'll call it some of the other projects in hyper ledger around identity And so I'm curious I don't know sort of the you went through a nice sort of overview of what you've done but I'm not sure What in a sense the origin of the project is Given the other frameworks that already existed. So if I look and I say, okay, here's you know hyper ledger areas Here's von ex which is another open source Solution and I'm trying to build what you already have I'm going to say gee those are already available for some reason You chose not to use those as a starting point even though they're open source and said no We're going to rebuild this from the ground up for some reason and I wasn't clear on that Yeah, so a couple of there's there's a couple of reasons for that and I would say some are probably better than others um I think a what what we saw when we made an analysis of the landscape was that there was There there are indeed very good Well solutions out there But they all come with their own set of trade-offs and the more mature that they that they become the more Difficult it would become to sort of deal with with some of those those trade-offs and then to give you an example, there's There's now a discussion on going in the acrobyte community on whether or not they should support it come to that has been going on for a while and being being a opinionated web three tech company Where where we came to was like, hmm We really like some of the things that they did but we don't like all of the things that that they did we wanted to Build something that was more loosely coupled from the ground up We picked scala for I would say purposes of scalability and then sort of concurrency especially sort of when building distributed systems Seems like a sensible thing to do And we didn't want to necessarily have And I think this comes with Our cardano background To be sort of dependent on indy and I think a lot of the agents Are still have have more or less of a dependency on indy even though That part is also sort of being being open sourced And all of those things combined sort of sort of led to saying hey, let's let's sort of Build something which Add something which Worst case sort of Help helps sort of bring a slightly different perspective of like web three communities into into the Identity space and sort of best case Provides a lot of interoperability and actually contributes some of the things Oh, so a lot of the people in our team have also started to sort of contribute In the mediator working groups On the non-creds specifications, so so we're hoping to sort of Participate and then it's always good to have some skin in a game and saying hey, we we want to have something that sort of does justice to our vision And start there and then then see How how that plays out Okay, all right, so I guess I wish your team a lot of luck with that what happens is as you know In the space there's many other I'll call it SSI implementations out there not just the hyper ledger ones, of course And so the challenge of it is for the rest of the world when you look at the enterprise level and say what are we going to use? We don't tend to want to lean into I'll call it You know bespoke implementations of something that's all and so to your point What's probably great about what you've done is it's I'll call it probably really I'll call it fit for purpose So in the sense that you already had a set of use cases in mind Otherwise, you wouldn't have done this. So you have a set of use cases and you had I'll call it an environment that those use cases make sense So my suspicion is all of that has high business value Immediately, do you know what I mean? Something you can realize in the short term, which is excellent That in a sense makes the investment worthwhile The other side of the coin is on the enterprise side when we look at identity solutions And say what's out there? Open source is good. What's better is if you have you know standards compliance and you did point out that did come to You know questions. There's a bunch of other things like that And then beyond the standards compliance is in a sense the ability to leverage and extend The existing work out there instead of going back and rebuilding the whole foundations again So the enterprise side is much more complex where I think the Um, I'll call it fit for purpose business goals, which probably really fit well with as I said what I think you're doing Are going to pay off quickly for you. That's my guess Um I I tend to agree with you. I think and I think it's I think you're right on it's a fine balance um One of the one of the things we we've really tried to do is is Make interfaces in in our design. So so to your point saying yes, yes, we have an initial set of use cases that we see that come mostly from the web 3 space At the same time We've made some uh decisions So it's easy to appropriate for other use cases as well um For example, one of the things we've done is is centralize all our cryptography throughout um The agent but as well as the the mediator and the and the sdk's So that should you require a NIST compliance stack? um, you could sort of switch those out relatively easy and and I don't want to hand wave anything with with cryptography But but the setup is is there to make that that easy um at the same time We've started with by linking the web 3 ecosystem to the digital identity ecosystem or the ssi ecosystem or specifically um, the next step is sort of expand that further in the in the the I would say the the regulated identity space So open id connect and open id for vc and stuff like that. They're all on on the roadmap Um, and we'd love to work with the community now to sort of say hey, let's let's figure out where this needs to go. Um to be easily maintainable highly performant and sort of Easily appropriated for whatever use case beyond the initial set of use cases that we have Okay, and I my guess is from what you described You were using open api as the driver. I guess to generate the uh microservices For your platform. Maybe i'm wrong on that. I don't know, but I had that impression that you were using open Yeah, so so yeah externally we do Um internally it's it's it's slightly different But yeah for all intents and purposes we we have a nice rust api which is an open api specification Um, that will help you drive pretty much any integration that that you need Okay, thank you very much You're welcome Patrick Hi, uh, great presentation. That's very good So I come from the devops where I work and I come mostly familiar with the obviously hyper ledger I kept by javascript and some of the w3c Uh standards being the verifiable credential in the vc api My question for you is in your presentation you claim that your solution is built around open standards Uh, do you have a way to demonstrate this? I know, um, what I mean by this is different communities They have these test suites and test harness available for you to Sort of demonstrate that you have implemented these standards, especially on the w3c side Have you ran any of these test suites or what's your approach toward quote unquote claiming That you implement these open standards um That that's that's a totally fair question and the answer is in some cases we have and in some cases We have a plan but we haven't yet implemented it. So Um for a mediator for example, um, we've actually created a test suite Together with the the diff working group And we have a number of mediators in there and we're sort of expanding that that test suite um for the agent side, uh, the the initial aim Was to look at the Aries test harness Um We haven't done that yet For for a number of reasons Um, uh complexity of of of running it was one of them and but also just sort of from a priority perspective We we just haven't gotten to that um, but it's definitely sort of on on the radar to do because um, um I've I've been in a number of these plug fast. Um, and uh I think as anybody in the ssi industry knows like it's it's it's easy to to make uh a spec compliant implementation That doesn't mean that it's interoperable. So it's going to it's going to be part of our testing strategy Um as well where we sort of basically for every feature for every endpoint or for every Protocol that we sort of implement. Uh, we want to sort of embed Uh, that testing Sort of at the at the system level in there, but we we haven't gotten around to that level yet Thank you. Yeah, and I think what you said is is very true The spec and the version in the field sometime you have some interesting discoveries Yes, um, the latest the latest the latest did peer one is a good example, right? So so we have we have the the latest mediator that we have is actually supporting did peer for um Probably it would take us somewhere up to a day to sort of get the whole system on did peer for The reason why we haven't done it yet is that We want to sort of talk with the communities and say hey, when is everybody making this jump because we can be the first But then you would not be interoperable and that wouldn't give you a whole lot of value Yeah, no, I agree like and that's a bit what I was thinking because obviously the different frameworks have different ways to make standards and making standardized and Some frameworks they sort of make the standard before the implementations come as others They will wait until you have implementation to finalize it. So it's kind of an interesting Different approach If I can allow like a second quick question Do you have plans for backward compatibility? Like you mentioned earlier about akapi supporting only did come v1 and You know akapi at least here in canada. It's fairly used in production by governments and smaller business Do you have plans for some backward? So that let's say someone wants to join the ecosystem and there's already all these deployments out there And they would want to choose a solution that will be able to at least still communicate with those Is that in the plan or you're sort of waiting for these frameworks to Before you go ahead and answer, um, could we take this question and then say this question lost and then I'm cognizant for time. We just got the demo Um, yeah, cool. So I'll answer this question the other questions. Please put them in the chat. I'll answer them them there. Um, this one The this is a continuous conversation in some cases It makes sense to sort of commit and say hey, the rest will catch up in some in other cases We want to be a bit a little bit more liberal What I expect but this is a personal expectation is that Um On the verification side of the equation We're going to try and be as liberal as possible with regards to the standards that we support for the did methods or the credential formats that we support Um, when it comes to issuance and holders, we might be a little bit more opinionated Um, so I think I think that's uh, that would be my general answer And I would say it's also a little bit up to the community, right? If we if we all make the leap into a certain direction Um, but but given where everybody is Um, that that is I mean the nature of standard work is that it takes a long time. Um, so I guess that's also something that's We'll try to figure out with the community to sort of see where does it make sense to be a little bit more backward compatible um He for us is which we'll start doing as of next year's like try to be as explicit as possible in terms of We have a contract first approach to sort of say which version of the contracts and which protocols do we support with which version of the agent Um, but but I'm I'm going to assume that we're going to have to fine-tune That approach over time together with all of you guys awesome um up next We've watched better than one demo having two demos Um, so now for a community demo I'd like to hand over to beyond from block for us to come and present to us Yon over to you. Yeah. Hi. Yeah, so try Um to shimmer screen So do you see the presentation? Yes. Yeah, great. Okay. So our journey with satara prism, which is now the open enterprise agent Uh F the others we will mostly still refer to it Satara prism and block trust. That's me and ad who is also on the call So, uh, what we're trying to do is not give you like a real demo because we built so much stuff and it's like hard to fit into The few minutes we have but give you more often Overview over the ecosystem what has been mentioned before and how The things we will fit into that ecosystem So in the center, there's the prism hosted agent or the open enterprise agent We have seen like something you can host somewhere in a cloud on your server As a back end running a stalker But mostly like having apis to manage the dates through credentials like did come communication and um below that It's usually a vdr in the case Of the open enterprise agent or prism is of course the katana blockchain. It's still bound to the katana blockchain in many um aspects That as a project will evolve it will support other uh vdrs Um, but the agent is not directly writing to the katana blockchain. There's something in the middle um, which is in our case the prism node and um, so you would first like connect the The agent to the prism node the prism node would then write the transaction to the blockchain similar basically like Hyperleda hyperleda indy So one project we built really at the beginning was the block trust analytics platform Um, I will quickly share um some screenshots So you can go there at analytics block dot block trust dot def and that's uh, um More or less like indy scan where you can look at the blockchain and see well now Here's the prism transaction written to the blockchain and it's live updated So you see what's happening on blockchain and which prism transactions are written there you get some statistics And also you can make a deep dive and really understand on which block is what written Uh here for example, you see there were dits created and a did updated And also it gives you like a possibility to do resolving of the dits So this is like one of the tools, uh, which wasn't provided By the prism team out of the box and we thought it would be very helpful for developers Um to better understand what's going on behind the curtain um another thing um Which comes out of the box with the open enterprise agent of different sdk's so that you can build your own wallet For example, there's the type script sdk. There's the swiss fdk and there's a common multi-platform sdk and we as block trust team Took that and also build our own sdk Based on dot net and build our own wallet. So we have a small wallet To do which is um 100 compatible with prism And like the classical wallet, you know like to Create dits to exchange credentials and also have a few screenshots like the browser extension wallet That's like the main difference um to most of the wallets out there though You would click like on a web page on the small icon of the browser extension And the wallet would pop up and you are able like to manage your dits and credentials And um, there are many features included like most of the wallets have But we have also for example chat So it's based on ditcom v2 Another basic message protocol. We support a lot of a lot of the other protocols like for changing the credentials um Discover features pick up protocol and so on Um, but that's um a feature that you can chat and then you can like use of course the prism mediator um to send One message to one wallet to another and um That was a very very short introduction of our wallet, but you can go to our website We have a video With a few demos with a teleprism how the wallet works Uh, especially a few videos about chat And also one feature we have in the wallet is like sign in you could sign in into into a website. That's also in the Feature set of the enterprise agent and one other thing we built is like communication with an AI agent So you would go to a website and then you click on the small button below like connect to agent The wallet would pop up and you can use a ditcom v2 connection um to talk to an AI agent At a backend service Well back to the map, um, we saw like the The prism mediator that's also in the package, uh, which you get with your own enterprise agent And as block trust, uh, we also built our own mediator implementation Uh, which mostly helped for inter ops testing like getting the protocols right that everything is working um And uh, the last thing, uh, we built Um, it's a credential builder Also give you a few screenshots of that because um When you when you want to demo like SSI in general and usually you have the the example of the trust triangle It's for people not coming I'm not having an SSI background. That's often like hard to grasp just seeing it in code And so we built a nice tool for it. Uh, which is basically a ui on top of the enterprise agent And uh, it looks like this so you can go to credential builder block dot block trust dot death and then There's a small plus icon and then when you click it you can set up an agent So you would host maybe you host your own instance of a prism agent or Maybe there's some hosted instance out there And then you can enter the detail and then connect to the agent and therefore have an ui to drive the agent And in the next screenshot, uh, we have three agents set up. So on the left Um, it's an agent which is basically currently an issuer mode. So you could for example, like You set agent to connect to another agent and then create a credential on the schema and issue that credential to another agent Like the middle one which is currently in holder mode Or you could like have also assert agent Which might be like in the verifier mode and then you have like three instances next to each other And go through the different scenarios issue and credentials Sending them over did come to another agent and then the verifier flow so That was a very very quick summary. Uh, what we have built in the last one and a half years And yeah, we continue building on prism and Maybe we we get now also a real life demo from another prism project Our community project, but if you're interested in what we're doing and want to contribute or Help us out feel free to get in touch with us So that's uh for me Back to you fiat awesome beyond. Thank you for that. It was a great presentation I like bill mentioned if you guys do want to get in touch with him Bjorn, could you maybe share your email in the chat? To come over that and then everyone could reach out to you. Thank you Okay, next up. We've got another community demo before we jump into the roadmap Uh, john, are you on the line john and Roberto? Yes, hello to you guys Uh, hi, um, i'm matthew. I'm along with john and reberto. We're part of the c-sign team Just want to say thank you all for having us today We're very excited for the opportunity and we just want to thank you all for your hard work But i'll keep that short and pass it off to john now for the demo Great, let me uh, show my screen Okay, can everyone hear me now see Can you guys see the screen? Okay, great Uh, thanks matthew and awesome work Bjorn and ed Um, there's a lot of really exciting stuff coming out of this community. So stay tuned for sure Uh, first of all, thanks so much to everyone at iog the atala prism slash open enterprise agent team Bart fiat and javier Tony darrow everyone who's cheered us on along our journey Um, it's been really really fun Uh, and david boswell great to see you and great to be back in the hyper ledger community once again Uh, really honored and excited to be here My name is john and i'm happy to give you a sneak peek today of something fun that we've built with the open enterprise agent Uh C-sign is a fully private end-to-end encrypted platform for signing certifying and verifying agreements between parties using self-sovereign identity and blockchain Let's jump right in and sign an agreement Now what you see here is two different browsers Uh on the left and the right on the left I'm signed in as john myself and on the right. I'm signed in as demo signer These are both kyc users Uh, and let's jump right in So I so Let's see let me do this Okay Now agreements on c-sign can be anything documents images, uh, or other media types Let's upload an agreement in this case. I've got my uh slides for this demo right here and I'm going to Upload them and I want a demo signer to review them and sort of sign off on the latest revision So I'm going to upload them here. Let's see uh latest Slides Uh, I'm going to give demo signer to the 20th to take a look at them and these are Now let's see version 4.5. Please take a look And approve Okay, and now I'm going to add a demo signer from uh to the agreement Okay, so I click add from contacts now. What are contacts? Contacts are actually did peers with whom I've made connections with so it's sort of like an ssi friends list Um, I have a cryptographic connection to each one of these kyc people on the c-sign platform So I know I can trust them. Um, I'm going to add demo signer here Okay, and I'm going to request a signature now when I request a signature I'm actually signing the agreement myself And then inviting them to do the same Our signature protocol uses biometrics to authenticate signers. So you always know you have the right person signing So when I do this you can see Um biometrics I get a biometric challenge. I'm going to use my fingerprint On my laptop to easily sign And invite And you'll see over here on the right it automatically popped up on demo signers screen And I want to draw your attention right now into the upper right corner On this notification up here. So, uh, these are notifications sort of invites and uh status on documents All of these are end-to-end encrypted using didcom2 Which is also available on the open enterprise agent Uh, so now I'm going to go through let's say uh latest slides And I'm going to review these and let's say I've proved them fine I'm going to sign Again, you can see demo at c-sign is the user. I'm going to use my fingerprint once again boom, I've signed Back over on the left. I get another notification saying the demo has signed. That's great And now you can see uh signature has been verified and now I can certify this agreement So I'm going to click this And I'm going to click certify and then we'll talk about sort of what's going on now You can see here that we are publishing on a blockchain So what we're doing here is we're taking the public keys of each signer and we're creating a did document That represents the agreement and its metadata and we're publishing it to the cardano blockchain And then we're going to issue a verifiable credential to each of the signers Who participated in the agreement and you can see here now it's done Now let's kind of inspect what we've actually done here Let's drill in so I've got all this metadata here. This is great and I'm going to go to the status and this verified thing Let's copy this and let's look at the actual verifiable credential we've created for this agreement If we go to jwt.io, we paste this in let's look at the actual payload here and sort of inspect what's happened Now I want to point something out here Right now for this demo We are showing a clear text verifiable credential just so we can talk through it and you can see the contents But actually we normally use end-to-end encryption So the agreement metadata would actually be encrypted and only the creator and the signers will be able to decrypt and read the metadata In fact, not even C sign can read your agreement metadata. It's all private between parties But for this demo, let's look at some of what's going on here. So here is the did prism This is the actual hash of the agreement that gets created. You can see the file name here Okay, and then we have an array of signatures Which are everyone who signed so john has signed this here and here's the date that john signed here's the proof and demo has also signed and The timestamp and their proof. Okay now If you notice over here the signatures also say signature verified. Well, what does that mean? so verification is yet another part of c sign and Each Each signature has a cryptographic proof embedded in the verifiable credential which prove that that person has signed So for example, if I click this we can look at this little verify tool if I go back here and I get my did prism And let's say I put this in here This should verify right, but of course if I change anything Um, this will not This will not verify you can imagine in the future like an api Or interface or something like that where a third party can verify the validity of agreement For example a lawyer or a judge if there's a dispute or that third party could request proof via ssi from all the signers All right Now let's go home here Now what I also want to point out here is sort of what you're not seeing With c sign, we've been able to abstract away all the complexity of self-solving identity Into a very familiar web experience So what you've seen right here is we're actually using ssi identity wallets dids for people dids for things Invites mediators didcom verifiable credentials and even the cardano blockchain All on top of the open enterprise agent and yet any internet citizen could use this without having to know any any of that stuff We truly believe that this is a project For the masses. This is not crypto. This is cryptography and open enterprise agent gives us the tools to make it useful for all of us Now i'm going to go to the actual slides that we just looked at and we just approved. Thank you demo for approving the slides So let's a quick recap. What do we just look at? We saw how c sign Uses open enterprise agent to manage ssi identity wallets cryptographically sign certify and verify agreements Write agreement hashes to a blockchain and issue verifiable credentials What's coming up? Well, we for enterprise use cases will have multi-tenancy support We'll have a private beta on test net Going to mainnet in 2024 and there's a lot more planned I do want to shout out the c-sign team directly Matthew marino in new jersey our brilliant lead engineer Roberto Carvajal down in Chile Now some in berlin who's seen all who's created all the beautiful bits that you've seen today And once again, thank you to everyone who's been involved The iog and atala prison team for always being welcoming supportive and responsive along the way The community is great. Please join the discord and don't be shy Uh, and if you want to stay updated with us, you can visit us at www.c-sign.io You can sign up there to be notified when our Test net beta will be available Or contact us for a more in-depth demo Thanks Also, John, that was amazing. I remember you guys first was designed towards turn into now. That's absolutely amazing Thank you. Thank you for sharing John. Would you give me a payback? So just uh, pop your contact in the chat as well in case Anybody would like to reach out to you for further discussions Yes, sure. Please answer questions or ask questions in the chat as well. Thank you Okay, so I guys my um video is up. I'm getting a little bit of lag at the moment Me no wants to go out and see my screen I think we lost my hand Yeah, well, we're giving him a minute. It seems like there's a couple questions or at least one question in the chat maybe we can answer Or maybe it's already been addressed but I see the question who pays for the gas fee and then whoever writes the transactions Yeah, yeah, so there's a There's a card on a stack sort of that sits behind this Which which requires a wallet in in ada Whoever operates it. We feel that this is like a more more business operations question sort of Who writes the fees one of the things that we've done we had a we had an initial version Which sort of did a lot more writing on the blockchain we've progressively sort of moved To touch the blockchain as little as possible or as little as needed and make the the verifiable data registry interface Progressively pluggable. That's not fully implemented yet, but hopefully that will come On the near term meaning H1 next year. We should we should definitely sort of make make good steps In showing that to you Great. Um, I don't see any other Sorry, go ahead. Yeah, no, no, I can I can I can share my screen if uh, if if needed Yeah, that'd be great. I don't know if there was more planned or did you have more slides or presentations or The other roadmap great stuff. Great. Yeah. Yeah. Yeah. So so we have uh, we have lohan That can talk a little bit about the roadmap Loan floor is yours Hi everyone, um, thank you for being here and it's been a quite interesting journey to get to this point over the last year and a half But I'll take you over where we are today Kind of high level roadmap features that are Kind of on the roadmap already and then I'll also kind of talk a bit about the stewardship and the governance of the open source project itself So where we are today is um, as you have seen by now, we have an open enterprise agent It can operate in single tenant mode or multi tenant mode Um, it exposes a rest api interface that you can easily integrate within any programming language that you might choose We have an open source version of the mediator and the various different wallet SDKs As Bart mentioned the objective is for all these different components to ultimately end up as part of the open enterprise agent in hyper ledger labs um, our Open enterprise agent is very easy to spin up and to get started and we have great documentation I suggest you go and read it and run through the quick getting Quick start guide to see if you can kind of get it all up and running and have all the components working together Uh, what we have done over the past year. We also have now have a wcc compliant d i d methods Our d i d method is called the prism And we are supporting wcc compliant verifiable credentials as well as multiple credential formats at the moment We have available jail ability and soon annan crates will also be released Uh, we are linking to the our current vdr is But we are planning to kind of go with an interface approach as Bart mentioned as well That will ultimately allow the open enterprise agent to work with multiple d i d methods multiple vdrs. Um, in a way that's easily Interchangeable or enhanceable um for developers and maintainers of the of the software One of the things that I think adds a lot of benefit to the open enterprise agent is our cryptographic perimeter library It gives us quite a lot of crypto agility. Um going into the future and I have a slide on that specifically and then one thing that we've integrated is We have an i m integration so that when you use multi tenants the multi tenant feature or custodial wallets You are basically authenticating into a i m system. It's currently currently key cloak But we are planning to make that an interface as well. So if you use Ping or opta or any other I am kind of system in the future. You can integrate the multi tenant mode into your existing i m systems And then all the secrets are kind of Stored and accessible from a hash you call fault. So that is where we are today And Bart if you can maybe just go to the next slide for me And what we are going to release soon is a sandbox environment and the objective of the sandbox environment is really to have a user friendly testing and experimentation environment And furthermore also to obviously run the open source code and as we make Upgrades or add features etc that the sandbox environment stays in sync and accessible not only to us but also to the community as well um Next slide Bart So kind of looking from a roadmap perspective going Looking a bit into the future. This is definitely not everything that's on our roadmap We have quite a lot of interesting features and functionality that we are at least ideating on But it is not set in stone. So I didn't actually add it here But join the community calls and you'll find out all the magic that's coming Uh in in the future, but what we definitely have done already is oidc support Adding other clinical formats like select which is closed as jdbt's We already have a version of the universal resolver, but we want to make a universal resolver driver So other people can also resolve the present dids We had a question about backup and recovery That is on our roadmap and to make it as seamless as possible to backup and recover either from agent level or from the sdk level And we will see how we progress on that that will most probably be a phased approach across the various different components We also looked at the incorporation of trust registries So kind of how can we link the agent to the concept of governance and one of those technical components is normally the trust registry decentralized web nodes for For storage and extra features and capabilities is also on our roadmap And then something that i'm excited about that bar touched on as well is this open interface approach Where we want the open interface or interface approach for effectively everything in the agent from the did methods that the agent can support And the verifiable credential formats what vdr you want to connect to That is the first step in that approach is we are going to start on the vdr And then we will go into the different components to make all those interfaces as well And one of the things that we kind of identified from very early on is we want to ultimately have open enterprise agent Being able to do universal verification or at least on the the methods that the did methods that it can resolve Okay Oh, let's continue. Um, and From a roadmap perspective, uh, I think we're on an exciting journey now because one of the things is this We have developers from within io g. Um, and obviously now going to high village labs We're going to build a community around it and the real question is that you will have a big influence You'll have influence on on on the roadmap and if there are things on the roadmap that you want that we might not have Bring it to the community calls and we can start incorporating this and actually create a public roadmap that everybody Not only can influence but it's visible Um, and usable by anyone who are interested in the enterprise agent and next slide All right, so, um From a stewardship perspective at the moment rather at the moment We used to be the owners of the code base now that we are moving all of it into hyper ledger labs We are moving from owners into stewards And we have a few principles that we defined that we really kind of want to Put forward in terms of trust trust with the stewardship. The first of them is obviously developing in the open Um, so collaborating discussing agreeing with the community. Um, what is the best but what are the Different features and functionality accountability, etc that we want to support on the open enterprise agent We want to communicate and decide consparently with the community so that there's always um A trust relationship with our community and we just don't build things that we think might be needed That also listen and bring the things that the community needs back into the open enterprise agent And then also providing clarity and strong commitments about directions. So Meaning obviously from our perspective The open enterprise agent is going to be utilized as a foundational component for ssi into commercial strategies But making sure that the commercial strategies that interfere with the open source and that the open source is kind of always the I can say the the latest and greatest version of what we are developing into different features and functional Next slide please Okay, so a few commitments that we want to well that we are we already committed to as stewards. Um Is that first of all the open source is a priority So any features and functionality with first release released in the open source code base and then where We needed or where we will consume that from a commercial perspective. We will move it into the commercial environment Um, we also also want to make sure that we have a feature complete code base That all the ssi functionality is there for you to use in public or private ecosystems Um, we don't want to impose any artificial limitations So the the open source code base will have unrestricted usage. You can use it. You can modify it You can add to it. You can remove from it. You can do with it effectively what you want according to the Apache 2 license um We also do quite a lot of work in terms of security and testing. Um, so all our testing and our benchmarks and everything will be Available for public consumption something that you can use and you can see what is the actual performance of the agent And how it can haunt us over time um, any security related issues, obviously we want to hear about them first and handle them Internally and once it's resolved, obviously disclose them in a responsible manner There will be no exclusivity or non exclusivity. Um, compared to the open versus versus commercial versions We will share all our benchmarks in order as I already mentioned Then one of the big things is we want to have uh, the community being a very big part of the governance And also be very inclusive in our decision making. Um So once again, I invite you to to join our course and really come and raise your voice and kind of contribute and collaborate with us Uh, next slide so on the Cryptographic parameter library, it's basically a crypto library that we develop That is going to be used across all the different components the agent and mediator stks And the main reason for that is first of all that we Can control the crypto agility if we need to have new cryptographic primitives, we can add them We can test the cryptographic library ourselves. It will go to external external audits or major releases once a year There will be internal orders of that. Um on minor releases currently monthly And it really allows us to like but also mentioned if we need to start supporting this related Cryptography we can just implement it at one place and utilize it across all the different components um Okay, next slide and This is really kind of my call to action from a community perspective. Um This is kind of built for the community with the community and ultimately for the community And what we want to do is we want to create an environment of community center collaboration and We want to leverage the collective expertise of within ilg as well as the community to create and innovate on open enterprise agent and Really kind of end up with an enterprise great solution that is highly versatile highly performant highly scalable and highly robust Um, we really want to give you a place and hear your voice So that you can influence our roadmap and what we are planning to to build in the next coming years And then also from a roadmap perspective. There's already been a question from Jim Do we have an open publicly accessible roadmap at the moment to answer that is no But this is part of the plan is to really create this open roadmap that is visible It's going to be in get up and anyone can basically see it They will be transferring it transparent planning around it And then we can co-create the roadmap and really have a democratic management aspect so that Everybody is well aware of what's happening and when new features are Going to be launched and more or less on what at what time for it And that is a high level overview of the roadmap as well as our kind of Hope for the open enterprise agent from a community collaboration perspective And that is all from me. Thank you very much All right Thank you. I think we have fiat back If we don't I'll just I'll just take the answer the q&a Sira, do I pronounce that correctly? Yeah, that's uh, that's correct. Can you hear me? Well, yeah Yeah, amazing. So my name is Sarah. I'm from foshos. I'm based in japan So I have a few quick questions. So um first one So you mentioned in the beginning of the presentation you'll be Releasing the wallet sdk for typescript next year, but we've We already have access to that repository today And what exactly will you be adding to the existing repository from now to the beginning of the year? Um, so so so it's mostly a governance question, right? So so we have The sdk and the mediator that are currently sort of still on their io that those are public open repos So you can go into them. You can use them today But we want to bring it all under the hyperledger lab umbrella So it all has the same governance And it just makes it much easier to manage As a whole so the maintainer calls will sort of contain like the the whole suite rather than just the agent and then For the mediator you need to go elsewhere and for the typescript sdk you need to go elsewhere So we're just trying to centralize that all under hyperledger also to make sure that it sort of has the right longevity Sort of the same longevity as as the agent Has and we cannot sort of revert back from that From some sort of commercial interest I see. Thank you. Thank you And so I believe that the sdk and other tools that you're building Will improve the developed experience of open enterprise agent then can you quantify if you can like how How much will it improve like for example, like, you know, it used to take Seven months to do this, but now it's like two months, etc. Like do you have any metrics on that? so so we don't have any metrics, but One of the one of the things we set out to do What when I had had recently joined Um, which for me was the start of the journey and the journey was already ongoing by a few other people and one of the wishes was Get to first issued credential in under five minutes Because we used to have a version where that could take up to seven to ten days There's many reasons for that But I'm very happy to sort of see where we ultimately ended up in a much more Standards compliant manner, which also makes the developer experience much easier I think some of the demos you saw Were built by people That have experienced that themselves. I remember a conversation with with john and I don't want to put you on the spot john but I'm saying hey, I had this idea and sort of over the course of a weekend I could come a very long way and sort of implementing all of this stuff. And I was actually thinking With too much level of detail about what I needed to implement versus what the sdk's did in terms of heavy lifting And I think those types of things that that's how we evaluate sort of the ease of use We're continuously looking at improving that I would I would like to make it as as self-service possible in the end. But ultimately it's also digital identity comes with a certain prerequisite of You need to understand how systems work distributed systems where there's many different agents and many different as And sort of they all need to talk to so so You're sitting on the higher end of the spectrum in terms of experience. I think but still we need to make it Very very simple. I think the c-sign demo was a very good example of that Of how you can make it very very simple. And I think we will all win if people don't realize that they're using ssi Amazing. Thank you all one quick question. So a toilet prison pioneer program It wasn't mentioned in the roadmap, but and now I think it's on pause like what's your plan for education programs? Education programs will continue We're currently sort of rethinking that and and part of the Part of the reason for that is we need to migrate our our entire technology stack another part of the reason is also related to The branding so so that was like the traditional prison branding. So we're trying to figure out how do we make this a consistent whole If you enter sort of via hyper ledger sort of how do you get to? A pioneer program, but there will definitely be A new pioneer program and I think it it's actually set to start quite quickly Early next year if I'm if I'm not mistaken. We'll definitely communicate about that Thank you. Thank you so much for your presentation and all your great work any other questions if not, then I think we're in good on time we have We've gained five minutes. So I wanted to thank everybody for For participating today I hope you will participate tomorrow Meaning next week. So so at the same time as this slot We have maintain our calls. So so next week on on Tuesday And then every every two weeks so so If you're interested Join there go to the wiki go to the discord There there's ways to find us Thanks also for for C sign and block trust for for their demos reach out to them if you have questions To them specifically they're very very awesome in in showing What can be done? So we're very grateful that that people are are starting to use the open enterprise agent because it's also those kinds of use cases That learn us the most on sort of like what what are the things that are required to make this a good experience for people to build something Which provides value to their customers? The society at large And that ultimately our our goal um So I'm going to say goodbye And hopefully we see you all next week Or in in the near future and if not, I wish everybody A very good december it's a Good month for for reflection and introspection and then as of january you can start the building Again, hopefully building some awesome ssi technology Thanks everyone Thanks everyone. I'll send some I'll send an email out with the recording and the other links that were covered today and thanks for joining us Bye everyone Thank you. See you. Bye. Bye Thank you