Content
@
0 reply
0 recast
0 reaction
Akhil
@akhil-bvs
is anyone solving this problem? or is there a way exists already? to bring all my onchain activity across multiple addresses (ie multiple apps giving me new wallets) under one namespace?
5 replies
0 recast
3 reactions
Vinay Vasanji
@vinayvasanji.eth
multiple attempts at doing this in the last cycle when @so @johanna and I were building everyname we came across several projects trying to do this, the challenge is less about aggregating accounts and convincing the user to do it, but rather getting apps to adopt that namespace at scale there is simply too much incentive for apps to have a native namespace, and extremely easy/cheap to do now with ENS subnames - case in point fnames the other factor is also the inability to do selective disclosure. I certainly don't want someone to be able to see all my wallets, i have a few primary ones where i do stuff publicly but correlating them with the ones i want to keep private isn't something I would opt into the only usecase I can see of aggregating all your wallets with a namespace is potentially a tax reporting solution, where zk or similar is used to keep details private but easy to manage for the end user
2 replies
0 recast
3 reactions
Akhil
@akhil-bvs
yes totally get keeping some of the wallets totally private. i think it only solves for public/social wallets being associated with one for tracking onchain history. opting to add whatever wallet you'd want to add to that is user's call, but yeah then adoption is tough to make it common across everything.
1 reply
0 recast
0 reaction
Johanna 🎩
@johanna
we can not come up with a uniform dev standard seems like all l2s wanted to do their own thing last cycle at least
0 reply
0 recast
1 reaction
