 Interest of time, let's get going. So my name is Kevin O'Donnell, the CTO and co-founder of BTP. We're here today to show you, talk a smidge about our company, just to introduce ourselves and then to talk about what we're doing with Sawtooth and doing for our customers as well. The, so a few slides to start with, nothing that tedious, but first who are we? A few years ago, we founded BTP. The main goal of BTP is to actually bring to commercial practicality, the technologies of distributed ledgers, smart contracts, and information security. To business, not just to provide it and sort of develop and go there, but make it practically usable in an everyday context. Very early on, we chose Sawtooth as one of the principal platforms that we do. Reason for that is actually a few different reasons, but one of them actually had to do with the decent architecture of Sawtooth as it goes through, and then it enabled some of our key focuses, which is that we can bring up multiple collaborative parties, really organizations, and that we could actually build upon that and extend the tools to create better functionality for application developers, which is one of our things. To that end, we sort of put together several different sort of combinations of our products. One of the principal ones is section for blockchain. The interesting thing about that is that that's built on, that includes, I should say, control distributions of hyperledger Sawtooth and hyperledger Bezos built on top of Kubernetes, and with our sort of real core value in a lot of ways is the management and distribution platform of the blockchain, so you can extend out. Notice the dotted line, the applications, that's where the customers come in. You build your own business on top of it, we're really a middleware company. So let's get the head. First thing I really wanna show actually is just kinda how everything works in practice. For that, we're going to go and log into Sexton. Sexton is itself a UI platform, it's not a managed service. You install this software on your own site because distribution is the key. Sure, I've got my right password. One moment. While I deal with demo gods, and give my password to something I know, I've got backwards. So, let me make sure I've got you guys sharing the right things. Good to do, hook in. Oh dear, can I, there we go. Make sure I share the other window. There we go. This is Sexton logged in. Sexton managed multiple Kubernetes clusters for the purpose of delivering Sawtooth and Bezu blockchains. This demo we're primarily concerned with Sawtooth and the first iteration is just a straight, Sawtooth, oops, wrong cluster, sorry. I wanna go into deployments. In the first iteration, we're just doing a plain Sawtooth distribution. Actually, I'll step back one. We provide a number of things and variations on things. This is a vanilla Sawtooth, which we're just gonna go and fire and deploy it. There's some easy to use forms to fill out there. There's also a way for us to actually extensively customize things by adding some custom YAML if everything draws outside of the lines of what we normally do. We deploy that. What this is doing is going out and contacting the Kubernetes cluster. Deploying some Helm charts and installing it. So now we've got a Sawtooth that we're coming up and running the, including the REST API and everything like that. One somewhat interesting thing, which I cruised by there. So if I go back and edit it, the Sawtooth works, this is all based off of Sawtooth 1.2 or our distribution of Sawtooth 1.2. So there's still external transaction processes. In this case, we're actually distributing and putting into the installation an open source transaction processor and therefore transaction family. If you're familiar with Sawtooth, that is made by Consensors, which I think is a target project. If I remember right. And so that's all distributed out and running. Nicely done. What we decided is actually that's a fairly generic solution in terms of Sawtooth. What we then do is actually use their value that we can move a little bit further up the stack and be able to provide better functionality for the users, open up blockchain functionality to a wider audience. And so one of the things we've partnered with a company called Taqian, which creates a number of things. Well, one of the big ones that we really liked out of it is what's called the TFS of the Taqian file system, which is a network distributed file system based on Sawtooth, storing its data in Sawtooth and auditable on Sawtooth. So you get what amounts to the functionality of something that looks like, in terms of functionality, a fused file system that looks like the way you would mount a NetApp filer. And so you can go through snapshots and take snapshots over time and things like that. But everything's actually in the blockchain and therefore you auditable over time. In particular, they are targeting, and we like this as well, the any sort of file data that actually needs to be audited for change and very concerned around hacking. One of the typical circumstances that they come is actually storing of logs where there have been hacking attempts where not only were the systems interfered with, but actually the logs were corrected to hide the fact that they were interfered with. So the initial logging happened with the intruders ended up actually correcting things. And in the case of if those logs are stored on TFS, you have a way to actually go back and see that the logs were actually modified and be able to get back to the original what was the case. The other reason we really like this is actually because it presents blockchain and a lot of the key benefits of blockchain, sort of auditability, immutability and time in probably one of the most common file system interfaces of all time or most ubiquitous interfaces, which is out of a file system. So in order to use and be able to get the benefits of it, you don't need to know any more than how to drag and drop a folder. So let's distribute that. And similarly, it's an example of an application this type built directly on SolTooth. It's only on SolTooth at the moment. And then provided via sextant. So it's switched to something here, it's going to share something else. To sextant, nice and easy, over here. Now, if I go back over to my deployments or actually over to my clusters and I take a look at the TFS demo cluster, which is just a Amazon EKS cluster, nothing fancy about it. I edit this as it goes. This is TFS in particular, which has a lot of, reduces some of the options that we present straight off the bat because TFS really only supports a certain set of things in terms of SolTooth configuration. We redeploy that and let that go. Let that sit for a minute. Now that's going in. One of the things you'll notice is, give it a second. Oops, this is actually also teared down this guy. Nope, not that one. This one's going down. Get my things safe. I'm gonna let that come up in a second. That's, these are, as it comes through, let's actually kick that to improve it. These are not really three different clusters. It's actually the same cluster, duplicated. So let's un-deploy this guy. Let's bring it back in. That should look much better now. One of the interesting things that we provide is actually on a given application for things that we support in Sexton. As you'll notice, we have this extra little gear icon, which will pull up. And this is actually how we go and we connect into Taki on itself, which is, this is actually a command that actually can connect you to the Taki on file system directly. This is via Docker. Normally for a host image, you just wanna pull that up directly in the operating system, rather than going through Docker. Key management, Taki on can maintain encryption on everything in there. Volume, snapshot, et cetera. And so that's a whole management level inside of Taki on. So here, this is volumes. These are caught through. I haven't created any volumes, so that's the problem there. So now, moving in, let's go to the next step. So, presentation, do, do, do, do, do. Then finally, at least for the purposes of this demo, there's more stuff involved in Sexton and BTP land. But we have a very strong partnership with a company called Digital Asset, which you may have heard. One of the things that they produce is a smart contract language called DAML. So DAML is a higher-level workflow-oriented language based on a declarative functional style syntax. Haskell, if you're similar to Haskell, if you're familiar with it. It's also very different from Haskell if you're very familiar with Haskell, but a lot of things going on there. So this is sort of in a kind of a direct replacement for if you're in the Ethereum world for a Solidity. We also actually have DAML on Bezu, but in this case, again, talking about Sawtooth. And that pulls us up more into the smart contract world. So rather than building directly on Sawtooth, you're gonna build your applications in DAML and with those tools and related issues. And so that's very generic. One of the advantages of DAML is that it works cross-platform. So you can go from onto Postgres into Sawtooth into Bezu. We, of course, like everybody to work in Sawtooth just because that gives you the higher level of immutability and long-term history of the contracts and also the bigger collaboration and not necessarily need to trust one centralized party. Let's jump back over to Sections. This time I'm gonna remember to do this. Notice that we control everything as we go through here. Finally, we have DAML in Sawtooth. Give it a second to deploy that, but again, series of things, more restricted information on DAML on Sawtooth. We only support three of the things. If you're familiar with Sawtooth, you're familiar with Poet. We don't support that on DAML. DAML requires a non-forking protocol. And so therefore, we'll just three. But other than that, there's a bunch of different options for tuning the way that DAML actually works, but you throw that out. And similarly, just like the vanilla Sawtooth, the TFS Sawtooth, and any of the other installations we have, we deploy it in exactly the same way. So one of the general things is we take the same strategy on every single thing that we deploy, so we're able to actually extend our always having to do with blockchain-related stuff and supporting tools having to do with blockchains and distributed letter, these other ones that you see that we deploy. Not all of them are actually available in our commercial product. This is our engineering one, which sort of contains everything we do. We have a series of different additions, but they're all meant to support running distributed ledgers in one form or another. The, with that, let's go over to what we're talking about in actual customers, which is a common topic. So recently, and it's just an example for us right now, is we are going to production literally as we speak right now, sort of declared to go last week and should be done by this week, is the Demex Group uses a Demelon Sawtooth deployment underneath their application that marks off their, I think it's their contracts, their actual contracts and issuances for risk products that are based on climate change. And so they mark that off and they're a smart bunch, but they use our platform, our version of Sawtooth and sex and deploying it in, basically wiping out an entire area of work they would have to do on their own, but then using and getting all the benefits of Sawtooth as they go through. Pretty interesting stuff. So that's how we do it on time. Oh, I'm too tired. So just a quick 1,000 mile overview on any of these things, I'm happy to take questions on anything more detailed if you want, but we are at the 22 mark. So hope you found, all found that interesting. Thank you. I don't quite know. Yeah. There we go. Thank you. Thank you for attending. Bye-bye.