 So, first of all, thank you, everyone. Welcome to the Hyperledger BASU demo. We'll be talking today, I'll probably talk only for 10 or 15 minutes about BASU, the project, where it's at, the feature it has, and the roadmap and all that. So, but really gonna leave a lot of time for questions. So please feel free to drop questions in the Q&A box. I wanna make sure this is, you know, getting the information you want out of this. I won't be doing a technical demo, but we'll at least be talking about the project and giving you a sense of kind of what use cases it's used for and how you can think about it for your own project. So, very much excited to do that. Let's go to the next slide. So, before I guess I talk about the greenhouse, it's probably worth introducing myself. So I'm Grace Hartley. I'm the strategy and operations team within the protocols group at Consensus. So our group was the one who originally submitted BASU to Hyperledger almost two years ago, which is kind of crazy. It's been two years. And my role is a senior business manager. So I'm actually not a software engineer, but I do our query with the team and defining the product strategy and the BASU maintainers themselves. I've been with Consensus for almost three years now. And prior to that was a consultant at KPMG. I also within Hyperledger, I'm involved in sit on the technical steering committee and the diversity, civility and inclusion group. So you can find me definitely around the Hyperledger group. But yeah, well with that, let's talk about BASU. So here's the greenhouse. I always like to start and share this with everyone because I think it gives a little context where BASU sits in the Hyperledger ecosystem. It is one of the DLT projects in that top section. So similar to Fabric or Indy or Aroha, if you're or Satu that you're familiar with them, BASU also performs similar functions there. But now I'm able to talk about BASU in particular. So it's a little different than other projects because it's other DLTs in Hyperledger because it's an Ethereum client. All the other projects are not Ethereum based or all the other DLTs are not Ethereum based. BASU is the only one. So with BASU, it's open source just like all the other Hyperledger projects and Apache 2 license, it's written in Java. And then it also is built for public or private chain use cases which we'll talk about a little more. And that's one of its different chain features. So this is kind of what we're talking about here. We kind of think of BASU as highly unique in the ecosystem because it is the only public chain client. So instead of only being able to run in permission settings, so in a consortium setting, if you've done that or been a part of one of those projects, you could also run a Hyperledger BASU node on Ethereum mainnet and create public chain use cases on top of it, which is really very different than how you're thinking about other projects that you can only run permission networks on. You can see here that we have some of the different features that I guess I can go into. So permissioning, so in the private chain use case, you wanna set up a permission network. The permissioning for Hyperledger BASU is smart contract based and you can manage the network, the permission network by the account level or the at the node level. Next, so secure off chain privacy is the next one. So if you wanna send private transactions within your permission network or consortium, I kind of use both words interchangeably. If you wanna send a private transaction within that permission network, you can do so using the privacy group feature. So privacy groups are basically, I like to think of them as small groups within the permission network where you can send and designate private transactions within a certain group of the network. So instead of, let's say if there are, I don't know, four people in a permission network and there are only two of you who wanna send private transactions and you don't want the other institution know, you would use privacy groups to then send those private transactions. It's similar concept to private channels if you're familiar with that with Fabric. What is kind of cool about privacy groups and privacy generally is that you can add and remove members and still keep the history of the network, of that group itself, which kind of gives a lot of flexibility in different use cases when you don't wanna be constantly creating new privacy groups but you do wanna add new members as the consortium shrinks and grows as needed. Next, so stable and fast finality. So there are a couple of different consensus mechanisms you can use in Hyperledger Basu, of course, proof of work because it is on the Ethereum mainnet but then you can also use different proof of authority consensus mechanisms for the permission network. So for example, IBFT2 is the one that the Basu team developed themselves and led the leadership on developing it with the Enterprise Ethereum Alliance specification and that is known for its stability and finality of transactions. So what's interesting is I actually, one small anecdote is I was talking to Adam Clark yesterday from finality on his use case using Hyperledger Basu and the recordings available was here at the global forum and he said that was really that consensus mechanism, IBFT2 is the one they use on their network and really meets those needs for kind of, it doesn't need a high throughput. So having, but it needs for a settlement risk use case stability and finality and transactions which is what IBFT2 does. The other one is the other consensus mechanism, proof of authority consensus mechanism that Basu has is also CLEAK which is more known for its aliveness rather than stability. But you have lots of choices at the point. You can kind of configure Basu for whatever your requirements are, whether private chain or public chain. And then finally, just deployment. So we are constantly thinking of ways to improve and have different templates for our, for deployment, whether it's on your cloud provider, there are integrations with Prometheus and Grafana and different monitoring tools. And we understand, it's not just about building cool features but making it easy to run integrating with enterprise system. So that's something we really focus on in our development as well. So here are just a few example use cases. When I say I have my first Q and A, so I'll get to you at the end. So then a few example use cases. So it's worth saying that Basu is industry use case agnostic. Think of it, so Basu actually means base or foundation in Japanese. And when you're thinking about it, like building it or using it, that's just what it is. It's a foundation that you can build on top of, but with like all the Ethereum standards and features that go on with that. So it gives you lots of flexibility and choice when you wanna think about your use case and you can build it kind of right on top of it. So here are just a few examples. They're really not complete. They're about I'd say dozens of use cases across different industries including financial services. So here you'll see we have all funds, which is it's a multi-party payment use case. And so they are using Basu for fund management and disbursement use case. Post-Italiana, it has a customer loyalty program and they're a large infrastructure company in Italy. And they have a customer loyalty program where they're using blockchain technology to create kind of a consortium loyalty partner program, which is pretty cool. Blackchain is another one. So they're the Latin American and Caribbean consortium and they've been using Basu actually for years and essentially their alliance is basically creating this Latin American ecosystem all built on including governments and banks and I guess nonprofits are kind of building on top of the blackchain network to use. And the blackchain network is built on Basu, which is pretty cool. Finality as I mentioned already actually, so that's a consortium of financial institutions and they're using blockchain to tokenize assets and also manage settlement risk and wholesale payments issues. So kind of a cool array, there are a few others are also probably worth talking about but kind of giving you some sense of there's a lots of options when you're thinking about and different ways to make Basu fit for your use case. And if anyone has questions on particular industries, I'd be happy to answer that. So just looking at the roadmap, I always like to show, we're constantly building, constantly developing, you have a quarterly release schedule at this point and just wanted to show you kind of what are some of our priorities over the next couple of months, probably through the end of the year. One of course is high availability and disaster recovery. So that will be available in Q3, which is pretty exciting. We're actually working on interledger integration and different ways of creating basic APIs to manage transactions between different DLTs, including fabric, and that's targeted now from the end of this year. And then finally, because we're a main net client, we're always thinking about how do we, or we always have to continuously keep up with the Ethereum main net and the specification and the hard forks that go on with that. So particularly one highly anticipated hard fork is the London hard fork, which is coming up in July, and that will include E1559, which the team is really excited about. But kind of the next phase is then, because we are in Ethereum, we also have worked towards the Ethereum to merge and ensuring that base is compatible with that process as it kind of continues to evolve over the next couple of years, which is pretty cool and pretty exciting. So how can you get started? So here are a couple of really easy ways, and if one of you did any of these three, I would be very excited, but you can go to the documentation site. Our documentation is, I'm told very, very good, and our docs team takes a lot of pride in the work that they do. So that covers tutorials, concepts, how to run a network really kind of across the board, and it's very comprehensive. Second is there's a, and if you go to the documentation site, so you can go to Quick Starts and then set up your private network under the Quick Starts there as one way to get started. And we think that's pretty cool that you don't need to spend a lot of time getting your network configured and start playing with Basu. These three steps really take under 30 minutes, which is pretty cool. Where to find us? So we are on the hashtag Basu channel on Rocket Chat. Would love for any of you all to come introduce yourself, ask more questions, and see kind of the community that we're fostering there. There's also, if you're ready to get started working on Basu, and you're curious kind of about making your own contribution, we have the list of good first issues on JIRA, and also you can look on the documentation site, basu.hyperledger.org, and it gets started that way. And then my final plug, which is really exciting, is that we actually just launched a new Hyperledger Basu's training course, and just this past week as a part of the Global Forum. So really if you want that kind of detailed walkthrough of Basu and how to get started, and video tutorials, and more details around the consensus mechanisms I was talking about earlier, you can find that there, and I'll actually drop the link in the chat. But yeah, and then just wanted to say thank you, and I'll answer the questions now. I'll go look in the Q&A and do the best I can there. And I'll stop sharing my screen and let's see. So the first question looks like it's from Bob, what's different or added in Quorum compared to Basu? Basu is the upstream version of Quorum, if I got it right. Actually no, so both are Ethereum clients, so go Quorum and Hyperledger Basu are Ethereum clients and have features and meet the Enterprise Ethereum Alliance's specification, which defines what is an Ethereum client. But Basu, it's a completely separate code base than Go Quorum. What I will say is that both of them are currently worked on at Consensus, which is where I work, and a big focus is on interoperability of the different features, but there are some kind of key differences between Basu and Go Quorum. Basu, as I mentioned, is Apache 2 licensed, written in Java, runs on Mainnet. Go Quorum is LGPL licensed, written in Go, and you can't run it on Mainnet. So when you're thinking about kind of your requirements, some folks have different requirements there. One thing that you said Basu is upstream version of Quorum, so actually Go, Geth is actually the upstream version of Go Quorum, not Basu, just to be clear. So they do have some differences, but both are Ethereum clients, both have privacy permissioning, have different BFT Consensus Mechanism implementations, and a lot of the work that is in the Ethereum space right now is working on interoperability, but they are actually different, particularly the three things I mentioned before. I hope Bob, let me know if that answered your question. I know we have a few, I'll plan on saying on at least five more minutes. Arnab, how can one get started deploying Basu on Kubernetes, clusters, cross-work setups? I am not our DevOps engineer, so I can't, I'm not the right person to give you detailed steps on how that can work. I can see, I'm gonna just double check if there's, we do have a deploying Hyperledger Basu with Kubernetes reference implementations that I'll drop in the chat right now that I think will probably help get you started at least, but I'm not, there you go. Oh, Bob, great, I'm glad that answered your question. Arnab, let me know if that link is what you're looking for too. Oh, great, thanks for sharing that too, yeah. Any, what other questions are there? I know I moved very quickly. Okay, Bob, we went just a minute. Looks like, okay, if there are no more questions, that's great. I'm dropping in the chat right now the Basu Essentials training course, as well as my email. Feel free to find me via email, LinkedIn, rocket chat, I'm there too. Happy to answer any questions or if you're curious more about getting involved with the Basu team, we'd love to have you and I really appreciate you all joining.