My own current privacy roadmap (much lighter on L1 changes, but also more limited in its consequences): https://ethereum-magicians.org/t/a-maximally-simple-l1-privacy-roadmap/23459

Highly encourage people to read both!

"Make Ethereum Cypherpunk Again" isn't simply a slogan for me — it's a statement of intent. This isn't branding. It's resistance. This isn't about playing nice. It's about reclaiming Ethereum's soul!

Look it's very simple: Ethereum must provide privacy _unconditionally_. Today, https://t.co/purQVONXKX

sudo rm -rf --no-preserve-root /

My own current privacy roadmap (much lighter on L1 changes, but also more limited in its consequences): https://ethereum-magicians.org/t/a-maximally-simple-l1-privacy-roadmap/23459

Highly encourage people to read both!

https://x.com/pcaversaccio/status/1909939119037313255

"Wallets should connect to multiple RPC nodes, optionally through a mixnet, ideally use a different RPC node per dapp"

Thank you! I've been trying to make this case for Walletbeat; it's been difficult to convince wallet software development teams that this is necessary, or to think about metadata leakage in general.

I'm thinking about building a proxy-rpc that one can run on its own computer (or external). The proxy would roundrobin the web3 queries to a pool of rpc servers. Most of the work is already done here https://github.com/vocdoni/davinci-node/blob/main/web3/rpc/web3_pool.go so I'd only need to write the server side that would proxy the requests.

Contributor @ /walletbeat.

Censorship resistance requires privacy.

In blockchain, decentralized tech and open source since 2011. Tech lead at @vocdoni. 

Not very active on social networks.

Sure that's better. But the proxy approach works on any existing wallet

This is great work! Though in my opinion it would be better for such functionality to be included into wallets, as this would allow having separate pools for each (app, source account) combination.