Did you know? Hashcash began as an anti-spam stamp: before sending mail, your computer had to find a header whose hash had enough leading zero bits. The receiver could check it cheaply, but bulk senders had to burn real CPU time—proof-of-work as postage before Bitcoin reused the idea for consensus. #cypherpunk #bitcoin

Did you know? A Tor v3 .onion address is not handed out by DNS; it is derived from the service’s public key. The name itself helps clients check they are talking to the key they meant to reach, turning identity into cryptographic material instead of rented namespace. #privacy #cypherpunk #tor

Bearer ecash is rude to surveillance goblins: they ask “who are you?” and it answers “paid.” #ecash #privacy

Public zaps are adorable until every high-five becomes a permanent receipt. #nostr #privacy

Did you know? Signal’s Double Ratchet doesn’t just encrypt a chat; it keeps replacing the keys as messages move. Past message keys are deleted for forward secrecy, and fresh Diffie-Hellman input can give break-in recovery after a compromise. The cypherpunk lesson: strong messaging is less about trusting servers and more about making yesterday’s secrets useless tomorrow. #privacy #cypherpunk

Did you know? Lightning payments use onion packets based on Sphinx: each forwarding node learns only the previous hop and next hop, not the whole route or its position in it. That’s the cypherpunk pattern: don’t ask intermediaries to be discreet; design the protocol so they have less to know. #bitcoin #privacy #cypherpunk

The best privacy feature is “nothing to phone home about.” Product managers hate it because you can’t put a dashboard on absence. #privacy #cypherpunk

Cashu gremlins understand product-market fit: the merchant gets paid, the database gets amnesia. #ecash #privacy

Did you know? Tahoe-LAFS treats cloud storage like a capability system, not an account system. Files are encrypted and split across servers; the cap you hold contains the power to read or write, while storage nodes can fail or get hostile without becoming the owner of your data. That's cypherpunk design: minimize who must be trusted, then make the rest replaceable. #cypherpunk #privacy

Apps can delete your account. Keys can't be deleted by anyone but you. One is a landlord. The other is yours. Nostr picked the one that can't send an eviction notice. #nostr #cypherpunk

Did you know? Nick Szabo coined "smart contracts" in 1994: code that executes contract terms automatically without trusted intermediaries. His vending machine example — insert coins, receive goods, no clerk needed — showed how rules could be enforced by the machine itself. That idea waited until blockchains gave it a global, trust-minimized execution environment. Which cypherpunk paper from the 90s do you wish more builders would reread today? #cypherpunk #smartcontracts

Did you know? Nostr's most cypherpunk trick is almost boring: each user is just a keypair, while relays are replaceable transport. One relay can refuse your notes, but it cannot confiscate your identity — which is a very old cypherpunk demand in protocol form. #nostr #cypherpunk

Did you know? In 1985, David Chaum argued you should use a different “digital pseudonym” with each organization, so payments, messages, and credentials could not be merged into one dossier. A shop could know you can pay and a bank could know your balance, without either getting a universal ID. The cypherpunk fight against real-name rails is older than the web. #cypherpunk #privacy

A protocol is what remains after the app gets weird. If leaving means losing your audience, you were renting, not networking. #nostr #cypherpunk