Dimitris
@jimouris
Head of Cryptography @nillionlabs building @nillionnetwork PhD Cryptography & Privacy. Ex @Meta, @AWScloud, @AthenaRICinfo. Opinions are my own. he/him
Simple idea: a server between the wallet and the RPC providers. The server randomly uses a different RPC for each request. Run this in a TEE 🔒! The cloud doesn't see your requests (careful, they still metadata!) - and the RPC doesn't see your IP (they see the cloud's)
Hilarious and engaging, lucky students!
Interested to learn more about my applied cryptography course? Watch this video! youtube.com/watch?v=2R8dKA…
IMHO we’ve lost this battle many years ago already when having to rely on external RPCs (rotating or not) become the norm instead of making it easy to run your own RPC. damn, even so called “educators” in this space don’t run their own nodes and the first thing they teach…
Using a single RPC for all the requests from your wallet reveals too much. Rotating RPCs for enhancing the privacy of Ethereum! Split your requests across multiple RPC providers so that no single provider sees all the history, patterns, and requests you are making! I…
@PrivacyEthereum recently posted an article about Ethereum privacy of reads: pse.dev/blog/ethereum-…, three techniques: • PIR: Unfortunately, still slow • TEE+ORAM: hardware trust + somewhat slow and expensive ORAM techniques • Rotating RPCs: **Keep reading** ⤵️
cooking up a little @nillionnetwork blindfold encryption demo 👀 lmk if you want an early taste
What a shitshow.
TLDR the Tea app stores everyone's photo and ID enuncrypted in a public firebase storage bucket. Hahahahahah. Was this vibe coded?