Content
@
https://opensea.io/collection/evm-6
0 reply
0 recast
2 reactions
Colin
@colin
Why did it become standard for all developers and wallet infra providers like @privy to call “injected browser wallet” just “MetaMask” instead of the actual name of the wallet? Laziness, preventing user confusion, etc? Not surprised Zerion is taking drastic measures in response
5 replies
0 recast
2 reactions
Max
@segall
We're actually shipping a revamp of our connector flow this week to clean up the wallet crossfiring! Lots of new stuff coming (eg devs can configure their wallet lists, dedicated space for a user's preferred browser wallet), and EIP 6963 compatibility helps a ton https://eips.ethereum.org/EIPS/eip-6963
0 reply
0 recast
1 reaction
Giuliano Giacaglia 🌲
@giu
I think this is really hard to handle. I think @dynamic has been pretty good at this. They built a full-system around this. Cc: @itai
0 reply
0 recast
1 reaction
Furqan
@furqan
Takes extra effort to get each wallet provider identified correctly. Something we focused on but took a bit of work.
0 reply
0 recast
0 reaction
Henri Stern Ꙫ
@henri
Lots changing fast in the wallet connector space! Our goal is to provide devs good defaults for users with ability to override to customize for their app's use case. Important to balance what the user expects vs what the dev wants and also not break others’ tools. But in that order: user > app > other infra
1 reply
0 recast
0 reaction
julien
@julien51.eth
Unfortunately "injected wallet" is really hard to understand for normies...
0 reply
0 recast
0 reaction
