 Thank you. Thank you, Brian. Hello, everyone. Welcome. It's quite an exciting day. I hope you will enjoy this. I set myself for a pretty much impossible mission, which is to give you a complete overview of what's going on in Hyperledger land. And so I will start with talking about what's going on with the TSC itself, and then give you a little bit of a test of what's going on in all the different projects, working groups, et cetera. So with that further ado, let's start with the TSC itself. So the work we do is kind of trying to manage all the different projects, all the different activities that are happening from a technical point of view, and give everybody some kind of organization structure. So we have a clear process on how a project goes through different phases of maturity and so on. So we actually have a decision log that we maintain, and when issues come up, they get added to the decision log, obviously. And then we try to solve them and improve the overall organization. And so one important decision we took a year ago is when we Hyperledger started with a fairly small number of projects, we had a technical steering committee with nine people. It became pretty clear that after five years, given the number of projects we had, we needed to have a bigger TSC to have better representation, more diversity. And so we actually changed to 15 seats. And I think it was a very successful transition because we effectively have much more diversity now, both in terms of actual gender, but also in representation of the different projects within Hyperledger. We have a project lifecycle that the project go through. They start in incubation. And then we had this thing called Active Status when project had grown up into active community with clearly defined processes, CI and whatnot. And this term was always confusing. And we actually borrowed from the CNCF, the term graduated instead. It's a fairly small change, but we hope that this will actually clarify what this is about. And so we renamed the Active Status to graduated. And so hopefully this will be clear because it's about the status of the community and how the project behave. And there are plenty of projects in incubation that are very active. So hopefully that will clarify this. We removed the requirement to have a lab sponsor. So Labs is an environment we created several years ago to help provide an area where people could actually experiment with new projects, start building a community maybe around a project that has been going on for a while, but there's not necessarily known publicly. And the idea was the process to go through an approval to create a project is pretty heavy because there's quite a bit of resources invested by Hyperledger into projects. And so having a lab space where the bar to creating a lab is much, much lower and you don't need TSC approval, you just go ahead and create one and you can start working. And there was this notion of sponsor we had put on this, but it seemed to be actually a barrier. This is based on actual feedback we received. So we removed this to lower the barrier to creating labs and bringing more activity to the Hyperledger. And so we've done a bunch of other things like the Hyperledger community is fairly fragmented for historical reason because we're different project that don't necessarily share much in common. And so one of the members submit feedback we got was, well, what can you do to try and break those silos? And so we've tried to look at different activities we could take on, one of which was to actually have people come to the TSC calls and present on the project to make them more visible known to everybody. In terms of the project life cycle, one more change we added recently was a dormant status. There are projects sometimes that want to just take a break. And there's actually the project quilt is going through this right now. This is what prompted this. We added the dormant status, which allows project to basically self declare, okay, we're not going to do anything for the next few months. So consider dormant. It doesn't mean we're going away forever. It just means for the next few months we are not going to do anything. So then we have this, the new activities that we're actually looking at more around we are looking at a badging system which beyond this status for projects, we're looking at something that's finer grained that would give us a better way to measure with the health of different projects. We've been looking at issues related to developer certificate of origin. We're always trying to, there's a trade off being trying to provide adequate protection from an IP point of view. I have talked about the intellectual property here and at the same time, not putting too much burden on the possible contribution, especially by people who are noticeably actively contributing to Hyperledger on a daily basis. And then there's the greenhouse. I'm sure you're familiar with, this is the way we traditionally represented all the different projects within Hyperledger. And this greenhouse, there's a lot of feedback again we got was that it's actually confusing because there's all these different projects. There are actually sometimes dependencies between those projects. There's different relationships that are not surfaced through this. And so we actually have an effort in the way to look into updating the website, changing the greenhouse to something that will be easier to understand for people. And then in parallel to that, we're actually looking at the charter, which has aged. We have evolved quite a bit of the charter, the initial charter, which actually only anticipated to have a single framework being developed. We obviously have a lot more than that today. So we're actually updating the charter. And then a big part of what we do, as I said, is manage the different projects. We are looking at new proposals and then as project mature, they can go through these different phases. A big one is the graduated phase that I just talked about. And I'm happy to say that the Aries project graduated this year. And it's in my opinion, one of the most qualified projects. Interestingly enough, they didn't think so, but as part of the quality report they give to the TSE, we prompted them to say, but why haven't you applied to graduate yet? And they said, well, we didn't know we could qualify for this. We actually kind of pushed them to look into it. And I'm happy to say that they did qualify. Their application went absolutely through very easily. And one of the reason is because a big criteria for graduation is actually the diversity in the community. This is something that often blocks projects that would otherwise qualify. And Aries is the most diverse project within hyperdagement. So let's move on to project updates quickly. So this is the list of graduated projects we have today. So as I was just talking about Aries, so they actually enjoyed over eight different implementations of what they call the Interrupt Profile, version one. They have many deployment of the agent and they have actually agreed on the Profile 2.0 spec which that will provide further interoperability among the clients. In parallel, the Bezu project has been working on the Ethereum improvement proposal 1559 which actually focuses on issues related to a gas usage. And this will actually be part of the release that will be deployed along with the fork that will happen in Ethereum in July and that will make transaction cost more predictable. The Fabric project went through some major revision with one significant event where we actually moved from the long-term support 1.4 branch to the 2.2 branch. So nobody should ever use 1.4 anymore. They should actually switch to the 2.2 branch at the minimum. At the same time, there are more development happening in 2.3 and 2.40 which is starting to be how there was a pre-release recently that always brings more features to make things easier to get on board, et cetera. The Indie project has been known to run, there's an instance of the Indie network running for the Sovereign Foundation, but there are actually two new instances that were deployed and this actually prompted the community to say we should define a deep method called the Indie that would be used by all public Indie networks. The ERA project has been going through some major rewrite as they were initially written, ERA was written in Java and for the version two, they are rewriting it all in Rust and they are going, they are approaching the first table preview release of that. SoTooth, when also through some major reorganization, they actually split SoTooth in many different pieces. There is actually now a library that can be used, extracted from SoTooth itself and used by different blockchain and DLT implementations. They at the same time use the Transact project that we talked about next for transaction processing and the Saber engine that they have in has been externalized to Transact. When it comes to project incubation, we have the Avalon project that has been going through some releases as well. They are actually focusing on taking advantage of new SGX capabilities. The Borough project went through some interesting development around TypeScript code generation that makes it easier for people to deploy contracts, submit transactions and so on. The Cactus project, which has to do with interoperability, is moved to a language-agnostic plugin-based architecture to make it easier to integrate different blockchain into the Cactus framework. The Cattipur project has simplified its connector API also to make it easier to connect different blockchain systems into it and to also move away from a programmable system to more configuration-based system which is more declarative and easier to use. The Cello project is going through a redesign to make it more decentralized and more flexible. And then the Explorer project added support for the latest fabric version. This is the 2.x version as in addition to the 1.x version and they also give more insight into what is going on with the fabric network beyond just the blockchain itself but you can actually access information such as the endorsement policy. The Great project had a civil revision and the latest one is actually bringing new capabilities related to the GS1 product definitions. The Transac project, as I was talking about earlier, has generated pieces of sawtooth. It has actually gone through major evolution that has led to reduction in latency and better performance and it is actually used both by sawtooth and Splinter which is outside of Hyperledger. Finally, the Ursa project which is a cryptographic library had a major release in December and they are going through some major reorganization of the code, I should say. Initially it was based around some projected usage and now that they have a bit more experience with how people really use the library they are reorganizing the library to make it better fitted to how people actually use it. So this is for all the projects but Hyperledger is not limited to those projects. We also have a lot of working groups. So there is an architecture working group which actually went through a quiet phase and as just relaunching with an interoperability discussion I will talk more about next. We have the diversity, civility and inclusion working group that developed a whole bunch of recommendations to be used across Hyperledger. I know that they are meeting still regularly. They have a fairly low attendance. I encourage people if they are inclined and interested in kind of topic to look into it and join. We have the learning material development working group which is led by the amazing Bobby Muscara who has a lot of energy and actually manages to get their group to help people literally on board in Hyperledger find their ways through all the different projects that I'm talking about. And they actually maintain a page which gives you kind of like everything you need to know about what's happening today or this week in Hyperledger. So it's an amazing piece of resource. I encourage you to look into it. The performance and scalability working group also went through a quiet phase and is actually looking into relaunching. They're discussing what they are going to do exactly. And then we have the technical working group in China which really is designed so that there is such an activity around blockchain in China, they felt like they need to have some kind of group where they could get together and talk. They work on many different aspects and it's a great piece of Hyperledger that is worth mentioning. So now I want to talk a little bit more about interprobability specifically. And if you look at the program for this conference you'll see interprobability appears quite a bit. I really think that interprobability is becoming a hot topic in the blockchain space. And it's especially for the kind of blockchain we do which is permission networks. And essentially we are building a lot of islands and from the very early on people started saying, okay, but once we have built all these islands how are we going to connect them? And I can tell you I also work with a lot of standards organization they were always asking me, oh no, should we start a standard? And I was like, wait, it's way too early. We're just still trying to develop the technology give us a chance. But I do think now maybe it's the time for interprobability. And for proof of the interest in this just looking in Hyperledger we have actually three different efforts. There's the cactus project which actually started with two different efforts from Accenture and Fujitsu but we also have two labs that were recently started one from IBM, one by data chain. And so they all take different approaches to that very problem. What are we talking about? Just to give you a very quick intro and again there are full sessions on this topic I encourage you to attend to know more but the three main cases for interprobability in blockchain. Data transfer. This is essentially being able to query some data from one network to another and being able to verify the validity of this data. There is asset exchange. This is imagine you have a on a network you managing an ownership of assets on another you do payments and you want to sell the asset. So you want to basically pair the asset ownership exchange on one network with the payment on the other and you need to make sure that those two transactions either fail or happen together. You can't have one or the other. And then there is asset transfer across networks. This is actually moving an asset from one network to another ensuring obviously that you're not losing the asset in between or you're not creating assets out of in there. So there's all these activities going on and I personally got interested and looked into it and started asking people, so how does that work? How does this compare to this other approach? And it became very quickly clear to me that there was a lot of misunderstanding of what each approach really entailed. And so we started the discussion which is now hosted by the architecture working group which aims at defining the actually developing a document that will give us a comparison of these different approaches. And the idea is that once we are actually developed a common understanding we can then talk about possibly what we could do in terms of collaborations between these different projects. Moving on quickly to hyperledger labs. So hyperledger labs as I said are not under the governance of TSE but they actually are the biggest source of innovation and new work within hyperledger which is why I think it's very important to look into it. There's tremendous amount of activity happening in hyperledger labs and I really invite you to look into it. I give you some numbers here and I tried to get through the list the other day and kind of define big high level categories of where I thought these different projects failed. And you can see, it's a very broad set of topics just to name a few at the very end of my list there. We have two new labs that just got launched recently that actually is Firefly and Fabric Smart Client to name them. And they actually I think take a hyperledger to a completely new set of topics because it's moving up the stack. So far we spend all of time basically working at the framework level at this fairly low level plumbing. And in fact, when you look and talk to people who actually develop applications you realize there's a lot more to it than the blockchain itself. And those efforts are trying to move us up into this land that sits on top of the framework and try to be closer to the business developer and looking into what is going to be going to tech to develop an application, provide APIs that are much higher level. So again, I encourage you to look into this. So the TSC to finish on this I'm trying to look back to my topic in the first place is officially our mission is to define what gets done and how it gets done. Of course, we are trying to be fairly lightweight. We try to live as much freedom as possible to the project all the while giving them a proper structure so they can effectively work and that we have some consistency across the different projects. But so the TSC is very open, we have weekly calls. There are 15 members as I said but we also have 30 or more people join. I invite you to join our call. The project calls are announced and I always post the agenda beforehand. I invite everybody to come in and join us. So there's a mailing list and to finish, I'm out of time, I invite you to get involved. The TSC is not happening out of thin air. We're all members of the technical community everybody who is involved in technical work qualifies to nominate themselves for the election. We will have a new election in the fall and I encourage you to nominate yourself and it's not to at least participate and vote. Thank you very much. Have a good event. Wow. Thank you so much Arnaud. You know, listening to you talk and give these overviews is kind of like wearing a jet pack and hovering over Disneyland and seeing all of the great stuff happening all over Disneyland and O'Fantasyland is being remodeled and there's a new ride over here. It's overwhelming but hopefully it helps give people a sense that there's so much dynamicism to the community and it's so much more than any one project or any one approach. It really is a really diverse ecosystem and so lots of places for folks interested to start climbing in and get engaged. Thank you so much.