litu safu

Screenshots

Problem Statement

A marriage between the Litpkp and the Safe Auth Kitwe have created compatibility between the auth kit and the litpkp so that you can create wallets that create and sign safes with oauth (google, discord). We provide some skeleton code for supporting webauthn (faceId, touchId...etc)The ability for a Litpkp wallet to sign and create Safes!We have ported over functionality from safe-core/protocol-kit to be able to sign safe transactions, create safes from your Lit pkp social login walletthis provides the infrastructure for being able to sign safes with your faceId, touchId, google account, Discord account ...etc!Account abstracted!

Solution

SafeAuthKit x LitWalletwe instantiated a litwallet with arbitrary auth methods (supporting both oauth and webauth) as the core provider/signer, replacing the existing provider/signer in the safeauthkitto do so required a ton of changes to the original safe auth kit classes, interfaces, types...etc.!The ability for the pkp to mint a safe!once we were finished with safe-auth x litpkp, we could now use the PKP address to create a safe!this was a difficult process as the pkp wallet wasn't out of the box compatible with the safe-core-protocol SDKthe PKP wallet then creates a safe via the safe factorythe ability for the pkp to sign transactionswe built a transaction through inputs of domainData, safeTypedata and the Eip712 tx type then signed this using a Lit actionWith this signature, we passed in other safe execution parameters which we require the user to input along with the signature to sign and execute existing transactions on safe!Some of the things worth mentioningCompatibility between the litwallet and the safe auth via writing our own adapter instancewe were able to use safe PKPs to sign a Safe transaction without using the SDK via lower level calls / functions