Improving web3 User experience through chain abstraction - Collins Enebeli

so uh that's my name on the slide Collins my full name anybody uh like I said I'm a Dev just like almost everyone here and I've been working in repb tree for about three years now that picture was taken in like 2021 so like it may not look really much like me but like I don't think it matters yeah okay I'm talking about improving web user experience through chain abstraction uh okay good I wanted to see this I wanted to see how I look like on the stage okay um let me start with this right how many of you here are not devs but you understand how the web ecosystem works like you know how to create a wallet you know how to interact with chains you know how to Bridge tokens from one chain to another you know how to basically you know how to use D apps like just wave something you're you're not a Dev okay so everyone here are devs very good so uh it's actually nice cuz I'll just be scratching the surface and I would assume that you guys understand what I'm trying to um explain uh next slide please good so I added this Meme here because um I kind of have um social anxiety so and I don't like um being in front of the cameras and all so I was hoping I would make this as a joke and then uh you know when people make Twitter post like oh inspiring session and then they tag you they post your picture and stuff like that uh I wanted to say like if you're going to post anything please post my slides and like not me cuz uh yeah like social anxiety thank you but yeah like it's too late cuz the cameras already pointed at me and I'm sure even before this came up like maybe people already take two pictures so next slide let's just skip this yeah so the ux challenge uh bridging web two and web 3 I'm going to try to be very very fast CU like um my time is already running out so uh it's common knowledge like that there's uh a very big gap a very big uh ux problem uh between web 2 and web3 so with web two all you need to do is just like log in maybe your email or with your phone number or something and then you're in but with web Tre next slide with web Tre uh there's like a lot of complexities so uh major challenges around onboarding Web Two uh to web Tre and when I say like web2 to web3 I mean like web2 users like people who are used to the traditional like web to Applications you sign in with your Google Google accounts or your email your phone number and stuff like that uh complex wallet management deters new users exactly so um okay you know I'll just list them also unfamiliar Concepts like uh gas fees public keys and stuff uh this this this Concepts they kind of creat uh friction for web web2 users who are trying to get into web tree they may not even know like what web Tre is they just want to use your application and then you're trying to tell them oh connect your wallet do this do that brid tokens all of that security concerns due to um irreversible transactions so for example if you're making a transaction via let's say Stripe Right um I want to believe there's a way you could uh retrace your steps and maybe like get a refund if something goes wrong right but then with web tree like it's irreversible to the best of my knowledge right and then uh lack of password recovery option so if you misplace your private Keys your your seed phrase that's it like you're done for next slide so all of this challenges brings us to smoothing the experience for users navigating between web 2 and uh web tree which I I'll I'll spend some time talking about like all of this but in the next slide I want to talk about uh tips on reducing friction for users navigating uh between web two and web three applications so these may sound kind of um intuitive like oh like yeah like this is common knowledge but I feel like most web tree devs I don't know if it's like the product teams or like the devs They Don't Really they didn't really pay close attention to most of these things they just assume like everybody knows their way around and everybody knows what they're doing when they come on a uh decentralized application so uh tips include uh implementing social logins and famili authentication methods like I just mentioned uh because with your web your web two apps you're able to sign in with your Gmail account every time your phone number and stuff sometimes you don't even need to sign in yeah but with web tree you would have to connect your wallet you have to do some kind of sign sign uh a signature and stuff like that uh use Clear Dragon free language so uh for most dabs I have I have come across right uh on the landing page you see like very big words and uh very complicated uh lingo on their website and this is because they just assume that um everyone who is coming into like who is um visiting that D app everyone knows exactly what those me all of those means right uh and this is because most times uh web tree platforms they don't really pay close attention to user experience they just uh want to make things work uh want to ship the next decentralized this and that provide guided onboarding experience offer fired on Rams for easier token acquisition so what what is basically means is um you should allow your users to acquire tokens via like normal cash transactions and also Implement Progressive disclosure of complex features so what this basically means is like you don't just throw all your features at your users right you don't just uh when they open the app you are showing them like a lot of things complex like you Progressive disclosure like just Le to by L to next slide so most times if you don't do all of these next slide please if you don't do all of this or even if you do it's kind of uh you you some of you may have this questions like okay so how does this help solve the problem right uh are in there web Tre apps that already do all of what I have listed uh in the previous slide and then good uh the the last one is some sort of a joke and I hope everyone here gets it so it says like okay how then do we interact or verify users wellet how do we verify if the users wallets are authenticated if we use social Arts that's um Google discord whatever rather than the usual um connect wallets right so next slide please the next SL is actually the joke uh with metal marks as usual next slide so all of these complexities would have um your your your DB literally screaming at your users like what what the hell is the polar beer doing in Alon Texas cuz like you're just basically telling them like they are not supposed to be there uh you don't care for them you don't care about them like you don't care about new users you only uh you only care about people who are very very versed in web tree um to use your DB so and that is not like that that's supposed to change like uh there are new technologies new um inventions new um research items that enable us um solve this problem in web tree so first item account abstraction I'm sure um you guys you guys agreed earlier that all of you here your devs uh so I'm assuming you one way or the other someone must have heard of account abstraction so when I came on the stage they told me like I have to be interactive right so I'm going to show a question like account abstraction like who who can like just give us like a two word one word what is it about like anything okay we have someone here uh your name or your nickname whichever one my name is um my name is Franklin that's nice um I think um I would like to say that um what I can say about the account abstraction um is like um with um ethereum name name service um you can use your name that's that's attached to the eth and they can use it as sort of an address to do transactions to you instead of your normal ethereum um account and so I think with that it's easier for people to do to send money to you and do transactions and all of that okay um that's awesome that's a very nice um answer it may not be exactly what I was hoping to get so I would throw the question to maybe someone else help us out anyone but he said I should ask questions are you guys bored I should keep talking right uh next slide please good so basically what account abstraction does it allows users to interact with smart contracts in a more flexible manner like uh more flexibly via um The Arc 4377 protocol so if you guys were not devs I would proceed to um explain what all of this means uh maybe I'll have to do some Googling as well but you all of you agree that you're devs so I want to believe that you guys understand what this means so the RC 4377 protocol enables us have uh what we call uh smart contract wallets right uh so we with the the normal web Tre wallets we have right now your metam Marx your Rainbow wallets your coinbase and all of that uh they they are all called um externally owned accounts but with the ERC 4377 uh protocol we cannot have what we call uh smart contract wallets next slide so what are the benefits of uh a smart contract wallet uh it lets you um it lets you use a custom transaction logic so with your normal traditional externally owned wallet uh when you want to make a transaction right you have to sign like that's that's almost yeah you you can't skip that you have to sign the signature and it's just you right uh just you with the key phrase that have to do that but with uh with smart contract wallet you can apply custom transaction logic uh so for example you can enable multi signatures for a single transaction so for example uh one person has to sign and then another that person have to sign so I don't know if you guys are already seeing like how this can be useful so for example this is like right top of my head but for example let's say maybe in a company where you have like various stakeholders right and then uh you want to make sure that um there are multiple signatures to a single transaction uh uh um smart contract wallets help you do that you can also apply spending limits yeah and then improved ux EG gasless transactions and B transaction so with um smart contract wallet you are able to B transactions which I want to believe means like sending multiple transactions like all all combined at the same time and then um gasless transactions which is not really gasless because someone has to cover for the fees right but with smart contract wet you can decide who pays for the fees so it doesn't have to be the person uh signing the transaction it doesn't have to be the person uh making the transaction uh who have to pay for the fees right so I'm going to I'm going to shed more light on that later but I just want you to note that like um smart contract wet enable you to have like gasless not gasless like enable you uh determine who pays for the gas fees so okay let me quickly give the example so uh an example of where this will come in place is okay let's say you're onboarding Web Two users to your application right and then they have to uh maybe maybe sign something maybe to make a transfer or something right but then your web two users they don't know anything about gas fees they don't even know to get G fees maybe you're in a relatively new chain like scroll or something uh some users don't even know the Dex even if they're familiar with like web tree you don't know what deck to go to to get gas fees on uh on scroll right so with smart contract W you're able to cover the gas fees on behalf of your users right so your users all they have to do is just like sign they don't have to buy oh let me go and get gas fees let me go to binance P2P to um get some tokens for gas and blah blah blah blah stuff like that yep enhance security so with smart Contra wallet you're able to apply like custom Logic for recovery so this is like a whole topic on its own so I would love like if you're enthusiastic like uh you can um do some research on that at the end of my slides I'm going to like drop uh platforms that enable you like use all of these Services also Advanced features like automatic payments and app Integrations next slide please so problem solved yeah please take a picture read yeah next slide thank you MPC architecture yeah like I really really wanted to talk about this a lot but time is not going to permit me but like this is actually like the main part of my talk but unfortunately they're chasing me away uh so soon actually how this works blah blah blah blah blah please take a picture thank you so much I'll share the slides after after I'm done yeah so and if you have questions like you can come to me and then maybe ask questions uh next slide NPC in action so these are basically platforms that let you use NPC architecture so basically MPC means uh multiparty computation basically what it does is it lets you um manage your keys without the need for key phrases without the need for seed phrases or private keys so basically you're able to store part of your private Keys uh in different uh how I put it