 same app at the same time. And if we have luck today, Cornell's in Romania, so we may have some network issues here. But if we're lucky, we're going to see some real-time stuff where we sign it, create a document, send it to Cornell. He can sign it. We can sign it, and then we can record it on the blockchain. So the blockchain, the one and only. This one is actually Ethereum that we're using. Unfortunately, sorry about the screen sharing thing. It's blocking some of the buttons. Also, it looks like the mouse doesn't work. Yay. Live demos. Where is it going? Something's frozen. OK. Oh, wanted over here. OK. So I'm, oh, let's switch windows. So I'm going to create a new document. I could create a couple of kinds of documents. This UI is generated from schemas. So you can have a schema for some kind of data that you want to collect, and it will generate a form that people can then fill out, and that can be signed. And you can also attach files to it. So let's do a vehicle sale. So I want to buy a car from Cornell. I would like to buy, let's see. How about a van? Let's buy a van so we can live in a van down by the river. That would be great. And I'll add Cornell as a recipient to this. This is not actually using email, but we're using email addresses as a quick and dirty identifier. And I'm going to add a file to this. Let's pretend that this PDF file here is actually a contract. We should be able to open this up. It will send the actual file to Cornell as well. I'll add a few things in here. I think today is Halloween. So in a perfect world, we'd be using things like DIDs, like Drummond talked about this morning. And that would happen automatically. Let's say this is a Mercedes, and it's a Sprinter. Those are really nice vans. Let's get right to the signature. Sorry for this. We may have some validation, so I have to fill out the form. And let's give it a price. Make it a cheap van. Save this, and now I can send it to Cornell. Cornell, if you can hear me, let me show your screen one second. So you can see that Cornell already has the stock in it. Cornell, can you open it up? So you can see the form data there. And he also has the PDF file. And I don't think this will show in the screen sharing. We'll be in a different window. But Cornell, can you sign the document now? So Cornell signed this. And you can see that I also have another minute. OK, try to be really quick. I have this document now with Cornell's signature on it, just like that. And I'm going to sign it. So it went into my signed bucket. That was the actual signature. That's what the digital signature looks like. It was that string of numbers. That's what was created from the private key. So you can see here, we have two signatures. And two, unfortunately, these aren't displayed very well. It's kind of mushy to see what it is. But this larger value is actually a certificate of the public key. So we can verify ownership of this. To this demo, the idea was that a credit union would be certifying an end user's public key so that you would know it was actually their key. So we're verifying key ownership. And then we've also got, I want to show you, we have a Merkle route. We made a hash tree out of the attached documents and included that here. So those documents are included in the signature along with this metadata. And so we do 30 more seconds. And now we'll finalize this. And, yep, OK. So you guys a little sketchy? We need to get some stuff. It was rapid. So yeah, very rapid. We did this in a couple of weeks in spare time. And so now you can see there's an Ethereum transaction received. So this transaction has been recorded, or this contract has been recorded as part of a transaction. This is actually one valid use of hashing something and putting it on the chain. We wanted to do dual integration, Monax style, and didn't have time to get to it. But ideally, we would have a transaction hash for a smart contract recorded in the document. And then we have the final document recorded here. So that's it. So thank you. Pretty good hack, huh? I think. So nice work. Everyone clap for Chris and his team, the whole team. So people got interested. So just one thing I'll say about this hack very quickly as a takeaway is grab our code. Take our code, use it if you want, report back. Ideally, we pull requests to GitHub. You can ask us, or it's at the MIT Media Lab organization in Trust Core ID. And then what we want to do next that we didn't really finish is do a moth trial with a bill of sale for the car. Something went wrong. Sally didn't pay the money. Phil didn't give the car. Alice and Bob. So now we're entering into evidence along the line he talked about laying that foundation, see how many steps we can skip from the contract and signatures and attributions. That's what we want to test. We want to quantify that and then tune the requirements of the technology accordingly to the legal requirements. Thank you and get out. Thanks man. I apologize, we're a bit behind. We got.