Content
@
0 reply
0 recast
0 reaction
mattdesl
@mattdesl
Considering the importance of client diversity in Ethereum, it’s wild to see the casual acceptance of WalletConnect’s centralizing forces…
2 replies
0 recast
16 reactions
mattdesl
@mattdesl
Every dApp needs its own WalletConnect projectId now, conveniently only generated by signing up to WalletConnect’s servers. 🤦 How did we get to this point and what happened to the goals of decentralization?
1 reply
0 recast
2 reactions
kencomsuner
@kenconsumer
This is interesting. I never thought about it like this. I thought of WalletConnect as a good service to help keep it as easy as possible for regular users. I never realised it forced users to use their servers because I never thought it through. What wallet do you suggest using that doesn't require this setup?
1 reply
0 recast
2 reactions
mattdesl
@mattdesl
I think when I first used wallet connect it didn’t have this projectId requirement and felt more like a protocol; now it feels more like a tech startup with multiple ventures. From what I can see, eip-6963 seems sane but only for browser extensions, doesn’t seem useful for mobile
1 reply
0 recast
1 reaction
nix
@nix
The WalletConnect URIs are specified in https://eips.ethereum.org/EIPS/eip-1328. Notably, v2 seems to have removed the ability for dApps to specify their own relay server; now, the wallet connect relay is enforced.
1 reply
0 recast
0 reaction
mattdesl
@mattdesl
How is anybody in eth ecosystem ok with this ?! 😵💫 absolute centralization
1 reply
0 recast
1 reaction
