No Keys, No Fees, No Hassle: The Future of Web3 UX on ZKsync | Antonio Ufano Gallego - ZKsync

[Music] okay uh hello everyone can you hear me well yeah so my name is Antonio I'm a developer relations engineer at matter laabs which is the team behind CK sync the elastic Network and today I'm going we're going to talk about web 3ux uh why it sucks and the things we're doing to to fix that so before we start uh we are one of the sponsors of the hackathon and we have $25,000 in prices uh in in four tracks and we have prepared a repo with all the information that you need to to build on any of these tracks we have examples tutorials uh the requirements Etc so if you're a builder just scan this QR code and you will have all the info there and I also have this QR code at the end so that's okay so yeah why is wave3 not main stream yet well there are a lot of pain points when you are using web3 applications like for example you need to create a wallet and when you create a wallet you have to manage your your private key you have to store it somewhere uh not on paper you don't have to take a picture it's nobody knows how to securely uh store a private key to be honest uh then you have to sign every transaction uh which is really a bad experience it adds a lot of friction uh you have to deal with gas fees you have to pay for everything that you do on chain and in general apps feel cranky compared to web two applications I'm sure you've seen this video from a from an onchain game where every single uh bullet is on chain and you have to accept every transaction to be honest I'm not sure if this is real or it's just a parody but this is kind of what it is right now uh interacting with with three applications and yeah other pain points obviously are hacks FDX Tera uh scams but yeah this that's for another talk so the vision is web 3 should feel like web two and uh instead of on web two you have uh you can log in with Google with just one click uh with on web 3 you have to install an extension on your browser or an app and you have to create a wallet uh on web 2 you can if you forget your password you can recover it easily uh on web 3 if you forget your private key and you you lose it basically you're done uh on web two when you interact with an application everything is instant uh on web 3 what you get is a confusion approval for a transaction uh with a bunch of random letters and numbers that nobody knows what they mean and in general in web two there are no friction but in web 3 it's painful as hell so the vision is like user stent even realize that they're using blockchain and if we want to onboard millions of users we need to make blockchain invisible so this is something that we've been working on uh a lot in the past uh two years and there are a few features of CK sync uh that really helps improve this experience well the first one uh C Ina and all the chains in the El in the elastic Network they are either Layer Two rollups or or validium so transactions are very very cheap compar compared to ethereum and block times are super fast we're talking about one two seconds so yeah that's one thing again uh we have native account exraction so and it's integrated our protocol levels and all accounts on S Ina and all the chains of the elastic Network are smart contact accounts even externally own accounts we have pay masters which are these special smart contracts that allows application developers to sponsor transactions uh on behalf of the users so they don't have to have e on their wallets to actually use your app and a few months ago we launched CK sync SSO which basically enables apps to to easily on board users but uh allowing them to not have a wallet and use use pass keys and Biometrics from from your phone like face ID or your fingerprint and then they use of sessions so they don't have to uh confirm every transaction and I want to focus on the last two on pay masters and and CNC uh SSO so yeah gas fees I mean they are necessary but they add a lot of friction for for users but if I'm a user I really shouldn't have to have e uh to interact with an app uh and pay masters are basically what allow this uh an application developer can deploy a pay Master fund it with some e and then the pay Master will pay the gas fees on behalf of the user so that reduces the friction so which means it's better ux so the users are happier and on cing we've been doing this for two years since we launch uh C care mainnet and there are a few projects uh that have launched since then uh like pay Master as a service uh applications like sci-fi that basically they deploy a pay Master for you so you don't have to as an application developer you don't have to do it on your own uh and basically you integrate it in your app and then your transactions are free it's pretty pretty simple and we other thing that we have also seen is a lot of collaborations between uh nft communities and different applications uh um on the network where if you have one nft your transactions on different applications are free this is an example from syn SWAP which is a a a DEX on CK sync and as you can see I'm trying to swap some e for usdc and as I have one CK Bey which is a an nft collection on CK sync the transactions are free and this is something that we've seen a lot in the past two years and yeah this is great because we are getting rid of of gasf but yeah we're getting rid of gasf but this doesn't solve all of the other problems that users will still need to have a wallet they still need to manage the private Keys uh they still have to accept or approve every transaction so to solve that that's where where we have built this inv invisibility cloak for blockchain uh and basically solving that problems means at the end of the day you using smart contract accounts using passys and using sessions and to to do all these things we build CK sync SSO which stands for smart sign on uh SSO is is a modular framework to create the smart contract accounts uh to authenticate users and to create sessions and developers can integrate it into their apps very easily I will show an example uh later on so the main features of SSO are we provide uh smart contact accounts based on ERC 7579 which is like it's a template uh smart contract and you can add modules like spending limits or uh limits to to say which applications your smart account can interact with things like that and those modules can be extended uh it it provides pass key authetication so there's no need for SE phrases uh we have an open source authentication server as well uh then as I mentioned with sessions uh that can be configured so you can configure the the spending limit uh or if their session is only allowed to interact with a specific a smart contract or with a specific method of a smart contract things like that that we we call them policies we have integrated pay Master support so you don't have to build your own pay master and deploy it on C sync and soon we will have account recovery so in case you uh your your account is not sync uh with iCloud or with Google Cloud uh if you lose it you can recover it through email for example so for my user point of view uh how does this look like so a user will sign up use your SP ID or your fingerprint uh then there is no se phrases the the out server will deploy a smart contract account behind the scene and the user will just he will not see anything related to to to the account itself when when it comes to interacting with applications there will be no popups to accept transactions and whoop yeah and that's it so if you want to see it in action uh users they don't have they they don't need to have a wallet so you can just open your phone with no metamask or no rainbow wallet or coinbase wallet or anything you don't need anything you just visit a website and you can connect when you sign up uh the account is is deployed behind the scenes and then normally what we do or what what the applications will do is they will Define a session with some policies like the contracts to interact with and uh the limits uh to spend things like that and there will be no need to to send transaction here's an example uh that we build so this is on a phone when you click on sign up uh you will get this popup and this are the policies that will be created like uh the target smart contract that will set this session uh will be allowed to use and I was recording this on my laptop so it will scan my fingerprint and then you're on your app uh as you see on the top there is a wallet but that's totally optional you you can decide not to sew it and in this one you we just meaning an n and as you see there is no popup to accept the transaction or anything like that everything just just works there is no wallet uh it's totally transparent from from a user point of view so uh if you want to integrate CK sync SSO into your app uh how do you how do you do it well right now uh SSO supports both wacki and web3 model which are basically the the most popular uh libraries to to build front ends uh to install your the the mpm package with with mpm or whatever uh package man manager that you're using then you create a connector uh and Define your session policies and then add that connector to your to your WME config uh and that's it uh this is how it look like on the code so if you see the the cync SSO connector it accepts the out server URL uh which we provide one on C synare atest Net at the moment so you can use that one by default and then on your session you can Define the fee limit which is like how much eth can this session spend in gas fees and then uh contract calls is an array of the policies that this session will be allowed to so in the example below the policy was that the the session was allowed to interact with the nftd smart contract and only with the mint function of that smart contract there's on if if someone else uh Ste the session private key and tries to do something else like transfering the e or interact with other application the transactions will will be reverted uh once you have your your connector if you using W meet you just uh pass it to the connectors and that's basically it I mean from a from a front end point of view there's nothing else that you have to do because wac me manages everything behind the scenes so yeah uh to start building if you're an application developer uh you can enable gasless transactions by using a pay Master uh but basically SSO take takes care of everything so you can integrate it on C in Cara today uh SSO is available on testet uh it will be on Main net soon but also SSO is not meant to be just a wallet that will replace the wallets for for everyone we we provide it as a starter kit for chains or wallet developers so if you're building a wallet or you're building your own uh chain and you build you can you want to build your own smart wallet uh you can use SSO as as a starter kit and for example uh abstract Global wallet uh Sone they're using uh the SSO smart contracts uh behind the scenes uh yeah that's basically it that was fast uh if you want to try the SSO demo uh that I was showing you before you have the the QR code over there and then again the hackathon resources uh for any Builders and yeah that was it 15 minutes that was faster