The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Web3 UX from a Wallet point of view - John Odey

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

A speaker looks at Web3 user experience through crypto wallets. They cover complex onboarding, gas management and key security, then compare social recovery wallets, wallets that split keys across parties, and account abstraction. The audience asks about paymasters and who signs transactions, and the speaker answers each in turn.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 1 October 2024.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:05 A: Good morning everyone, my name is John Ode, I'm a SaaS contract developer at NAMI, right? And unfortunately, um, Nkechi got my topic wrong, right? So I will be talking about, um, how, uh, the user experience of, uh, Web3 protocols generally, right? But I'll be taking, um, the angle of, um, the crypto wallets, as the case may be. So I don't- So, uh, most times when we look at, um, user experience, we tend to focus more on the, the protocols. Yeah, maybe the Ethereum, the Polygon, and the likes. But that is one aspect of, um, user experience, right? So today I'll be talking about Web3 UX from a wallet point of view, right? So, um, I don't know, I'm trying to make it an interactive session, so I don't know how many of us- I think yesterday we were giving background on, um, the blockchain and how the blockchain works, right? So, um, did we get to talk about crypto wallets? Does anybody know what crypto wallet is? Crypto wallets. All right, please. Uh, sorry, Mike, Mike, Mike. Yeah, I don't know these things, so I'm just here to have a conversation, right?

1:42 B: So basically, wallets are used to hold your assets.

1:47 A: Can you hear him?

1:50 B: So basically wallets are used to hold your digital assets.

1:53 A: Okay, they are used to hold your digital assets,

1:56 B: your keys and everything.

1:58 A: All right, all right. Is there any contrary opinion towards wallets? Please.

2:02 B: So, um, basically a wallet is software that helps you manage your private keys, which are like representations of your accounts on-chain.

2:17 A: All right, that's beautiful, right? So, um, like you said, wallets are what? Software or application or devices? Because we have some devices that are actually like crypto, um, wallets that are not technically softwares, right? So we'll be talking from that, um, perspective. So next slide, please. Oh, sorry. All right, so, um, we've already, um, defined what, um, crypto wallets are. Yeah, so, and we already know the roles that crypto wallets play in the Web3 space. So they are used to what? To store our digital assets and also store our keys that we use in what? Signing transactions and the likes. So for us to be able to onboard the next billion users there is a need for us towards to, um, to rethink the approach that we are taking currently when it comes to Web3 wallets, right? We know that, um, the onboarding process for getting a Web3 wallet is quite cumbersome as, as now, right? And you have to do a lot of things like manage your private keys and whatnot. So, um, that brings us to the major key US challenges that we have in Web3 space right now when it comes to wallets. So the first one is that the onboarding process is quite complex, right? So we have complex onboarding, we have the user face, the user interface are not quite intuitive and the gas management. So we have to learn about, okay, how do we manage gas once there is a spike in the network? how do we, um, manually increase our gas fee so that our transaction can be attended to before others, right? Then there's issue of security and privacy. Yes. So, so there are self-custody risk and, um, there's also cross-chain interaction. So currently we do not have any wallets that you can use on Uh, maybe an EVM-compatible blockchain, then take it to maybe a Solana blockchain or whatnot. So there's always a need for us to have multiple wallets across multiple blockchains, which is actually like problematic. So, so keep track of the private keys and whatnot. So, um, for my talk today, I'll be focusing on 3 main UX challenges that we have here, right? The first one is, um, simplified onboarding and key management. So, um, currently what- this is the current state of what we have, right? So we have, um, social recovery wallets. So social recovery wallets are majorly multisig. I don't know how many of us have heard about multisignature wallets before. All right, so, um, multisig- yeah, you can actually use, um, so multisig is like agents and Genosys Safe. So for us to- if we have a wallet like this, um, if we eventually- so we have a wallet that has like multiple signers. So you can add, let's say, um, 4 people to your, to your safe, to your wallet. So whenever I- whenever my key is compromised, so user cannot- the person that took over my key cannot actually take over my crypto because it requires some other signature for transactions to actually pull through. So inasmuch as this is an attempt to make the onboarding- because management of private key is actually hectic, right? You don't know, do you store it on chain? Do you write it on paper? How do you even manage it? So there is no, there is no foolproof system of managing, um, the crypto wallets, the private key, right? That is why, um, the guys at Argent and Genosis Safe came up with, um, a way that you can actually- if let's say you have 5 signers, so if you don't have 4 over 5 of those signatures, there's no way you can take over that particular account. So the next one is, um, wallet as a service. So, um, Torus, right, the guys behind Web3Auth. So for, for, for them to make onboarding easy, right, they, they wanted to create like a Web2 kind of feel to what's, um, the experience that we are having now. So whereby you can sign up with your Google accounts, then underneath the hood they generate your private key. So they share it into 3 shares using MPC. I don't know, have anybody heard about MPCs before? So MPC is multipath computation, right? Whereby your key, your private key, is not stored, right? It is cryptographically encrypted into 3 different shares. Right? You, you hold one on your browser, one is associated with your, um, the login, um, social media, um, that you use, and the other one is stored on the Torus decentralized network, which is run by a couple of guys, I think Binance and the likes. So with that, we have a Web2 kind of feel. So then you ask, how do you sign transactions, right? When you are using, um, a social, a social login while interacting with, um, Web3 auths. So the thing is, for, for you to be able to sign any transaction using, um, Web3 auths, right, the- there, there are 3 key shares like I mentioned earlier. So there's one on your browser, there is one on the- that is associated with your social media, and then it's one that is managed by the Torus network. So easily when you log in, so you get the one from the social and the one on your system. So you have 2 out of those 3 shares, so you can actually sign any transaction. So those signing takes place under, under the hood. So there's no need for, um, popping up of MetaMask and the like. So you have like a Web2 kind of feel. But there is a problem with that. So this, uh, this other keystore, right, is installed on your browser. So you can actually look it up on your local, local storage. Then if I have access to your, uh, what's it called, your social media handle, I can actually compromise this, um, this particular wallet. So that is one of the drawbacks on this, although they've done a lot of great job, but that is part of the limitation. So I will move to the next one, right? The next one is account abstraction, right? So how many of us have heard about account abstraction before? All right, all right. Um, can you please, can you explain to us what, uh, Don't worry, don't worry, we are here to learn. I actually don't know what account abstraction is. Just help me, help me, help me.

10:07 B: Yeah,

10:09 A: you can pass, you can pass.

10:10 B: It's just, uh, more of like a, uh, should I say a way whereby an account is- ah, Jesus Christ,

10:20 A: sorry for putting you on the spot. I'm actually shy. You can see that I'm struggling here. No, you can pass.

10:30 B: Okay,

10:31 A: do you want to phone a friend?

10:33 C: No, no, no, no.

10:36 B: So it's- so account abstraction is just like, um, abstracting, simplifying managing of accounts. Just like, you know, I mean, like the same thing you talk about, MetaMask popping up multiple times. You don't want to allow like users to go through that stress. You want to abstract it, make it more easier and simpler. Yes, yes.

10:55 A: All right, thank you. So, um, for, um, AA, right, we know that, um, there are actually 2 types of, um, wallets, right? So I mean, there are different classifications of, um, wallets. Generally we have self-custodian and non-custodial. Then we have the, um- so when we talk about accounts, right, we have 2 types of accounts. We have the externally owned accounts and the smart contract accounts. Do you get? So the problem with externally owned accounts is that you have to manage the private key, right? And the problem with smart contract accounts is that you still need an externally owned account to interact with your smart contract accounts for you to be able to carry out any transaction that you need to carry out. So that is like a bottleneck, right? So, um, the guys at, um, Ethereum Foundation, so they proposed, um, AA to be one of the ways that we can have better user experience, right, when we are interacting with the blockchain. So it's just a fusion of the externally owned accounts and smart contract accounts. So what's- what it does is that the account is actually a smart contract account, then you can connect any externally owned account, yeah, to interact with the smart contract account. And if that externally owned account is compromised, you can actually change the ownership of, um, you can actually, from the smart contract, can actually change the ownership. Then you have charge of that particular account. Although one of the drawbacks is that we are still interacting with smart contracts, right? The pop-up will still come. So it's really not an effective way of solving the UX issue that we have. So, all right, so, uh, that's that on, um, simplified onboarding and key management. Key management is actually very, very, very tedious. I think, um, the closest to the Web2 experience that we have is from these guys at Web3 Auth. Yeah, because you have like a Web2 feel. The signing, um, is done underneath the hood. Yeah, you don't have to pop up, uh, multiple times for you to approve a transaction before swapping and the likes. So it's- it can be very, very tedious. I just want to swap. It should just swap. I don't want- okay, you have to approve the contract to spend this. You have to do before you can actually swap. So, um, we move to the next one, right? So improved security. So I, I talked about MPC-based wallets, which is, um, the approach that the guys at Web3Auth and Fireblock are actually, um, taking now. But there's, there's still a problem with that because there is a, there's a centralized party to that. like I mentioned when I was explaining how Web3 Auth works, one of your key shares is managed by the Torus team. So there is still room for it to be compromised, right, if the Torus guys are actually bad actors, right? So although it will be difficult because they don't have access to your, your browser to get another key share that they can use to compromise your uh, what's it called, your account. So we still have a very long way to go when it comes to getting the decentralized, um, wallets to work the way we would love it to work. Because to onboard the next billion users, there is a need for us to- you can actually come up with a fusion of all these things I have mentioned, and you would- there is a market for it because still, there's still a struggle with, um, the crypto wallets and the user experience it provides to us. So, um, in conclusion, right, simplifying the user experience when it comes to crypto wallets would actually drive mainstream adoption because a lot of people are still trying to understand why do I have to pay gas, why do I have to manage my key, how can't you do it like the banks? That- can't you provide security for me? I don't- I- once I- once I- my password is compromised, I just want to reset it just the same way we do on, uh, when it comes to NPCs. Then, um, security. Security and privacy are the use of, um, the keys. The keys. So once we can simplify the way the security when it comes to managing our private keys, right? It would actually make a lot of sense. And the future of, um, Web3 depends on making wallets accessible to the ordinary user. So you don't have to be technical for you to be able to interact with, uh, um, the blockchain. So, um, thank you.

16:05 D: Please, a round of applause again for him. Thank you so much, John. And I'm sorry I got your topic wrong, but I think we should look at the bright side, are we? Oh, okay, okay. Someone has a question for you, sir.

16:34 B: So I wanted to ask, like, for account abstraction and others, the MetaMask doesn't need to come up every time for user to sign interaction, right? Right. Is that correct?

16:49 A: Um, so, um, there's no implementation of AA on MetaMask currently.

16:55 B: Okay, more like the user doesn't have to like explicitly sign interaction all the time.

16:59 A: Yes.

17:01 B: Okay, so what if like the action is by mistake? Like these are clicked by mistake or something, so these are keep paying gas fee, all that.

17:12 A: So, um, when it comes to- sorry, I didn't get that. When you mistakenly do what?

17:18 D: What if- okay, now I feel like MetaMask, or for example, I'm using MetaMask as an example, it makes us sure like you want to do this. Now with the making it- making a good user experience whereby the wallet doesn't come up all the time for you to sign it, transaction. What if the action was a mistake? Like, what if like you clicked on the button by mistake? And it's all I'm trying to say. Yes. And then you keep, keep paying gas fee every time you make that mistake.

17:46 A: So like I mentioned, right, when it comes to AA, it's a fusion of externally owned accounts and smart contract accounts, right? So sometimes, most times, you actually initiate the transaction from your externally owned account. It's just you use that one to initiate the transaction. The transaction is done by the smart contracts, um, the smart contract wallet itself, but you need an externally owned account to initiate the transaction. So that's the current implementation that we have. Maybe tomorrow there might be an improved implementation of that, but for now that's what we have. You have to even- you have to instantiate the, um, the transaction by your externally owned account. The only upside to it is that you can actually change the externally owned accounts that is, that is connected to, um, the smart contract account.

18:39 D: Okay, I hope that was okay. Hello, hope you're satisfied with that. All right, and that question- okay, we'll take just 2 more questions and we round it up.

19:02 B: Yeah, um, thank you for the discussions today. So my question basically is on, um, account abstraction. So, um, I think yesterday a speaker gave similar, but he talked about paymasters. Okay, sorry. So he talked about paymasters, right? And he was saying something around paymasters that, um, let's say you want to build like social media on Web3 and you don't want users to like kind of always pay, right? You can connect it to a paymaster and then the paymaster will be the one to sign transaction on behalf of- so, but my, my thinking now is, are you the one to fund the paymaster to carry out all those, um, or how does the paymaster really work? Yeah,

19:46 A: all right. Um, paymasters are actually, um, for platform that wants that wants to, um, give you like, um, a gasless, a gasless, uh, transaction, right? So they actually pay for the transaction. So you get- so you approve the paymasters to actually sign your transaction, then they pay for it, right? There are different approaches to it based on your own implementation, right? So if I want people to just fund um, the paymaster, then based on maybe subscription, maybe you fund your paymaster 1 ETH, then you can actually carry out X number of transactions for that particular ETH. So it depends on the, um, the implementation by the, the guys that, that, um, actually runs the, um, account abstraction. So it depends, right? Ideally are supposed to pay for it. But some platform, like you said, maybe a social media platform, and they want to give you a seamless feel, a seamless UX, then they pay for it. So it depends. So, but most times the paymaster is actually the, the, um, the, um, from the owner of the platform. So they just carry out those payments on your behalf. So it's gasless because someone else is paying for it.

21:09 B: Hello, sir.

21:18 E: Good morning.

21:18 A: Good morning.

21:19 E: So my question is, um, for the account abstraction, yeah, for the transaction, are you doing like if you initiate the transaction, is it the part of the key you will use to send the transaction, or like they are doing to send the transaction for you after initializing?

21:36 A: So come again, please.

21:38 E: Like, I'm asking about the account abstraction. You said that like something like MPC.

21:43 A: Yeah,

21:44 E: the, um,

21:44 A: MPC is quite different from AE.

21:46 E: Okay. Yeah, let me say, uh, if you are signing the transaction, if you call the smart contract for the account abstraction, are you the one any- like, uh, is your key the one that will sign the transaction?

21:58 A: No, it's the Paymaster.

22:00 E: It's the Paymaster. I'm not talking about the Paymaster implemented one. Like when you call the transaction, you call the smart contract. Yeah, you are supposed to sign the transaction. But yeah, so what I'm asking about is like he is asking about MetaMask will not- you say like MetaMask will not pop up when you like sign the transaction. So am I the one signing the transaction or are they the one signing the transaction for me?

22:21 A: So the transaction is that you are actually interacting with your smart contract wallet, right? So once you do that, it's just like calling a smart contract calling another smart contract. So you are interacting with your own smart contract wallets, right? Then the smart contracts initiate

22:42 E: another

22:42 A: transaction, which means

22:44 E: you are the one paying the gas

22:45 A: fee.

22:45 E: Yes, that's what I'm trying to get. Thank you.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.