privacy

Farcaster Devs

On farcaster, we will have:

- Custody Address
- Auth Address
- Verified Address
- Warpcast Wallet Address

I really hope we can consolidate these into a single address.

Privacy is required for mass adoption, and cannot be accomplished if users are identified by public immutable identifiers such as Ethereum addresses.

App developers should take note, and not build under the assumption that users can be identified by Ethereum addresses.

Contributor @ /walletbeat.

Censorship resistance requires privacy.

While privacy is undeniably important, it’s a misconception to claim that public immutable identifiers like Ethereum addresses inherently prevent it. In fact, Ethereum and similar public blockchains offer a unique foundation for building selective and programmable privacy, which can be far more robust than traditional web systems.

𝘠𝘢𝘱𝘱𝘪𝘯𝘨 𝘰𝘯 𝘧𝘢𝘳𝘤𝘢𝘴𝘵𝘦𝘳.

That’s fair, and I agree the real issue isn’t Ethereum addresses themselves but the assumptions baked into how they’re used. The “users = addresses” model is a design convenience that’s become a norm and that’s where privacy probably suffers.

Yes, it doesn't inherently prevent it. What does is the currently-ingrained assumption developers might make that users = addresses. If that wasn't the case, there would be no justification for EIP-7702, because users would not be tied to their existing EOA.