Content pfp
Content
@
0 reply
0 recast
0 reaction

polymutex pfp
polymutex
@polymutex.eth
Building out the wallet details page. 👀
2 replies
2 recasts
14 reactions

Sebastian Bürgel pfp
Sebastian Bürgel
@scbuergel
Oh wtf this is so cool, IDK why "the other social media platform" never brought up your work, thanks so much!
3 replies
0 recast
1 reaction

Sebastian Bürgel pfp
Sebastian Bürgel
@scbuergel
Some random ideas as someone who's passionate about resilience and concerned about wallets specifically in that regard: - can you add "why it matters" for each point under "methodology". Yes, quite some work and you think it's obvious but the next generation of devs will use this page as go-to reference
2 replies
0 recast
1 reaction

Sebastian Bürgel pfp
Sebastian Bürgel
@scbuergel
- can you add a section on "privacy"? Some ideas here of things I find concerning 0. user tracking of any kind = -10 points, user tracking linked to an address = -100 points :) 1. non-customizable non-standard API-calls and hard-coded RPCs (hello Rabby...) = bad, ideally I can control (or at least disable) every (!) endpoint that my wallet calls. That includes token icons, price feeds, custom balance and gas price endpoints, ENS resolvers, etc 2. Allow for non-batched balance requests (to keep your balance unlinked) 3. If the wallet renders NFTs, allow the user to disable that (as it leaks my IP address) 4. Allows for (ideally customizable) proxying of RPC calls (and every other API that's called if there are any additional ones) 5. Integration of shielded pools!
2 replies
0 recast
1 reaction

polymutex pfp
polymutex
@polymutex.eth
Yes, there is already a section for this under each one! I just only expanded it in two sections on the above video, but it's present for all sections. Also going to add a "What can <wallet> do about this?" section for non-green ratings, to list possible implementations.
0 reply
0 recast
0 reaction