AllWalletDevs #16

AllWalletDevs · September 2023 · 8:04

Call 16 of AllWalletDevs, held in September 2023. Wallet developers meet to coordinate on the Ethereum standards and protocol changes that affect their products.

Topics

From AllWalletDevs, hosted by ECH Institute.

Transcript

welcome to all wallet devs don't think we have a ton on the agenda this week or this month but um yeah we can hang out and chat a little bit and uh if we run out of things to talk about we can meet again next month um I'll kick this off with a little bit about wallet test framework um we've kind of been quiet since the last update um not a ton to report uh we have a few changes that we're getting done in Geth now um to support uh each call without a block number and I think that's um pretty much the only the only major update with WTF which to plug you away on tests and uh yeah we're looking for

integrators if um any of you are interested to use wallet test framework in your own CI uh let me know um and with that if anybody else wants to talk about anything please feel free hey Victor I I didn't anticipate that was so fast in your updates so I was about to cook up some uh some examples for my proposal but uh since there's no other uh update or it's open for I just sign up um so the proposal here is that we're trying to address the problem of address phishing uh which I can give an example

here so generally uh there's probably a common problem of wallet user when you see a long address you don't know whether they are your the address that you intend to interact with or the one that you trust of course there are other ways that can be can be solved to can be used to reduce the potential of phishing but it would be nice if the developer of wallet Community could come up with the solutions to find the way that we will agree to shorten the address one of the way is to so as we see in the existing approach

the ens the 2.0 is using a few zeros in the front and then uni swap is doing similar things so one way to think about it is we can have the number of zeros represented and then a shorter version maybe like two digitron two digit or even just the first four digit or ending four digit would be good enough um so so long as we make it hard enough to generate these amount of zeros um and um it takes long enough time then um adding like even two more uh two more accounts uh adding even more two more characters so of hack screen is

60k harder than generating those zeros assuming this is one day like you take the current uh time of one day to generate um two more digital uh two more characters will take 100 years to do that so four digits plus a number of zero could be one way one easy way to we do to make it super hard to fish uh addresses so this is a general concept um just wanna like put on the table for people to to give feedback and if people like the idea or not like the idea we can come up with an alternative but I think some kind of standardization would be helpful to avoid phishing in general

and so with that um hope to borrow some wisdom from the wallet Builders here so the idea is to make it more expensive to fish or yeah or harder to fish so for example we can we can make this address display them in a standardized way where you can say something like 13 0 and then Ace ADC 0.

so if we display it in this way anyone who has a lot of zeros in front will benefit from this um and then it can make them make anyone trying to fish it much harder as opposed to currently the currently people are coming up with their way of displaying random address like this would be in in currently it would look like this right and so anyone who is who wanted to could

spend some hours of engine of authentication and then mine the same one that looks exactly the same in the first eight and then last eight of the address so I think coming up with um like a series of recommendations or guidelines on how to display uh addresses is a great idea um like you should always display them beside like a blocky or some visual representation like that's that's a decent idea um maybe having a short form notation for repeated characters like at the beginning or end would also be useful [Music] um and always be able to see the full expanded address

not not naming anybody in particular um but yeah that that would also be a a good recommendation um I I'm not a wallet developer and I'm not a UI expert so I I can't really say more than just those General bits of feedback but I think having some document is probably a good idea [Music] to anyone else uh I I'm taking down the feedback from uh from Sam oh

if not then uh thank you for the feedback I'll come up with a document and then post on the theme on the forum for uh asynchronized feedback Sam giving back the time sure um so I guess uh another thing that's kind of come up that I can talk a little bit about uh the EIP editors are kind of restructuring how they um organize documents and we're creating this concept of working groups and I think it would be beneficial to wallets to have one of

these working groups to work on standards and documents like these guidelines that um Victor was talking about so I think um if anybody's interested in in maybe talking about how working groups should look if they'd like to participate in the governance uh please reach out to me I mean I'm happy to have as much or as little help as possible on this so uh yeah cool so I guess we could just hang out for a few minutes um feel free to chat or do whatever and if not then I guess this is the end of the official meeting that was