 So we've got 15 minutes to really just give you a little bit of a taste about what we've been doing with Sawtooth and how it's been used in real life. Now there's other people on the call like Arun who are very heavily involved in the actual development. I'm co-founder and CEO of BTP, so I'm more involved in terms of really the business development and ensuring of course that we as a company are involved in the right way, in the right organisations of course including Hyperledger, which is who we're representing and by the way delighted to be sponsoring today. So what's our focus and what's our perspective on all this? Well the way we see the world is that business is inherently multi-party and what that ultimately means is it takes two to tango. If it's a supply chain there's many, many more counter parties involved in many cases, but the whole idea of business is about collaboration and the core of collaboration is efficiency and trust. So what we do as a company and this is a plug for BTP is we provide those building blocks to enable multi-party innovation and so what we've created is a product that helps people do that and it's called Sextant and what it ultimately does is simplify the deployment and management of a wide variety of enterprise blockchain infrastructure. So we're going to talk about Sawtooth specifically today but it's broader than that. Shoot, sorry that was my keyboard going nuts. So ultimately if we think of this as a stack, we're involved in management and operations and so what we've done is we've built a set of Kubernetes home charts and if you're familiar with the blockchain automation framework it's very much along the same lines as that. I would say perhaps a little bit more advanced but the whole idea here is that in the context of Hyperledger which we're talking about today, we can actually deploy and manage both Hyperledger Bezu and Hyperledger Sawtooth. So somebody said in the chat they wanted to see this in action so let's go straight to a demo and we'll flip back and forth. So just log me out which any good application should do. So I'm logging in and of course I have done a little bit of background preparation. So let's start by going to, I've got three clusters here. So I'm going to go to the first cluster. When I say cluster I mean Kubernetes cluster and so I'm going to add a deployment and what Sextant does is it allows you to take everything from plain vanilla Hyperledger Bezu or Sawtooth to Damwon Bezu, Damwon Sawtooth and then something called TFS on Sawtooth which we'll come on to in a minute. So let's start with very basic deployment. So what we're going to do here and obviously this is only a 15 minute session. So we'll welcome follow up questions and also we do have a booth so please join us and ask any questions. But essentially this is very much about making life simple for people. You don't need to know a huge amount about Kubernetes or even Sawtooth. I'm just adding in here some image pool secrets. This is kind of essentially permissioning the Kubernetes cluster to actually pull in the right images. By the way we have something called BTP Parallels which is completely free and available on Docker Hub which is our build of Sawtooth which we maintain on behalf of the community. And that's built, tested and maintained by us and available on a long term basis. So if I just click deploy on here, what am I actually going to do? Well I'm actually going to roll out a Sawtooth, small Sawtooth network on this cluster. So if you have a look over here, we should see something quite familiar to everybody. So what I'm showing here is really a sort of bird's eye view of that running Sawtooth cluster. It's come up very quickly because we're using Kubernetes and Kubernetes is kind enough to cache images. But that's not very interesting in and of itself. If we go back to this diagram here, what we really care about are the applications. And so in this sense applications of course in the world of Sawtooth typically means transaction processes. So if I go back to my deployments and I will undeply this, a little bit of safety there just to make sure I don't do that accidentally. Come back to my Sawtooth demo cluster. Now let's just go in and let's edit that deployment. Now I could do this live incidentally, but I'm going to add a custom container. And I'm going to use one that the guys at Target have made available to us. And so essentially anybody that's involved with Sawtooth knows, I would hope that essentially you package up your business logic as a transaction process from the server side, but of course you're engaging with that through the actual gateway. So if I click save on that, and those of you that were paying attention will probably recall, I hope that the last time I did that there were seven nodes in each of those Sawtooth pods. So, in fact, there we are. So now what's happening, what's happening is we have launched a custom TP alongside the original Sawtooth network. And so what's up and running now is is a for no sorted network now loaded with the consent source, not to be confused with consensus processor from Target. So this could be any any any any TP that you've developed yourselves. It doesn't have to be publicly available. This one happens to be on Docker Hub. It can be, you know, on a on any other repo and that's where those image pool secrets come in. So that's deploying and managing Sawtooth. But let's go back to the presentation and let's quickly step through in the interest of time and look at something else we've been doing. So we've been working with a company called Takion. In fact, we met them at Hyperledge Global Forum last year, last in person event I actually attended. And what they've built is a secure file system on Sawtooth. So suspiciously like the last the last diagram I showed you but if we go back to the demo and come out of here. I'm just going to stop this guy. I'm going to deploy Sawtooth. And I'm going to go back to my clusters. And I've got a TFS cluster here. And now I'm going to add TFS on Sawtooth. Now, at this point, no prizes for guessing that this is going to follow a very similar pattern. The only difference here is that otherwise the TFS namespace, that's just the name of the namespace in Kubernetes. Again, I'm going to just accept the defaults. Now we could add a transaction processor here but in fact what we will be doing momentarily is actually pulling in Takion's own transaction processor. So again, I'm going to add these image pool secrets. And yes, a bit of pointing and clicking going on here, but hopefully not too onerous. I am the idiot that makes our software idiot proof. So if I can do it, anybody can do it. So roll this out. Take a look at this. You'll soon see a refresh. And now we're rolling out. Now each of those validator nodes, so four node network, each validator node is now a pod. That's essentially thinking of it as a collection of containers representing that node that's now of size 10 because we've now loaded in three additional components. And these are the TFS attacking on file system components. The only difference between this and the regular sort of deployment is that we've also got admin access to create TFS keys, volumes, snapshots and so on, which is beyond the scope of this demo. That error warning coming up there is because actually the middleware, TFS middleware is still coming up. So again, in the interest of time, I think I've got about four or five minutes left. I'm going to do one more demo. So come out of here. Hopefully this is making it, you know, real for you guys and girls out there so and just what I call it. Okay, it's checking that I know what I'm talking about TFS on sort of was the name of that deployment. That's just a logical name, incidentally. So come back to clusters and our daml clusters. So going back quickly to here. The third, if you like, configuration that we also handle is working with something called daml, which is smart contract language again topic for another day but essentially it's open source. It's been open source now for a couple of years. It's backed by digital assets. Another member of the hybrid family. And so here what we're doing is we're supporting the deployment of the runtime daml environment that will execute their smart contracts. And in this instance, as you can see from this diagram, we're supporting basis or two and a number of alternates alternates. So so these are centralized ledger in the case of QDB and also Amazon Aurora and Postgres, which of course is just a plain old database. And that's because in this in this particular example, what we care about is the use case and what's appropriate and what's not. So if I come back to here, going to add another and everything I'm doing today with daml on sort is I could of course do with Bezu, but and it kind of gets repetitive after a while. But again, all the defaults that are here, including by the way, practical Byzantine fault tolerance is the default. That's the one we recommend tacking or working on something called ABFT asynchronous Byzantine fault tolerance and we're keen to explore other potential consensus algorithms because we're mostly dealing with enterprise with that exclusive with enterprise. We don't want to use a forking protocol. So that means something like part is not something that we're currently looking at. So now if I deploy daml on sort is what's going to happen here. Well, you know, hopefully you'll get the message. It's another deployment saw to this time. However, we're loading in some additional components that are specific to the daml layer. And so you'll start to see a few daml components of the daml RPC sort of thrust API still there. But you know, additional services have been added. And so the point here about engaging with the daml ledger as it's called is whatever the persistence layer whether it's Bezu sort of or whatever. You want the same, the same same interaction through their GRPC mechanism or JSON API. So coming back to just wrap things up. I'm constantly telling I will try and have a quick look at questions. And just give give a flavor of where this is actually being used. And we're big fans of the DEMEX group. Why because they're really helping people address climate change in the sense of building climate resilience into their business models. So that means allowing us a business to hedge against, particularly the effect of extreme weather events. So, yes, it's important to address climate change. We all understand that cop 26 is happening here in the UK in a few months time. That's very important. But along the way, businesses also need to be protected. And, and what we're doing that is of course through insurance. And so the DEMEX group is a spin out from Munich Ray, big re insurance company. And they're using daml on sort of in their example and I'd commend them to you. And also I'd suggest you also if you have time go and look at the DEMEX climate center dot com which is a free resource that they've now put online. Which, which allows you then explore your, your location and see see what's happening in a way of the trends in terms of climate and so forth. So I'll stop the presentation there hopefully that was helpful. And just come back and see if there are any additional questions in the time remaining. So, please be prepared. All right, I'm not sure there is this about 60 seconds left. Thank you, Aaron for sort of picking up on that question. I don't see anything in the Q&A. As I say, we will be here for the duration. We have a, we have a booth. So come talk to us. Please also, if you're still awake, I appreciate it might be late for some of you, please come along to Chiller's talk, which is happening later today. So that's it. 2050 Central European Time, 750 p.m. UK, 230 p.m. New York and 1130 p.m. Pacific. So hopefully you can join us then where Chiller will be talking about the DLT landscape which is something near and dear to our hearts. With that, I'll say thank you very much for attending and look forward to talking to somewhat all of you across the along the way over the next few days.