 I'm David Snyder and basically going to cover three things today which are two software licenses that Marta and I wrote together, just to kind of talk about them conceptually. One made it all the way to production, one didn't quite make it there, and then we'll introduce a little bit of the work that we're doing today around decentralized access control and I think it has some implications for some of the thinking that is happening both in the context of what is the technological infrastructure that can be used to achieve the goals of patents not necessarily through a regulatory route. So with that, we'll start with the first license. We wrote in 2018 and basically it was a software license whereby in the header of the license, well let me add a bit more of a preamble. So the intent in writing this license was to do turnkey dual licensing whereby you would have some code that was licensed under a copy left provision like GPL and then the other commercial license that was on top of that and associated with that code in GitHub in the repo in the header was basically referencing a specific smart contract essentially an array of holders on chain that were the parties that were dual licensing and by virtue of having the private key associated with that address that was referenced either by holding a token or being part of array, it was through that way that this dual licensing was possible rather than having so the license was functionally just living in one place and then the parties that had paid for this for this exception if you will was on chain data and so that was really fun. Marta, anything else to add on that license specifically? Oh no, that was a very good overview. Yeah so that was a pretty kind of interesting experiment in 2018 as it relates to some unique licenses. The other one that we never quite got to production but was even a little bit more radical was an idea to create a tokenized co-op as an alternative to licensing some code in an open source way and so this concept was your developer, you create some unique piece of IP, some unique software and the license that you associate with it in GitHub rather than being like a copy left or you know another open source license would basically again point to the chain and say only people who hold over N of a given network token have the right to use this software in kind of an open way and the intent was then to essentially have a DAO-like organization where anybody could voluntarily add their IP and their software to this pool just by licensing their code underneath this provision and it was kind of like an interesting way into opt into a communal pool of goods that then had a tokenized system on top of it around incentivizing good new work. Maybe a little bit interesting in a deep because it's not de facto or definitionally open source but thinking about these other commercial mechanisms especially with really really easy non-technical ways for people to opt in into that kind of system so yeah that was the second one I think we called that like the I don't know token community license or something like that so those are some two those are so two interesting projects both of those are just kind of sitting in a zombie state happy to like share that or you know a lot of that is just kind of open and lingering and then I'll take a couple minutes to mention what I'm working on today with LIT protocol and what I think some of the implications are around I mean dweb tech in general and then we can talk more about IEP and licensing but what we have is a decentralized encryption access control and compute network we don't have to go too far into the architecture but it's basically the system that is custodying a key pair a private key aka a wallet across a set of nodes so if you're familiar with like multi-party computation or group signature aggregation threshold cryptography it's very much in that category and what people are using it for today we do a lot of work with protocol labs and file coin and and a lot of customers who are using ipfs ipfs is around storing private data on the open web where people can encrypt something client side upload it to the decentralized web take that symmetric key tell lit this decentralized network hey only provision this key to a user who meets certain on-chain conditions such as the asset that they hold in their wallet and then we have this network that can do that verification and do the key provisioning so this is kind of a really interesting thing especially if you're you know if we think that there's things to discuss around access as it relates to ip and license and patents because this is a mechanism to have essentially a key master or a key provisioner without there necessarily being a centralized key master in the context of building these decentralized systems so that's where we are today and then I'll like peek a little bit ahead into the where we're going the way that that system functionally works it's basically like one big distributed custody wallet for doing the signing and encrypting and then where we are going is with a product called programmable key pairs whereby this network can perform a dkg a distributed key generation creating a new wallet and basically we're envisioning a future where every agent whether it's an individual some internet connected device something else essentially has a cloud custodied programmable key associated with it and think that there's also some other interesting things to kind of like explore through the lens of ip security privacy and innovations and patents in that way