AllWalletDevs #17
AllWalletDevs · October 2023 · 18:39
Call 17 of AllWalletDevs, held in October 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
sounds good so um everyone thanks for the opportunity for this all wallet def uh I want to come back to a topic that I present in this um meeting last time uh can I share go share screen uh so basically the concept is that uh we we realize that the threat of fishing is the problem and um we have seen industry using ER let's say uh eth 2.0 deposit contract has eight zeros Unis swap has 10 zeros increasingly open C
have 13 zeros so traditionally wallet will show the address of open c as this uh and if it's shortened it will look like this and it doesn't help much um with only four zeros showing up and then add last one because anyone who want to fish can still create this and so it would be ideal if we can come up with some way to show the length of zeros and then the four starting four ending it will make the uh fishing this much uh harder and so I'm gonna uh so that's why I'm want to bring it to to today's meeting uh for a way to to propose one way um to show the wallets in a shter way when they're multiple leading zeros
I don't have a good name for small address uh or rare address but basically you get a you you get a point um so suggestion will be greatly appreciated uh of what how what how do we call these kind of address and how do we better show the address I'm just proposing this um as a way to get inspiration so you're suggesting putting a 13 in curly braces before the X I don't have a good idea about how it could be best present represent um but I think it would be good if we can account let the short form account for the fact
that it has a lot of zeros so maybe this is not the best way I'm asking the participants what is it a good way or if if there's other opportunity uh ways to represented but in at first I think um is it a good idea to represent these many zeros where the fact that there are a lot of zeros and that's the first question I want to ask the the audience the the participants so uh what I would say on that is that you need to have a a useful um reference for how many zeros it should have displayed elsewhere because otherwise a user is still going to click through because they're not cognizant of
how many leading zeros there should be yes that's true yeah it's the that's why I think a standard will be helpful because if everyone is um just deciding to use the same way to represent it when users see references from other side let's say they see it on their wallet and then they go to Ether scan if they both shows to be represented in the same way then user can can better compare but if user aren't seeing it out elsewhere if only one wallet is implementing this short form or any of the short form then user wouldn't even be able to know I think this is you know kind of a
general problem because just shortening addresses at all has this issue right like if you cut out the middle part of the address and only display the first four and the last four or something along those lines like you still need a way to check the whole address you know what I mean so like I don't know if we want something specifically for zeros or if we want something that works for for just shortening addresses generally so [Music] um yes you need other way for user to check the full um the full length and then ultimately I think uh the domain
names is a good way um but uh in this particular case solving one problem at a time I think um if we can come up with a standard way to represent at least zeros which is the practice that that the the industry is picking up then we solve the problem the partial solu with partial solution better than it it is right now and at least help some of those legitimate projects so let's say if you even if you only display four
characters like two before and two after if you have 13 zeros you have to mine 13 + 7 to make it look like the same um and that's very very hard that's like 16 to the um to the 16 to the 17 uh large number yeah it's true I mean I don't really have any particular input I just think it needs to be considered that's all um yeah yeah hey guys uh sorry can you hear me je has to rejoin because I
didn't have microphone permission yeah we can hear you Lou all to have you back perfect perfect hi um just a bit of intruction this is the first it's the first one that I'm I'm joining um I'm fivo from a protocol that's called mean mean Finance uh we do DCA stuff and just cool stuff around go three um so I I wanted to uh chime a little bit in about this uh so talking about uh showing addresses to users is uh when we talk about the ux here I
think it goes a little bit beyond just showing a bot TR exod decimal numbers that the most common user is not going to be able to recognize anyway right um so what I think we we as a community as as a the community should aim for is to try to start hiding addresses as as much as we can without being without letting the users not verify them right so in this example the uniso permit uh contract um I wouldn't like to show the
user ZX 000000 stuff I would just say hey you're interacting with the unop contract if you want to click on it I can show you the full address for that so you can verify that is actually the contract you want to interrupt um but I think we should that's start try a need to uh to not actually shortening addresses because that's just the same problem that we have right now where you see an address on you to know what it's linked to uh but maybe yes letting the user go yeah sorry yeah yeah I I I think I we are in uh very much agreement with that um the
problem is that um you will there will be Fisher who comes out and says hey we are permit to and so can you use us and approve with us to interact with Unis Swap and then take your money and we're trying to solve a problem in a lower level when officier comes up and says hey we are Unis swap permit too and then actually we have a address that looks very similar to Unis Swap and that's the problem that's the problem we're trying to to to solve today yeah yeah 100% I I I agree with you on this um so I think this uh this
problem specifically is where do we tackle it right so who should be tackling the issue of how we show how we display addresses uh should we leave that responsibility to uh the wallets there are the the end users um Final Approach into either confinment a transaction signing a transaction signing a message etc etc etc or should we leave it up to each specific um application to handle I think it should go into uh the wallet space right so each wallet should try to keep up to dat as much as it can because it's really hard to um to at least the
most known protocols and what their contracts are so we can so for example if metamask I'm interacting with the the Unis perit to contract I would love for metamask to tell me hey you're interacting with the UN permit to contract and if I go into a patient site and they say hey you're about to interact with uh unof permit to and I click to sign a transaction or whatever and my metamask model pops up uh in my meta Mass model it shouldn't say unisoft permit 2 anywhere else right uh so that's kind of the point I'm trying to aim for
um I don't think I have the right solution for this I mean I I don't know if there's a silver bullet to handle this like where should it go I think it should be like more of a joint effort between both like apps should be able to uh keep their own registry of what is their identifying to a specific domain for example for me too and also uh what it should try to maintain that record too it's hard I know I I don't see how we could improve this uh I I agree with you it would be good for the wallet to also um support that and then I think that's a a
separate solutions that we can also consider and there's nothing preventing with with us from Sol solving the both and then it take time for the mass adoptions of all all those wallets to also have their own list of legitimate um projects that they think yeah so and then we still as a decentralized and permissionless space we still want user to be able to verify at the end of the day right we're not like uh Twitter and who says hey uh if we Twitter consider this is illegitimate we will take you down and the user of tter should not be interacting with it this is permissionless so at the end of
the day it's up to the user what they want to interact with and they need to have a way to veridate this yeah so I think I love to hear uh wallet Builders uh what your thoughts uh about having a way to show the address for users who easily compare um the contract or the wallet they're interacting with with the one that they intend to I mean maybe the recommendation should be that you don't display shortened addresses so either you display uh like a name that the wallet provides or you provide the full address and you you just never show shortened addresses um effectively that's a that's
a way to do it uh it's just that if I swap one address from here user is still very likely to um to Mis mistaken them right so if if it's a very long address and then I swap I I manage to make it very uh similar to yours user can get confused and the longer the address are the longer it is going to be easier to confuse user just like how you never so back in the day people will display summarize of uh the use the term of use of a website for user to
understand them before they click yes and then I think the current General approach is that they will show the full thing and so user will never look into them so there's a there's a uh trade-off we made when we show the full TX versus um and whether user will look at them um not to pass any value on you know if we should implement it or not but um maybe just a general comment about the idea there's a lot of zeros in um like vanity type wallets but there are other um you know value that are repeated so like multiple ones multiple
of a letter something like that um so the approach that you took right now is 013 and then the part of the uh address that comes after it it might be beneficial to keep the zerx and then just compress the parts that come after that and are redundant I that's that's a very helpful suggestion so something like maybe something like this right yeah and and this way it could work on anything um different address yeah I I still think it's ill advised to
give the shorten address but it would be better to do it this way than maybe another yeah um I I it's generally people don't short them at all uh it's that they will highlight for example a lot of our address will highlight the part for user to at least check so they say if you don't have time to check every single character and make sure you're not reading the shifted uh the shifted um characters at least check these eight the top four and top last four and yeah I agree if user can do it every time that's great and so I I'm all for uh showing the full address uh it's
just that yeah we we also find that user don't look at them at all I mean I feel like this should be something we can we could do empirically make a like a little web page that compares different ways of shortening addresses and find out which ones people are the best at uh like you know telling the difference between because I I don't don't think we can just like guess at what the safest method is going to be because like like shortening it at all is going to be a problem so right right yeah and also yeah sorry I I cut it off go ahead no I just said that I I agree with
that like um shorting adter is always going to be a risk U no matter how we short it how how we want what do we want to do it or what not it's always going to be a risk because you're not looking at the full address and even if you're looking at the full address it's very easy to uh not see like a little difference between number a letter um an uppercase lower case just because I I get confused for example between the the ey and the I sorry English not my my native so a little trouble uh pronouncing the the Bost but yeah um yeah I just
thought yeah yeah I agree there's the the way to show them is not perfect right now and also uh we can have more uh we can ask for more suggestion on how the better to show the the short pH but in general we will advise user that um it's better that they compare entire entirety um yeah so this is just here to uh to put before all the wallet developers because I don't know any other better uh venue to talk about this thanks for hearing me would you like um a Discord channel for this maybe I I find it much easier to get feedback like asynchronously from this group yeah that would be great uh inside
of wallet uh ethereum wallets right yep I'm honored it's a warrant a separate uh Place very legitimate cool um I think that's everything we had scheduled again uh little notice at 6963 has gone to final so if you're a wallet implementor take a look at it um it lets you
have multiple Wallets on the same page um and with that I guess that's the end of uh this meeting thanks everyone