Andrew Wisniewski I Universal Composability Digital Ownership & Autonomous AI I Agentic Ethereum 2

[Music] hi everyone Andrew from the lip protocol devil team here recently our team has been working to resolve a pretty crucial issue in the AI agent space uh which is how do we trust an agent developer with our agent's wallet and so we've come up with an interesting solution using the lit SDK and that is the lit agent wallet so what is lit agent wallet it provides AI agents with immunity tempering by agent developers so this means that the agent owner whether that be a dow multi-g or eoa can be assured that their agents funds aren't tampered with by the developer responsible for executing the agents intents or actions so before we get any further into the explanation let's quickly cover some terms from the lit SDK so lit has programmable key pairs or pkps uh LD actions are a mutable JavaScript code published to the ipfs and we Define a sub agent as a GPT 40 model that parses an intent whether from a user or Ai and from that uh intent correctly selects a lit action uh based tool for the pkp to execute now that we've covered some uh lit specific definitions let's explore how the framework separates the interests of the agent owner and the developer so we Define the agent owner as the admin the admin is responsible for the ownership of the pkp nft and the admin also defines the tools and the policies um that restrict these tools uh so for example if we have a tool to transfer erc20 tokens from our agent to any other address we can restrict our agent to only send uh permitted tokens to permitted addresses and to transfer a specific amount of each token so next is our delegate delegates can be thought of as the Developers responsible for executing the agent's intent their execution scope is limited by the tools and policies defined by the Admin and they must be specifically chosen by the Admin to execute the agent's intent if you are a developer yourself and you are building with an agent framework like Eliza in this case you would be the admin and your delegate would be the llm that Eliza is using so this diagram is a pretty granular view of how the framework operates so we can see that the llm provides transaction parameters to an Executor or developer um that executor or developer provides the transaction parameters and authentication to a specific tool and that specific tool performs signing um so that tool is again a lit action published the ipfs so it goes to that tool with the correct ipfs C ID uh and we can see on the bottom right signs the transaction but before that we can see that the admin has delegation and policies and so delegation we have the delegation engine where we delegate specific executors or developers uh and then next after we have successfully added a developer or delegated them guess as a delegate as we said previously we have the policies so has to verify with this policy to ensure that the parameters passed in by the developer are restricted or I guess within the confines of this policy and after we pass a policy we then perform the signing so for this project we have a couple prerequisites you have to have node.js version 18.12 or greater get of course to clone repository pnpm um which can be installed with npm or yarn an ethereum wallet and for that ethereum wallet you will need lit uh test lpx tokens and you can grab those from the faucet linked on screen or it'll appear if you just search uh lit faucet and then CLI demo so we'll add the package from npm um the CLI is just a simple demonstration of how you can use the lit agent wallet uh package uh kind of the first use case of it so we'll add the package from npm and then we'll run the executable lit agent wallet and next we'll go into the demonstration of that so after installing the aw CLI package we will run the lit agent wallet command and we'll be prompted to select a lit Network so these are the three lit networks for development pre-production test and production uh lit agent wallets are scoped to these networks so once you've minted a wallet it can't be moved across networks so just please keep that in mind for development in this example we'll be using do Dev we'll start as an admin it asks us if we would like to manage an an existing agent wallet or mint a new one for the demo we will mint a new one and we'll say yes we would like to manage it we'll start by going into the tools and we will permit a tool for our wallet so the awci demo comes with three tools erc20 transfer a swapping tool and a signing tool so we'll just say we'd like to permit the signing tool we'll then go to delegates we will first add a delegacy so we'll enter in the address and then we're going to go back to the delegates menu and we're going to permit our tool for the delegate te so you can see we select the delegate te we select the tool and now the tool is permitted so then we'll go to policies we'll set the tool policy so we'll select the tool AR delegate T and then it'll ask us to enter the ipfs CID for the policy so so those can be found in the readme um there's a default policy which I will copy paste here so nice we've set the tool policy so one last step here we will go to our policies now we will set a tool policy parameter for S cdsa and then again for our delegacy as well and then we have to enter the parameter name so so the sign ecdsa tool has one policy attached to it and that is allowed prefixes so we'll enter that and then you enter in the type so the type is an array of strings so we'll say we allow the prefix High nice so we have added one policy parameter to our tool and this is the step where we move to the side of the delegate now so next we'll run the lit agent wallet command again from the perspective of the delegate so again we'll have to select the Datil Dev Network where we minted our pkp or agent wallet of course uh we'll select delegate rooll can look at our delegated pkps so you can see I've used this wallow before because we have three pkps delegated to it but the most recent one is the one we just minted with the ad so we can say get registered tools select our pkp and as you can see we have our sign ecdsa tool with the policy enabled uh we can also get tool policy so if we just wanted to see the ipfs CID of that tool policy we could do that as well so finally we'll go execute tool we'll go to our agent wallet sign ecdsa and as remember we set a prefix so the any message we send has to start with that prefix so we can say hi there and so we'll execute the tool and as you can see we got the signature uh sign message success it sign the message hi there again we can execute the tool select our pkp sign ecdsa but this time we'll say I will not say hi there again this message doesn't start with the one allowed prefix which is high so we'll try executing this tool as you can see there was an error and our error was message must start with one of these prefixes and that prefix is high so yeah that's it for this demonstration if you have any questions I recommend you reach out in our telegram we have a dedicated channel for questions about the agent wallet I also recommend taking a look at the API docs there's a lot of good information there on how you can build with the lit agent wallet yourself and yeah I hope this demonstration was helpful thanks for watching [Music]