Content
@
https://warpcast.com/~/channel/privacy
0 reply
0 recast
0 reaction
polymutex
@polymutex.eth
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.
5 replies
3 recasts
17 reactions
Roadu 🎩🦊
@roadu
im not a expert but it seems like addresses as identities are so core to evm stuff that it would require a whole new vm (maybe cairo or another like that) to accomplish this
1 reply
0 recast
1 reaction
𝑶𝒕𝒕𝒊🗿✨
@toyboy.eth
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.
1 reply
0 recast
2 reactions
Philip Sheldrake
@sheldrake
Thanks for setting the example in using “identifiers” and not “identities”. We will abstract away from identifiers. Forgive me for sharing this again … 😊 https://ethereum-magicians.org/t/a-maximally-simple-l1-privacy-roadmap/23459/29
1 reply
0 recast
1 reaction
丂ㄒ卂尺乃ㄖ爪乃
@starbomb
Testnet launching soon🪬 https://aztec.network/
0 reply
0 recast
3 reactions
Sebastian Bürgel
@scbuergel
Maybe we have to reconsider paradigms in order to get to acceptable levels of practical privacy. Here Kyle argues that web apps "being in charge" is effectively just as horrible wrt privacy as cross origin tracking on the web: https://kyledenhartog.com/recreating-web3-cross-origin-tracking/
1 reply
0 recast
0 reaction
