In secret, Silicon Valley & venture capital stresses “AuDHD” as an ‘optimal human cognition stack’.
SLMs and agent swarms uncover a deeper truth within cognitive science: the synthesis of “AuDHD” + “DID” as a 'complete' form of cognition to model "AI".
Wow, major respect for @EliBenSasson, you are a legend, but 90% of this post is bullshit.
The sad part is that's not ignorance (he is a genius), but just narrative games.
Wish we'd be able to focus on actually building the privacy space, rather than 💩ing on eachother
Overview off all privacy events @EFDevcon 🇦🇷
Nov 16, @web3privacy Cypherpunk Congress #2
Nov 17-22, Privacy district @ Devconnect
Nov 17-22, Privacy Hub @ Devconnect
Nov 17, @0xMiden Privacy Salon
Nov 17, @RAILGUN_Project Private Party
Nov 18, zkID and client-side proving
Nov 19, zkTLS @PrivacyEthereum
Nov 19, Encryption Day @fhenix
Nov 19, Privacy & Compliance summit @partyactionppl
Nov 20, Noircon3 @aztecnetwork
Nov 21, Ethereum Privacy Stack
Nov 21, ZK Real World Summit @zk_monk
Nov 22, Applications To FHE
Nov 22, Obfuscation (iO) Day
Nov 22, @Waku_org Privacy Hacker lounge
Links below ✨
Surprisingly, even for someone who once failed calculus, implementing a mathematical crypto paper isn’t as impossible as it sounds.
At first it feels daunting: a paper by brilliant PhDs I’m lucky to work with, full of overloaded letters and strange symbols (^, ~, ′). Feeling lost at the start is normal.
The mindset that helped me:
👉 You don’t need to prove why it works right away, just know what each step does.
Kickoff
Let the experts explain the theory. Build a common language. Don’t chase the “why” on day one, if the spec says add x and y, trust it’s there for a reason.
Cheat Sheet
Write a slim summary in your own words. Drive the discussion, ask every question, and make each step crystal clear. No dumb questions.
Validation Points
Crypto algorithms are tough to validate until the very end. Break that rule. Add checkpoints along the way so you know exactly where things break.
Quick Demo
Before “proper” engineering, hack together a scrappy version in your easiest language. Make it run, confirm you understand.
Ship
Now you’re shockingly well-prepared to build the clean, efficient version.
Bonus
By the time you finish, you’ll realize you do understand the “why.” Not PhD-level but enough to feel like you’ve conquered something you once thought impossible.
And here I am: two weeks after thinking threshold decryption was pure voodoo I’d never deeply understand… I’ve reimplemented the entire protocol and I actually know why it works the way it does
@fhenix #FHE
in the eth space, we largely consider privacy a meme.
however, most people care about privacy w/o realizing. I teach intro cybersec camps to youth, and use this diagram to show how we like keep certain info private.
try filling it out yourself!
We're co-hosting Encryption Day with @arbitrum, @fhenix, @Optalysys and @silhouette_ex!
Let's spread the love for privacy tech at @EthCC 🇫🇷
3rd July 2025, lock in the date! 🔒
Registration & details ⤵️ https://t.co/5ZyJatxrpS
@serotonin_hq Encryption Day: Cannes by @fhenix
Just a short walk from EthCC. Dive into applied cryptography—ZK, FHE, MPC—and their role in creating private, secure Ethereum systems.
Join us for our 4th Encryption Day with researchers, founders, and devs!
RSVP 🎟️ https://t.co/trpPJvoLgE