 Thank you very much to Hyperledger. Thank you, Thomas, for hosting this. I also want to call out David Berger, who's joining the webinar from our team. David Berger, based in Las Vegas, is our chief scientist and the originator of many of our core technologies. What we're going to do today through this webinar is present Integra's vision for universal document automation using Hyperledger technology. And that vision is to rethink the way documents and contracts move in the world, simplifying and streamlining it very much in the way that global universal credit card payment systems now operate, cell phone networks, and even the internet and the worldwide web itself. And so we're going to draw those comparisons through this webinar, walk you through the concepts, show you the technology in action, explain the deployment, and then give you an overview of our tech stack and take questions. So jumping right into that, most people when they think about blockchain technology are focused on payments, the sort of the miracle of Bitcoin and what that gave rise to in the world. And Bitcoin, of course, is just a data network and distributed ledger, unique numbers. But we use universal systems of unique numbers that are not blockchain based. And we use them in ways that have absolutely transformed the way we live. You think about cell phones as an example. Obviously, these are very sophisticated devices. But at the heart of a cell phone's connection to the world is a SIM card. It's a unique identity, a unique number for that phone that distinguishes each phone from every other one in the world and enables ultimately those connections, those nearly infinite connections among anyone that has one. You can see some of the stats there, seven billion phones in use, eight trillion text messages and obviously a huge market. Another even more universal example probably is credit cards, bank cards, ATM cards. The world wasn't always this way, right? We used to use cash for things or checks even. The notion of universally accepted Visa cards, American Express cards, Master Cards, to buy a cup of coffee or to buy services, subscriptions, you name it. I mean, that's a relatively new phenomenon. But if you think about what's actually happening in credit card networks, again, not blockchain, but it's a unique number and it's a unique proof of existence typically via chip and that plastic card. Amazing to think that unique numbers and proof of unique existence can enable global, seamless, on-demand payments. Final example, I use the image of the Hyperledger website, the internet, right? Again, for those of you who are my age and above, you certainly remember the time when there was no internet, there was no email. The foundation of that universal connectivity and connection and data transfer, of course, is unique addresses, IP addresses, numbers. The fact that we can uniquely connect to these numbers around the world and each number, of course, each through DNS and domain name registry confirms identity, allows this trusted transfer of information, incredibly efficient, change the world, obviously. But that brings us to contracts. Almost all value in the world, hundreds of trillions of dollars, euros, yen, one, moves via contract. It could be as simple as when you press a button on your screen to accept cookies, you're accepting the contract terms of that website. It could be as elaborate or as dramatic as $100 billion M&A transaction. Contracts define ownership and the transfer of value. In the blockchain era, most focus has been on how to automate those contracts, how to digitize them, smart contracts, how to put them on blockchain. But our insight is that we have a current world where pieces of paper, PDFs, digital documents that are not authenticated, that are not identified are controlling all the value in the world, or virtually all the value in the world, yet there's no universal numbering system, no proof of existence or authentication. So if we think back to my cell phone example or the website example IP addresses or credit cards, there's clear precedent that adding unique numbers and authentication to universally use things creates incredible transformative efficiency. Integra is just following that pattern. Best examples again, cell phones, credit cards, and the internet. What we're gonna show you through the rest of this presentation is how we can rethink a document in a way that makes it feel like a cell phone, which may seem like a crazy example, but I think it'll make sense as we step through it. And to walk you through exactly how that works and how that actually is similar and how that can really change the world, I'm gonna turn this over to Mike Renau to walk you through the demonstration. Mike, take it away. Thanks, David. I'm getting my screen shot and all right, good. So for cell phones to receive calls and messages, the cell phone network or cellular network needs to know where to route the call or message. The cell phone has the SIM card like David had mentioned with the unique identity and the identity is linked to the phone number. That way, when the cellular phone network receives a call to the phone number, it can route the call to the cell phone with that SIM card. To make a document behave the same way, we need to give it a unique number just like the SIM card. Adding this ID, we record that identification of the integral ID as we call it for the unique number on the integral ledger blockchain. Because documents are purely digital with no hardware-based security like a chip or a SIM card, one additional step should be performed which is also registering the hash or digital fingerprint of the document along with that unique integral ID. Together, those two items confirm the uniqueness of the document and the integral ID becomes the address for that document similar to the SIM card on the cell phone for the unique address. So a document that's registered on the integral ledger blockchain with an integral ID and a hash is what we call a smart document. This is different from a smart contract in that a smart contract is code on the blockchain itself, whereas a smart document is a normal document whose uniqueness and authenticity is recorded on the integral ledger blockchain. So I'm gonna go into this now and show you guys, sorry, this is where the slides are supposed to be shown while I was going through those. Anyway, I'm gonna go through an example now of how we basically register documents onto or create a smart document with the unique identifier. So first step here, we're using a tool called the integral workbench, which is software that makes it easy for us to show what we're doing without being in a production environment where in a production environment, this would be layered on top of additional software in what we consider a blockchain authentication layer. So the first step I'm gonna do here to create a document is I dragged and dropped a basic PDF document, as you can see here into this page, which is our create page on the integral workbench. And the first few steps are, I'm gonna add some metadata to it, which will be stored in the document and not on the blockchain. Go ahead and do today, description here. It allows you to also add additional fields or values for whatever you may need. If it's a contract or a mortgage, these could be fields that are pertinent to the contract itself. And you'll see why they become important here in just a little bit. The other thing that we allow is standardized codes, such as chance relaying, Sally, and what these allow are standardized metadata to be put into the smart document as well. So I'll do manslaughter, I guess that's a good one. And we'll search on it and select one and you'll see it puts in the unique code for Sally, along with the term voluntary manslaughter. So I'm gonna go ahead and create this smart document. And what this is doing is it's taking that information that is in these fields and it's creating a document that's registered with that unique identifier on the integral blockchain. And you'll see now we have this QR code that was not there. I'm gonna make really quickly, open it up in Adobe Acrobat so we can show you guys what has been, what's happened to the document. You'll see it's the same document as before, but when we come in here and we look at the metadata or the custom properties, you'll see that we now have an integral ID. That is the unique number that's similar to the credit card number or the SIM card number. Also in here, it stores all the other information that we had stored from that form. This would typically be generated in a contract management system or any other way that companies typically generate documents. It'll embed the information within the document and not on the blockchain. A very important distinguishing factor. So I'm gonna go ahead and click on this QR code. You can also scan it with a cell phone. And what this is gonna do is it's gonna take us to a page where we can verify that this document was registered on the integral blockchain along with the ability to check that it has not been modified or tampered with. So here is the integral ID as we saw back here in the custom metadata. So that's consistent. We've got that. That's a good start. All right, we've also got the document hash that can be seen here. And that's of the document, the final document. You'll see the transaction ID, which I'm gonna go ahead and click on right now. And this is gonna open up our version of Blockchain Explorer, which is a fork of Hyperledger's Blockchain Explorer. So I'll come down here in the transaction. Nope, wrong click. And I'm gonna go into the actual transaction and show you the data that's written. So you'll see here that we have the integral ID, the same one that is the unique number that I showed you in Acrobat and on the verified page. Also, we have the transaction ID, which was just linked to and clicked on. So this points to this transaction within a block on our Blockchain and also the value. So there's no proprietary or private information stored on the Blockchain is our company policy and it's never a good standard practice to put that type of information on the Blockchain. Anyway, so now I'm gonna come back here and the second step into this is we need to verify that the document has not changed since it was created. One other thing I wanted to show you is you'll see here that when we created that document, we appended an underscore smart document to the original file name. It's another indicator that this is a smart document and not just a regular document. So we're calculating the hash of the file locally and it's making a call to the Blockchain to check that that identifier and that hash are unique and matching what were originally generated when the contract was created or document created. So here you'll see that it was indeed an exact match of the document that is registered with our Blockchain. So another thing I wanted to show you here is you'll see that this is also the same metadata. It was extracted from the document. It was not pulled from the Blockchain as I showed you that none of it's stored on the Blockchain. So it's extracted from the document itself once it's been approved has authentic and untampered with. So you'll see now it's in standardized JSON format. So this can be automated into other systems. It can be mapped into various other pieces of software and we'll show you how you do that here in a little bit. So now the, let's see. The last thing I wanted to show you here we showed the verification. So I'm gonna go ahead and kind of sidestep this and I don't have the ability to do it live but I've got a video of me associating now that this document, the key part here is the document has been registered on our network just like a cell phone with a SIM card. It's been registered on the integral Blockchain. So now it can be communicated with. So what I'm gonna do is I'm gonna go back and show you a video of how this QR code here can be scanned with one of the apps that we have which is the Integra switch board and portfolio and that will allow communication, messaging and other things. So we're gonna go ahead and show you how easy it is to associate one of these documents with our portfolio which was previously called wallets. You have to bear with me. So we're gonna scan the QR code there and it's going out and it's basically allowing me to create a meaningful name for the document in my own personal wallet. So this is not gonna be stored anywhere but on my personal device similar to the switchboard which is more for companies registration of documents. So once you've added it, once you scan the QR code you'll see that the document shows up under your documents section and you'll see how there's a slight delay there for the creation ID or for creation date Integra ID, transaction and hash that's because it's actually checking the blockchain for those values. The last thing you can do is now you can share it with friends and colleagues or counterparties for the document and what this will allow is once there's a connection established, it's a peer to peer and encrypted connection for document messaging for attaching files to that for communicating with the document similar to the way a cell phone does it. So I'm gonna go ahead and show you the next slide. Sorry, this one, this is basically an example of how you would communicate with like a document messaging similar to a cell phone messaging. And so I'll show you a quick video of that once it's in your wallet or portfolio, excuse me you'll see that we can associate various other documents with it, we actually can message it and you'll see that there's a slight delay once we send the message because it's going out to the blockchain to figure out where that document resides like communicating with another cellular device it's gotta go check the cellular network to see where that message or call should be delivered. So basically the Integra switchboard which is the enterprise version of our portfolio is software that'll let you connect the documents messaging capabilities to other software applications at the enterprise level. And this is where the heart of universal document automation will be enabled. The switchboard will allow configuration as you see here on this slide of various third-party applications and it'll allow routing. So the switchboard is exactly what it sounds like. It's a switchboard, it's a directory the phone directory of all the documents or Integra IDs for documents within the organization. Every time a registered document with Integra ledger the Integra ID is added to the switchboard to make it aware of that document and will allow for data routing, automation, mapping to other parties, et cetera. So also one thing I forgot to mention is in the switchboard it'll allow configuration of other software. Any OAuth, Exchange, Dropbox, DocuSign all these on the right side it'll allow for automation to be triggered within those. It doesn't matter what software we're using to store or manage the documents the switchboard will basically route them to that software and the counterparties or people on both ends of documents can have different softwares. It's not an issue. We're enabling universal document automation between organizations. With that, I think I got everything I'd like to pass it back to David. You're on mute David. What we're doing here is we're establishing a data channel. So you've got the party on one side which could be using our software, Integra portfolio or Integra switchboard or they could have custom built that into their existing software. And then you have the other party on the other side of this which could be a company, a vendor, a client, anyone really, anyone on the other side of the contract implementing the same Integra enabled software. And so you have identity on one side, identity on the other side and the identity of the confirmed identity of the document that connects them. So the magic here is simply three numbers, blockchain authenticated on Integra that establish that unique connection peer to peer party to party embedded in that is the reference to the contract. What this does, I mean, it's a very simple idea. I mean, it's, but profound in its impact. What it means is that rather than having to use all sorts of disparate systems, email, text messaging, custom software integration, cloud and intermediaries to do data transformations, expensive, with security risks, complexity. I mean, this is part of the reason our world defaults to email, as the universal way to transmit documents information is because every other way is so messy. What we're showing here or demonstrating is that using simple identifiers and the ability to authenticate the provenance of a document or contract enables a nearly perfectly connected data channel relative to that. And through that data channel, you can connect software on either side. And so you can move invoices, you can move legal notices, purchase orders, almost anything that at some point we think even payments can be routed using this unique peer to peer data channel that we're creating. It's universally applicable. We think it fits the pattern that I mentioned previously of cell phones, credit cards and IP addresses. Very simple idea, add unique numbers, add proof of existence, provenance, authenticity. And you enjoy the same sort of universal data interactions that we enjoy with these other technologies that we're all used to every day. I'm gonna kick it back to Mike quickly to talk about how this is implemented. It's startlingly simple. I'll keep control of this, Mike, so you can just talk over it. Okay. Yeah, I'm gonna go into a few little technical details for those people who are here to hear about Hyperledger, which is great. So basically all our infrastructure currently is on Hyperledger Fabric 2.1. We're able to run nodes on prem for various companies. And once they're behind the firewall, we're allowing them to access the APIs. There's two sets of APIs, which we'll get to on the next slide that will allow the endpoints to be in their firewall. We only have to expose two ports to the outside world currently, which is 7051 and 7050. So this will allow the entire node and API calls to reside on the infrastructure of the organization hosting that node and nothing will be open to the outside world. Eventually, this will all move to in browser, which David Berger will talk to here shortly. And like we talked about earlier, none of this information except the hashes and identifiers, which we don't control the identifiers. The organization generates them and stores them. None of that information is stored on the blockchain. So everything, we don't compromise data privacy and or security. You can go to the next slide, David. So all of this is accomplished with relative ease with basically chain code APIs, which interact with the blockchain themselves, which are on the left-hand side. And those are basically registering identities, integral IDs and hashes, and then various ways to look them up. And this will change over time, but right now that's the way they're done. And then the other component that we created is a dockerized container where organizations can host it on their internal sites where they don't need to know the inner workings of PDFs, word documents and how to store metadata or extract metadata or any of those complicated operations or to query the blockchain for that. Basically they can call these simple endpoints which I consider helper APIs. So you don't have to do deep research on how the inner workings of a PDF document work. That might just to interject here. The emphasizing the simplicity of this in a world where almost all software is trying to solve complexity with more complexity, our insight is on the left-hand side, you register an identity, you register proof of existence, record the hash. You can then query it and get that identity and check it. That's the identity piece of it. And on the right-hand side, for those helper API calls, those are just simple functions to manipulate the documents, to inject the identity, add the QR code, simple stuff and register it on the blockchain. Yeah, and as Mike mentioned, like all of this stays on your infrastructure. There was a question in the chat about where the documents stored. The documents stay where they are now. All we're suggesting is that software should become aware that registered documents exist within the system. But fundamentally, the documents stay in their existing applications, in their existing storage. All we're doing is writing that proof of existence and identity to Integra, which then enables all this other functionality, much in the way, again, that universal SIM cards, credit card numbers, IP addresses, universalizes data transfer. I'll move to the next slide. Yeah, and through two of our applications, they allow basically the ability to track and have associated documents and communication between these documents occur seamlessly. And with the Integra switchboard, it'll allow organizations quickly and easily to configure to their existing software needs or platform. And it prevents organizations from having to have the exact same software for automation to occur. Yes, very much like a, you know, back to the credit card, you know, credit card example, the act of possessing a credit card, I mean, fundamentally, you just, you have a piece of plastic, right? It's inert for what it is. It doesn't do anything. And so you need to have enabling software, say, in a point of sale system, you know, that's able to process that number and transmit it to a bank or someone on the other side. So what we've done with Integra portfolio and Integra switchboard is create some out of the box enabling software, you know, to make it easier for organizations to connect their existing systems, you know, to this document identity system, you know, to facilitate this seamless peer-to-peer, you know, data connection scheme. So that's what that is. It's not necessary to use Integra portfolio or Integra switchboard. Everything can be done custom using those straightforward APIs that we listed before. But again, we have the software just to make it easier out of the box for organizations to add this functionality to their existing software. That's part of what's amazing about this. Most contract automation or document automation is specific to an individual organization. You have to buy the software, you have to configure it. It's complicated, it's expensive, you know, and furthermore, it doesn't typically allow you to seamlessly interact with anyone else outside of the organization. This is a completely different way of thinking about it. Again, it's about identity, you know, as the way to connect organizations and create the potential for automation, you know, rather than creating complex intermediary software, you have to do the same thing, you know, in a traditional cloud type of technology. David, I wanted to say one more thing and then I'll pass it back to you. We've had integrations with existing software that have taken a matter of hours to actually calculate hashes right to the blockchain and check those hashes. So it's not, we're not saying overhaul software, it's very easy to implement. And that's all I need to say. Thanks. So for the final segment of this, I wanted to bring it back to David Berger, who, you know, originated many of these ideas and many of these concepts. The company launched Integra in 2017 and David Berger there was with me at the beginning thinking through these technology patterns. I'd like him to just talk through our technology stack, which is completely hyperledger centric. David, take it away. Great. So Mike talked about the current system using hyperledger 2.1 and we're not fundamentally changing the way we're doing, we're adding a lot of layers underneath. A lot of them actually apply to the IT people and the programmers dealing with it. So fundamentally, things don't change, there's just kind of a level of improvement. So Hyperledger has a project called Firefly and Firefly was written by the folks at Collido and contributed and it creates an infrastructure of plumbing to make a lot of this stuff easier. So you have a hyperledger super node that provides a lot of functionality, including connection to, you can use Ethereum, but there's out of the box support for using hyperledger fabric, which we'll still be using, although we're going to bump to 2.4 in the next release, the current release. And the guys who wrote the software at Collido actually have a software service hosting service, which we'll be switching over to. And I was able to do a beta where I spun up a network on Collido and in under an hour were able to hit our APIs. The other thing that Firefly provides is a much easier programming model. So the API Mike showed the API layer is a traditional software as a service API written in node and it's using the Hyperledger SDK that's out there, which is pretty easy to use. You can write in JavaScript or Java or Go rather than having to hit a solidity, the more complicated languages from Ethereum, but there's still a layer where you have to hit the SDKs and then it talks to the chain code, the code that's sitting in the ledger. One of the really nice things that Firefly and Collido have provided was a really nice API where the middleware just, it doesn't require you to write specific, I'm sorry, it doesn't require you to write specific code for everything you're going to do. There's one nice API call where you basically say, execute this piece of code or a chain code API Mike showed and not have to write one for everyone. Guys, just if it's not clear, if you're not a programmer, put the snooze button on. This is really the ultra geeky and technical stuff. Now, one other thing we're layering in is you'll notice we didn't really talk about digitally signing things or and you kind of might wonder why Aries is up there. So Mike mentioned that a smart contract is a PDF where you're recording the hash and an ID, the proof of existence up on the ledger and storing the metadata within the PDF. There's some more under the hood stuff that you're able to do, including storing signing data. Mike mentioned in general, you can store metadata. Well, one of the pieces of metadata you can store is a self-sovereign identity and non-cred. So if you don't know what a non-creds or go and read the hyper ledger documentation, they're really cool. And you'll notice that a non-creds itself became a hyper ledger standard recently. So we actually will allow you to sign a document but not in the Adobe fashion, which is expensive but in a much easier way and use, embed the non-credentials in the document itself. And to get super geeky where almost no one will care about what I'm about to say but I'll say it anyway, we're doing something really interesting where the DID of the document resolves to instead of a location of a file somewhere up on the net actually refers to the proof within the document itself which is something that we're doing that's really cool. Anyway, one other, the last cool thing I'll mention is that most people are using the Aries with ND which is the hyper ledger purpose built blockchain for identity, there is mention out there you could potentially use fabric but no one really is except we will be. So we have functioning betas right now of a blockchain where we're using the integral ledger to back Aries so you can do a non-credentials there. So basically that's just some of the stuff I care about. It will all be coming in the next release somewhere in the future although it doesn't really fundamentally change anything David or Mike talked about. So that's it for me. Thanks, David. So we've been working on this project like I said for since 2017 I think that makes this the seventh year or something. This is a long, long live project. Some of you who know us know that we also found the global legal blockchain consortium with about 350 members around the world. We're also the founder of the global legal hackathon which is the largest legal innovation event in the world involved about 20,000 people in 75 countries. And so we've really worked to build global ecosystem and consensus around the use of this, what we think of as brain dead simple technology pattern that again, just follows other precedents. But again, we've been working on this for six, seven years. We have dozens of global organizations in some stage of testing or deployment for this. One of the questions in the comments. We see this as much as it's a technology innovation and we think a great one with kind of the critical hyperledger components, which has been fantastic for us. But almost more than that, it's a social phenomenon. Very much like Bitcoin in the early years where like what's Bitcoin, what's blockchain? There's stories of people trying to buy, I guess the first pizza that was purchased for, I forget, 10,000 Bitcoin or something. In the early days, why does anyone care about putting a number on a document? You know, a question I commonly get is, what does it do? The, yeah. And if you spin back a couple of decades and think about cell phones, credit cards, ATM, so on and so forth, these things weren't universal. And today we just assume they're just part of the fabric of life. You can get online and connect to anything instantly. You can call anyone in the world. You can go anywhere in the world and get a phone call. We assume it, it almost feels like it's always been that way. But think about the profound transformation from that universal connectivity, again, all based on systems of identity, really. I mean, yes, there's a lot of fancy enabling technology. We have fancy enabling technology, but at the heart of it, it's just identity. And the technology that specializes in identity is blockchain. We're using that, as we said, to simulate in a certain way what a SIM card does with a cell phone and applying that to documents. Simple idea, as we get more and more adoption, hopefully this will become universal and hopefully the day will come when we can interact with contracts, documents, related payments, automations, just as seamlessly, just as easily as we currently do with those other technologies. Having concluded with that, I'd like to invite any of you that are interested in working with us, and that could be individually or as your organization. We'd love to talk to you. Our contact information is on the slide here. As I mentioned, we work with a lot of global scale organizations. And so there is ample room for collaborations. And again, we do this worldwide. So wherever you're located, we'd love to meet you. We'd love to work with you. Come on, let's back to you. Right, thank you so much, David, David and Mike. So we do have one hand raised. So it's Arun and Arun, I will unmute you now. So feel free to talk and ask your questions. And then we do have some more questions in the Q&A. And I think we can get to those as well. So Arun, the floor is yours. Yeah, thank you, everyone. That was a really nice presentation. Really overrun by the way you guys have shown and really see the importance of how a document is. I mean, how we can, doc management is done. We have seen multiple places, but this seems to be a very good platform. I just have one question. Is this open sourced? I mean, like multiple lists of this hyperledger thing that all open source, we can go ahead and contribute. So whatever you have done, is it open sourced or is it like you have restricted the contribution? Since you said that you are accepting, you are willing to work with people. So how are you taking it ahead? So up to, and David Berger, you can jump in a second. I'll answer it broadly. We're using obviously open source technology in it. Up to this point to get to a sufficient level of maturity and functionality that we could, in fact, this is the very first quasi technical webinar I think we've ever done. We've done some other specific talks on parts of the technology, but we've never presented it in this holistic fashion. It's our view that absolutely this will be fully open sourced for development, addition, so on and so forth. Underneath it is the integral ledger blockchain, which is fee per transaction. But in terms of all the technologies around it from wallet software, for example, helper apps, I mean, there's a reason. We found the Global Legal Blockchain Consortium and the Global Legal Hackathon and interact with so many developers and innovators around the world. And that's to collaborate, learn, develop. As we go forward, we'll be much more explicit about kind of the approach to open source development, contributions to the project, that sort of thing. Up to this point, it has not been open sourced in that traditional sense. Hopefully that answers your question. I would reach out directly to me or David Bergeron if you wanna learn more. Definitely. My one addition is that in the spirit of being brutally simple and with some of the advancements in the libraries and stuff, if you ask chat GPT to write the backend system that we showed, it could knock it out very quickly and it would be close. This is not about, we're not a technology company although we have some really cool technology. We're a network services company and we'd absolutely, we have shared in technical demos everything that we're doing. Any competent blockchain programmer wouldn't even really like ask. They would just go, wow, I hadn't thought about that. Okay, thank you for that answers. Yeah, thank you for your question, Arun. And thank you, David and David for answering. So we do have a couple of more questions in the Q&A box. Would you like to take them one by one? Yeah, so I was about to type them, but I'll just, so the question is currently, currently are you only targeting law firms? What about the mortgage industry? So we interestingly are our most noteworthy first mover early adopters are Hogan levels, giant global law firm and BNP Paribas in their real estate division. We have significant focus on real estate, but we interact with some of the biggest banks, insurance companies, the technology is really, it's a universal thing. We've started within the legal industry because lawyers tend to draft or touch almost every contract of significance. And so the legal industry operates as a horizontal from which we can then create collaborations in literally every industry. So by historical coincidence, we happen to have done a lot in real estate. We're very interested in that industry and our first deployments are in real estate, but you'll see, you'll see things coming that some of which have already been announced with respect to ESG, you know, and so in the concept there is, if you're using, if you're trying to, to me, ESG is a messy problem, right? And their company is trying to create fancy new software to figure it out. Our view is using identities. You should be able to catalog and move ESG information firm to firm related contracts. So it's intellectual property, it's supply chain, banking, insurance, it's everything and we're working with everyone. Next question, how do you manage revisions and addenda to your previously registered contract? So we are not a document management system, right? We are a document identity system. The, and so how people implement this within their existing software or patterns of document management or collaboration is up to them. So we've actually built, you know, a demo that builds this right into Microsoft Word. You know, so you can have successive hashes of successive versions, you know, and we see a future where potentially this enables universal collaboration, save Google Docs to Microsoft Word and others using identities to help, you know, create the connection and translation of data without having to actually commingle or share the document. Yeah, hopefully that answers that. So we're agnostic as to revision, you know, revise it. You can hash an ID, the revision within that revision you can embed the identity of the predecessor. I mean, there are various patterns that we think make that pretty exciting. David, very quickly, if you create a revision, it gets a new idea, it's a different document. Can you tie these IDs together? Sure, there are patterns you can store as metadata on the blockchain, although Mike alluded to, that's not always the best idea, but we support it. You can embed the IDs and the metadata of the smart document, which is a pattern we really push, or you can, as David alluded to in Enterprise Integration, you can store, you know, within Salesforce or whatever software you're using, the IDs and relate the documents together there. So that's a slightly more technical explanation. So going to the next question. So Dave partially answered that. Is the document storage handled through IPS? We don't care. You can do it there, you can do it in your C drive. Again, we're just registering proof of existence and creating identifiers for documents. So documents can be stored anywhere you want. This is critical to the system. It's non-disruptive to current software, current usage. All we're doing is adding this blockchain anchored identifier. Next question. Do you anticipate collaboration with law as code initiatives? So we've spoken at Codex a couple of times, and I assume you're referring to Stanford. We think what we're doing is actually part of the answer to the challenges in the smart contracts world, for example. Smart contracts need to work on trusted agreed data. What we're doing here in adding digital trust to kind of the traditional document layer, which is kind of everything at the moment, allows, in a way, Integra to be like the ultimate oracle. So if you're moving data from, again, the trillions of documents and you want to perform operations, automated operations and smart contracts, we think Integra infrastructure is profound in what that enables. And just in general, anything where you're going towards law as code, machine processing, automations, whether smart contract-based or just traditionally-based, anything that distills data to something that's trusted and structured is helpful. And I think we make a big contribution to that. Hopefully that answers the question. What security do users have that the information is still there five years from now? The couple, I mean, a couple of answers to this and David Berger, feel free to chime in. The ledger, the Integra ledger, if you think about it, is just IDs and hashes. It's really simple stuff. It's publicly available. You could copy the ledger. I mean, anyone, any could take it. So for our first organizations, part of the selling point with them is if Integra disappears and they've brought their clients into this technology pattern, provided they possess a copy of those numbers, they can continue to operate using similar technology with their universe of clients. The critical thing here is Integra is not moving value. So you don't have that security risk and complexity and we're not intended to be performing automated operations. In other words, smart contracts or chain code in this case. It's a very, very simple idea. David Berger is also experimented with redundancy on Amazon's QLDB, I believe it is. Again, it's a long list of numbers. You can copy it, you can store it. And it's our view that with the many organizations involved in this, there will be a huge amount of redundancy. So I don't think that's gonna be a worry. It has not been a concern of any of the big organizations that are involved. Yeah, actually, David, not only have we played with the redundancy, one of the first real world uses of Integra was our QLDAI does a California workers comp claim. So if someone gets hurt at Amazon in California, there's a fairly good chance. It's the hash of the documents will hit the ledger. They have a functioning Amazon QLDB acting as a backup. Last question. You have mentioned areas in the non-creds who would be the holder of the verified credentials. The person uploaded the document or the parties involved in the doc, wondering since they're usually at least two parties in legal docs. David Berger, do you wanna take that? Good, it's the creator of the doc. So we have functioning demos. We have functioning demos where you, when you drag the doc into the browser as Mike alluded to, we're doing a lot of processing in the next version within the browser itself using WASM and various technologies. And you have the ability within the browser, within the app Mike was showing or the live apps where you can click and it brings up a QR code. You can then take the wallet Mike showed and scan the QR code and open up a channel between the browser and the wallet. And the wallet can then sign the hash or send over a non-credential information to embed in the document. And again, since I'm gonna push technology and all and this is kind of a geeky detail, we're going to port the wallet over to the ARIES by full wallet. So again, another hyperledger technology and use AFJ, which is the JavaScript implementation of ARIES to actually do all of the work necessary. So the creator of the document, remember, whoever, when you create the document, it gets hashed and that becomes the ID. So the person embedding the information is the one responsible for hashing it and then calling the API that Mike showed to actually record the data. That's my long-winded answer. Thank you very much, David. I see we do have some more questions but unfortunately we ran out of time. So thank you very much, David, David and Mike. And for those of you who still have questions open, please feel free to reach out to integral ledger team and you have the contact information over here and all of the slides will also be uploaded to our webinar library. So you're always welcome to check them out there as well. Once again, David, David and Mike, thank you so much for your time today and for sharing all of this great information. And thank you everybody who joined us live for this webinar. I hope you enjoyed it. Now before we say goodbye, I would like to invite you to join our Hyperledger Discord where we have a lot of real-time engagements and you can contribute and also get good information about our projects, about our special interest groups, our original chapters and more. We have some other upcoming webinars. So in April, we have instant about enabling portable KYC for financial institutions. So please go to Hyperledger events to register there. Thank you everybody for joining us. Thank you again to our panelists for this great presentation. I hope everybody enjoyed it and thank you again for joining and hopefully see you again at our next Hyperledger in-depth webinar. Thank you. Thanks everyone. Thanks.