 Hi everybody. Today I'm going to talk to you about MediZar project. I've been working on the last few months at CryptoNet. I'm going to talk about fresh on-network and on-chain data management. So let's derive why. What is MediZar? MediZar, I'd like to describe it as a toolbox to do many things. To do programmatic essence control, which is the first application we're going to focus on on-chain time encryption. One is big on the menu of the stuff. Basically, you can think of it as MediZar allows smart contract or any application that we're focusing on the central application today to all the private key via a fresh on-network. We have a demo about access control we're going to showcase later on on Gurly, Ethereum. And let's dive right in what it means all this. So let's take a step back and what is the problem exactly? Like right now, in terms of private information, there's nothing private basically on-chain. So everything you send is kind of public. And so the smart contract act as a third party, but it cannot hold anything private to its own. So it's a complete public, state public third party. And so that means the smart contract cannot sign or perform any kind of operation on-chain. It's just a testing and running some logic, but not logic, which includes private information. What do we want to do if we could add the possibility of having a smart contract which has the private key, then we could do many things. We could do, for example, one thing, but which are the focus of this talk by now is programmatic access control. So for example, you can access to this document if you show you have this entity during this event. Or I will give this access to this mailing list to all ads protocol.ai user or anything, any condition you can actually prove in a smart contract or in other ways. So general concept of on-chain balls. And so how does this work in the context of Medusa? So Medusa is kind of a network by itself, okay? A network of nodes. It's a threshold network. So that means there's some kind of assumptions here about the honesty of the network. So we need more than 50% can be any threshold. To be honest, in this case, the network will hold the key without anybody knowing it. So no nodes of Medusa will know the key and nobody will know the key, but yet the smart contract can use it. It's very, and when you integrate this design into the blockchain mindsets, then you kind of have this protocol-like design, kind of similar to chaining for those we know. So when the smart contract wants to, for example, let's say one operation you can do with your private key is decrypt something. So the smart contract can see a decryption request to the Medusa network, and then second, the Medusa network will decrypt it and push back the plain text. Okay, so you really have to think about the Medusa as an extension of the smart contract in this way. And so what you can do with it now is you can do things like problematic access control in a very easy manner. So basically imagine plenty of applications that needs to have access control, like for example, document sharing or private mailing list or even the music platform, whatever. They delegate, let's say, the key to Medusa in some sense. They don't do anything, but when they use Medusa, it's kind of similar to, it's behind the key, but they get to the Medusa and they ask the Medusa network to operate on their behalf. And so any smart contract in the Medusa, there's no registration. You just say, hey, Medusa decrypt this thing. And that's what it's like one call. There are kind of two modes about Medusa. Like you can have a global depiction where the Medusa network completely decrypt the cyberdex and push it on chain. So now you are rebuilding the message. But this can be useful for applications like, I don't know, bets or auctions. Speaking of this, but you can also, and this is the focus of the demo that we have today, about focusing on that re-encrypting cyberdex. So if this is what we need for access control management, like the document sharing, we request that you, that the Medusa network decrypts this document explicitly for Bob. So it requests a decryption for Bob and the Medusa network is decrypting it with just re-encrypt the document towards Bob. So how does it work? Let's say from end to end as the user flow. So let's say imagine we have Alice, which has new super top secret documents. First thing it does is encrypting it. Okay, right? So now it has a cybertext. Second thing it does, Alice will submit the document or the key of the decryption it will submit the encrypted key that lead to the encrypting of the documents and it will lead to an event on Medusa. So now the Medusa network is aware, but there is this encryption document somewhere, but it doesn't do anything yet, right? And later on, it can be one week, one month, one year afterwards. Then Bob comes in and say, hey, I want to read these documents. So now it goes to document sharing smart contract and say, hey, I want to read. And now the document sharing platform needs to say, okay, is Bob operational? And this is custom logic. Anybody could code his own custom logic. It could be if Bob is more than 18 years old, or if he's taken enough if or somewhere, like it can be anything. And then if the Bob has the right to access the document, then the woman sharing platform will ask the decryption, the re-encryption to add to the Medusa network. And so now the Medusa network reads everything, will read the decryption request and the submission event formats. And it will re-encrypt. So it will never decrypt the site for text. At no point in time, the encryption will be built. It will be read. And so then once that does meet internally, it will push the re-encryption on-chain to the Medusa smart contract, which will push it to the document sharing. And then Bob will say, oh, okay, my re-encryption is ready. He downloads it on the browser, on his common line interface, whatever. And then he do a local decryption. So then he can read the document by himself, locally on his computer. And that's kind of the whole workflow we've been working on right now on these Medusa projects. Right now, there's only me for this last month. And we just hired somebody that will help me on the smart contract on the backend side. Jonathan is someone. And then we have a working program concept codes. You can check out the code, which is not completely public yet. So you need to ask me first if you want to have invites. It's based on Rust for all the backend and the 3DT right now because we deployed the proof-and-concept code on Gurly. And the nodes communicate barely P2P. We were running several pretty big stuff. We have a demo, which I'm going to show you later. On the future, we want to expand a little bit, so we use it. So like I said at the beginning, there is a test control, but we can do, we'll see when it has begun. We can do time encryption, where upon any condition or witness encryption, general witness encryption, or upon any condition, then we reveal something. We can also do a privacy on top of what are the conditions for somebody to be able to ask the encryption. This could be private as well. So you could not reveal that your name is bothered by your more than it's the other. But if anybody could verify, but at least you are more than it's the other than you are somebody. And MPC could help there. And also we are trying to have some kind of research acts on the extending and the scalability of the basic cryptographic primitive that we use, which is special cryptography. And as such, at least we have the first iteration. We made the first prototype code about DKG. So the underlying cryptographic primitive, which can run with under the nodes, which is not familiar now, and will lead to maybe a prediction thing later on, but we need to decide where we're going to go. And so this is a very brewing project. And if you're interested to hear more and participate or there's plenty of things to do, so don't hesitate to contact me. And now I'm going to show you a quick demo. This is the ACL contract, the Access Control List contract, where it lists only reader and writer roles. I write a text, a cycle, something. It encrypts a whole other chain. And there's a reader role I can show you later that will try to decrypt, ask to decrypt. And this is the Medizar contract. So let's say I want to type a small secret here. Okay, so I play with my Metamask. Well, I can sure it's good. This is on really if you're on Testnet. Now I will switch to a reader role. So I'm not just switching kills. And now I can read. I can read all the side products. These are all the side products, submission times, submission activities. And now I will ask to decrypt this one. I just made one here, you see. I will ask to decrypt this one. So again, it's a transaction by the bottom chain. I asked to decrypt. So my keys is white listed already on the Access Control List smart contract. So I can already read anything at once. This is a very basic demo. But the idea is that anybody can code his own rules. Like there's no, it's just a major size, just a toolbox for people to use on tablets. And now we submitted the transaction and now we're waiting for the order of results. And in the meantime, because it takes a little bit of time because we are on girly. I can show you that there are four participants in the network right now. So there have been four nodes that are holding the private key and major data. These are all the address addresses. And there is a distributed public key to where to add with China groups. And here, I signed this certificate of Uber vanilla and that's it. So you see I can decrypt from the border as well. And that's it for me. Thank you everyone.