 Hello, everyone. This is Arno. It's an honor to be here today. I hope you all have a very good time during this event. So I took on upon the task of trying to give you kind of an overview of all the things that have been happening within Hyperledger. And I realized in 20 minutes, this is a real challenge. So bear with me. I'll probably won't be able to touch on every point that I even in my slides, so I encourage you to read the slides as I speak. But, you know, there is a tremendous amount of work that has been happening and I wanted to try and reflect this in my presentation and give you a sense of what you might be able to see and hear about in the coming days. And so I encourage you to, you know, dig into the schedule afterwards and look for additional information and some of the points that I'm going to touch on today. So first to give you a general overview of what the TSC itself does, you know, we actually work for the community trying to improve our processes, trying to help the different projects move forward with the maturation of their project. And so we actually have a decision log that tracks all the issues that come about and the decision that we make. And so one of the first decision that we made that I wanted to highlight was the increase in membership of the technical steering committee itself. It may sound pretty mountain on then but actually it is a representation of the growth of hyper ledger. When we started six years ago now, you know, it was fairly small organization with just a few projects we had nine seats on the technical steering committee. It became very clear that this was not sufficient to represent adequately the whole spread of project that we now have. So we actually increased to 15 seats, and I'm happy to say that it's very clear that this was a successful transition towards a representation that's much broader, both in diversity and gender as well as representation of the different projects and activities happening in hyper ledger. So there are things like, you know, what things we do is, we look at the project life cycle so where different statuses that kind of conveys the where different projects are in terms of maturity of the community and product. And so we have this status for instance, when you go to incubation and then you graduate to active status. And this has been a source of confusion for a lot of people because it didn't seem to convey what we really meant it to convey. So we actually changed this and call it graduated. And hopefully this will make it clear moving forward. We did a whole bunch of other things like, you know, we have these labs that we'll talk more about later, where we require to have a sponsor and it seemed to kind of defeats the point of making it super easy for people to actually stop little labs, little things that they want to experiment and start getting into the hyper ledger community, and build a community. So we really move that requirement that seemed to create a barrier from, you know, actual feedback we've received. And then we've talked a lot about one of the challenges that hyper ledger has been having is, you know, the fact that our community is quite fragmented and we have basically silos with different projects that tend to ignore each other and even though from the very beginning the TSC has been saying, we need more collaboration and trying to find ways to encourage collaboration, we still are quite siloed more than we'd like. And some of these, by the way, come from feedback we also got from the members submit that happened early on. And so we talked about this and one of the things we did is trying to find very practical, you know, actionable item was to invite everybody, every group within the hyper ledger community to come to the TSC and present on what's going on. And this is just another way to expose what's going on and maybe, you know, find the opportunities for collaboration. We also added news, new status to the project life cycle called dormant, which as its name implies, allows projects to, you know, it was a recognition of what can happen with some project in the quill project actually prompted this desk, because they came to us like, you know, we don't expect to be doing any activity for quite a foreseeable future we don't think this project is dead yet. We want to resume it at some point. But so we just want you to know, don't expect any feedback from us or any updates in the coming months. So we created this kind of parking lot type of space. This is just examples of the issues we are looking at. We also looking at badging system that will provide a finer grain mechanism to measure the health of what's going on in the projects. We had several issues related to DCOs. We always try to find the right balance between ensuring that we have, you know, proper coverage when it comes to patent protection IP related issues. And at the same time, not creating extra barriers for contributions. And so there are, you know, practical aspects that we're looking at to try to streamline contributions, especially from people who are not necessarily active in the community on a daily basis. And so we've talked about the greenhouse. One of the issues is people, you know, the greenhouse is getting bigger and bigger. Some of the relationship between the different projects is not represented in the greenhouse. You're all familiar with I'm sure the graphic that's on the website. And so we actually are looking into ways to basically revamp this and at the same time update the charter which mind you is quite out of date. It actually states that we would be developing one blockchain platform. And obviously we have many more. So we need to update the charter to make it accurate. And one of the things we do as I said is look out after the different projects and help them move on the project lifecycle track. And so on that front, we actually graduated the project areas. I find it especially interesting areas is the most qualified project to graduate in my opinion in the sense that one of the key aspect of graduation is to actually have a healthy community, which is quite diverse. And areas by all means is the most diverse project we have in hyperledger. So it was very pleasing to me that, you know, they would come we actually prompted them to actually apply for to graduate. And I'm glad that it's actually happened. So this is the list of graduated projects as we stand today. So there is the areas project that I was just talking about. And as a sign again of the diversity they, they enjoy, you know, they have eight implementations of what they call the areas into your profile. And so they have countless deployment of the agent, and they actually have already work started working on the new version of the profile. So I think this is a great example of various successful project that reach out actually even beyond the hyperledger community because they're there are people outside of hyperledger that already that also implement at the this profile. On another front, the Bezu project. So they've actually been working on the IPM improvement proposal 1559, which is key to solving some of the most annoying feature aspect related to gas, use of gas and on the main net. And so they are looking forward to the fourth that will happen this July and that will this improvement will make some of these issues go away and make transaction cost more predictable. On the fabric side, there was a major shift, which again is a sign of material of this project where we're moving from the long term support being on the one dot X branch which is one dot four in this case to two dot two. And so work is happening on that version 2.3 and 2.2.4 and there is more and more features, making fabric more decentralized and more manageable with things like, you know, allowing to have snapshots that basically makes it faster for new participants to join an existing network and so on. On the Indy side. So Indy has been, you know, well known to be run by the sovereign network sovereign foundation has been running an instance of Indy. There are actually new instances to new one that came about. And it has actually prompted now an effort to create a deep method that would be used for all the Indy public networks. Iroha is working towards their version 2, which is rewritten in Rust. Iroha was initially written in Java. And so they're actually rewriting everything in Rust. And they're getting close to a first table preview reads. So Tooth has been going through some major reorganization. First day where they also went through a rewrite process where everything is rewritten in Rust. And they basically split So Tooth in different components. And now So Tooth for the most part is comes in the shape of the library that can be used by different blockchain and different pieces it uses transact for its transaction engine and the saber transaction mechanism is actually moved out into transact itself. So moving on to other projects that are actually incubation. We have Avalon. Avalon is actually moving along creating new releases where they're taking advantage of some of the progress made in the SGX world. The Borough project has had some very interesting new development where they are moving away from people writing code directly, but instead having a code generation mechanism that facilitates deployment of contracts and mission of transaction and so on. So this is actually a very interesting development. The Cactus project is moving towards a reorganization of the architecture so that based on a plugin architecture, they can make it easier to integrate other blockchain network into the system. The Caliper project has also gone through simplification of the platform connectors so that it's also easier to incorporate different networks. The Chillow project itself is being re-architectured to be more decentralized and more flexible. The Explorer project has been upgraded to support the latest version of Fabric in addition to the 1x version and it gives more insight into what's going on in the network beyond what's actually on the blockchain but also things like the endorsement policy. The Great project is moving along. They are working on a new release where they actually have a GS1 compatible product definition and they are working on the identity system features as well. Transact. Transact again is like a transaction engine and so they've been working on improvements both in latency and performance and it is actually now as I was saying earlier used by Soto as well as Plinter. Versa which is cryptographic library so they had a major release in December and they are actually working through some reorg because initially it was designed based on some expected usage and now we still months behind the initial release. They can actually look at how people actually use it and try to make adjustment to make it more suitable for how people effectively use it. Final slide and so this is for the projects and I wanted to give you also an update on what's going on in different working groups which is also an element of what Hyperledger the technical community is about. So the architecture working group was a bit in on a pause and is actually resuming activity around interoperability and I'll talk more about this later next. In terms of the diversity, civility and inclusion we still working groups in the works they have actually produced a whole set of recommendation and they're still meeting on a regular basis. They are you know they could use a little bit more participation. And if you are interested in this topic I invite you to look into it and see if you can join the meetings. The learning material development led by the amazing Bobby Muscada has been very active to literally you know help people come on board and find their way through the Hyperledger community and they actually maintain a page that gives you all you need to know about what's going on in Hyperledger. So this is an amazing piece of information that resource that's available to you are invited to look into. The performance and scalability working group also went a bit of a pause and they are just relaunching figuring out what they should do next. And then there's the technical working group of China which is developed credit because they have very active community in China, and they have been looking after them by creating this working group to that they can talk about you know Hyperledger related issues. Finally, I wanted to highlight what I see you know stepping back a little bit from what everything that's going on. You know, one thing that is very noticeable to me is the fact that into ruby is becoming a key topic. You know, especially in the world of permission network, it's been very clear for a long time that well we're creating a lot of islands, and the next big question is going to be like well how do I connect all these islands right. And so there are people who started from the very beginning to say well we need to fix interoperability but quite frankly, you know, I had a lot for standards organization say I'll know should we create a standards for interoperability of networks and I was like, this is just way too soon please come back in a few years. We are so busy trying to develop the technology. We have no time, you know, no cycle to think about interoperability how they're going to interact with one another. So this time I think is now. It's definitely happening. So we actually have three different efforts happening in April later now. There is the cactus project that's been going on for quite a while that was actually initiated by two different efforts that came together. We have now two different labs that were created in the last few months literally one, you know, initiated by IBM and other one by Tete Shen, they all take different approaches to this, you know, big problem and, you know, I think it's interesting to see that all this is happening and showing like there's a clear interest in trying to tackle this, this problem. So just at a very high level I want to give you a sense of the things that they are trying to solve, which I think is very critical. There are three main cases for interoperability. The first one is the transfer is basically trying to, you know, retrieve value from one network to another, in a way where you can actually validate that this data is the real thing. And then there is asset exchange where you actually want to be able to do two transactions one on each network so you can have a payment on one side and an asset transfer and another for instance, and you want to make sure that they both succeed or both fail. And then there is the asset transfer itself where you're actually moving the asset from one network to another and you need to ensure that this is happening without losing the asset in between or creating some assets out of thin air. And so, given the state, and all this activity happening, I have to say, even personally, I started getting confused about, you know, people trying to understand what's going on and hearing claims and say, Well, our system is different because we do this and the other we do that too. And I say, guys, we need to get together and get a real understanding of what these solutions are all about what the differences are between these different approaches. And so we started a discussion which is taking place in the architecture working group to basically understand, develop a common understanding on all these different approaches, looking at different aspects of them with the goal that, you know, once we have a common understanding, maybe we can actually identify areas of collaborations where I could lead to development of some shared components. Then I wanted to give a glimpse of what's going on in the labs. So the labs we created the labs because we didn't have, you know, the tool for to create an actual project you have to get TSE approval there's a fairly elaborated process which is pretty heavy. And there were projects that didn't seem to be quite ready for a project, but it would have been a shame to completely shut them off. And so we created lab as a space where the community can create areas where they can work, get exposure, get visibility for their project and create more communities so that maybe they can transition to a project later on. And so this is a very active space. There are many different labs that exist, we have new ones coming in all the time, some labs eventually transition to a full on project, others are eventually merging into an existing project. It doesn't matter. To me this is a lot of the future of hyperledger is happening in the labs today. So it's very interesting to look at what's going on. And so there are too many of them for me to side, but I listed some of the topics that I see being touched on. So there's some of relapse some are very different. And there are different dimensions and ways to split this. It's very clear to me that there's a lot happening and it'd be a shame to not look into this. You know, just to name one, the very last lab that we have heard about and that I just came about, I should say, our firefly and the fabric smart client, which I think is the idea of yet another space in which I expect hyperledger to work in the foreseeable future because it's basically taking up, you know, a level up the stack. We've been primarily focusing on the low level blockchain layer and these these these efforts look into at the higher level, you know, what does it take to actually create an application, a blockchain application. There is a lot more to it than what is provided by the low level framework. And so I'm looking forward to see what's going to come out of this project, but I think this is going to be very important. And just to end, I want to give a plug to the TSC itself. You know, Jerry speaking, the TSC is shorter to to define, you know, what gets done to decide what gets done and how it gets done. It's a bit, you know, more subtle than that. I don't think the TSC has that much power. We actually leave a lot to the projects themselves, but we try to provide some common, you know, infrastructure and organization processes to streamline as much as possible to work and try not to get in the way too much, but help the community to grow. But so they, you know, it's a very open setting, even though they are officially 15 members, anybody can join. We often have 30 or more people attend the call and I invite you to look into it yourself. And then to finish, we have the TSC doesn't happen out of thin air itself, right. We are all active contributor to Hyperledger, one of the other project. And, you know, there is an election happening in the fall every year. So I invite you to consider running the more the merrier. And, you know, if you at least you don't want to nominate yourself, please do consider working on, I mean, consider voting in the process because that's very important. We want to have as many people vote as possible. So with that said, thank you very much. I hope this gives you a taste of what's coming up during this week. And I invite you to dig into any of these topics that might be of interest to you. Thank you Arnaud. There's an amazing sweep of all of the activity happening across Hyperledger. Sometimes it can feel very chaotic and feel very, very hard to stay on top of. I sometimes compare what we do in the technical steering committee as being less like an orchestrator and more like one of those traffic cops who stands in the middle of, you know, a gigantic traffic circle, trying to like just hope that they can steer traffic in the right direction. But somehow it works. Somehow somehow we're able to like help guide these communities to shipping product and working together, and it's a little bit messy sometimes but I think that's that's true for every open source project. And it's really awesome. Thank you for the work that you do to support that. Thank you.