willscott

@raulvk Excited to see what you pick up next!

Ethereum's roadmap got real in the last 12mo: PQ, scaling, latency, privacy, AA, minimization, hardness. A lot hinges on p2p networking. A few weeks ago I decided to leave the EF to keep advancing this layer from the outside. Last week was my last day; the end of a memorable chapter in the arena with some of the most principled, humble, and talented people in this space. The Protocol cluster is in great hands with @corcoranwill, @kevaundray, and @fredrik0x. The work continues, no time to skip a slot. Core Devs got pilled on ethp2p at interop, and so should you. 👇

One week left to submit an idea or grab an earlybird ticket at a lower price! July in Alte Hölle for @GETDWeb Camp is going to be something special ✨

𝗗𝗪𝗲𝗯 𝗖𝗮𝗺𝗽 𝟮𝟬𝟮𝟲 𝘁𝗶𝗰𝗸𝗲𝘁𝘀 𝗮𝗿𝗲 𝗼𝘂𝘁! 🎉 ⛺ Join us at Alte Hölle on 8–12 July to shape the decentralized, democratic, and open tech we truly need. 💡 Submit your proposal and take part in the conversation! 🎟 Tickets + CfP → dwebcamp.org

@raulvk There will likely remain value in getting to “consensus” on shared protocols. Having known ways to negotiate that lots of others also speak is useful for efficiency if nothing else. The question then is how much more is gained from reference implementations or other buy-in

serious question: do (A)GPL licenses still make sense in the age of agentic/vibe coding? the point of copyleft licenses is: if you use my code, you have to open-source yours too. it encourages contributing back and spreading openness, instead of leeching and turning something proprietary. in the past, when a company opted to copy without honouring, they'd have to go to great lengths to ensure clean-room implementations. this severely narrowed the pool of companies willing to risk it. but today, you can just point an LLM at a copyleft codebase, have it reverse engineer its behaviour into a neutral spec, and then have another one implement it from scratch. the main barrier to copying without GPL obligations is gone. IMO, the only place where the moat remains is large, complex codebases (a) embedding decades of battle-tested knowledge that (b) run in mission-critical scenarios, e.g. Linux, MySQL, Git, etc. for smaller ones, copyleft won't stop people from just reimplementing their way out of the obligation. the whole OSS licensing model was built for a world where code was expensive to write. we're rapidly leaving that world. we're starting to see the effects with "vibeforks", OSS companies going back to closed source, etc. i wonder what comes next, and how it connects more broadly with the era of personal, on-demand software.

@zemnmez Takeaway is don’t sleep for more than 32 hours at a time since you’ll die if your heart rate goes to 0

slept for 12 straight hours until my alarm went off and my heart rate just kept decreasing

@raulvk You're motivating the embedded relaying by 'validator privacy', but how are you planning to address the ongoing needs for client and end-node network privacy?

➡️ docs.google.com/presentation/d…

Why P2P matters: How Ethereum talks to itself. And a preview of what's next in the Networking roadmap. Recording out soon. Slides below. Thanks @Bankless!

Our first individual member! @willscott Pure human, hacktivist, always willing to help, support & be there with us. So greatful. youtu.be/arW5Y4dxp90?si…

What does user ownership of data really mean in the age of decentralized systems? 🛡️Join us for an X Space on data privacy, personal sovereignty, and digital identity. 🎙️Featuring voices from the @ethereumfndn and leading privacy researchers @andyguzmaneth and @willscott.

1/ We’re back! Join our next meetup on October 9! 🗓️ Open to all, from newcomers to long-time community members and devs. We’ll dive into fundamentals, privacy, digital rights, and ecosystem updates. Let’s reconnect, learn, and explore together! Details & RSVP in the 🧵

@tabcat00 Carpe diem!

i get feeling i should do something and then don't. feels like a sin most of the time.

trying to take more action on gut instincts. this is the will to act. fudging heck im a coward sometimes.

@lex_node @ArweaveEco @irys_xyz IPNI is a bridge that some large publishers to IPFS have used, but the IPFS DHT has continued to work without issues. IPNI as well has been recovering over the last week.

what's the best decentralized/autonomous document storage solution tied to hashes? IPFS seems to be having a lot of problems (see hackmd.io/sRmr-vnPRH2THa…) other stuff suggested to me: -- @ArweaveEco ? --@irys_xyz ? any others people like/use?

@mr_ligi @web3privacy @IPFS @EthereumList You said "For sure only reading stuff enabled." - but it sounds like you want the ci bot to have read/write. check e.g. github.com/ipfs/pinbot-irc for something kinda close to this

@willscott @web3privacy @IPFS It's for the icons of @ethereumlist - these are usually quite small - if this is what you mean with scale. But I think I will just rewrite it to go via http gateway and not IPFS node only. Was mainly interested if something like this exists. Thanks anyway!

Is there any public @IPFS node (not gateway - means something with port 5001 open)? For sure only reading stuff enabled. Would need it for a CI job where it would not be feasible to start a node every time the CI runs

@web3privacy @mr_ligi @IPFS what sort of scale of content do you need to access? If you want to be able to pull from a single public node content it doesn't already have pinned it will need to be in gateway mode, even if it doesn't have the http interface on.

@mr_ligi @IPFS @willscott

The chaos congress persists each year as a view into an alternative world of technical co-existence. It’s inspiring to see so much creation.

@OSObserver @RaymondCheng00 @Optimism Congratulations for impacting the thinking in this space a lot in a short time!

We are extremely proud to be the top recipient in the analytics category for @Optimism's latest round of retro funding. We are also humbled to be in the company of so many exceptional teams & individuals working to improve Optimism governance. Thank you 💖💖💖

More info on the ruling: The Fifth Circuit has found that Tornado Cash smart contracts do not constitute property, finding that Tornado Cash software is not covered by the IEEPA's authority. The court found that OFAC overstepped its authority by placing Tornado Cash on its Specially Designated Nationals and Blocked Persons List. The court found that while "OFAC’s concerns with illicit foreign actors laundering funds are undeniably legitimate," "perhaps Congress will update IEEPA [...] to target modern technologies like crypto-mixing software." "Until then," the court found, "we hold that Tornado Cash’s immutable smart contracts (the lines of privacy-enabling software code) are not the “property” of a foreign national or entity, meaning they cannot be blocked under IEEPA, and OFAC overstepped its congressionally defined authority." This is a developing story – we'll update both the article and this thread as we go through the information available 👇 therage.co/fifth-circuit-…

Our first @EFDevcon educational session x Hacktivist hub: Censorship circumvention by @willscott 14:00, at Hacker cave x Hacktivism Hub, today. powered by @costgallo, @PG_CDG, @SCBuergel, @ManuAlzuru, @0x_m_f

*The* decentralized protocol and infrastructure conference is back! Announcing: 𝐏𝐫𝐨𝐭𝐨𝐜𝐨𝐥 𝐁𝐞𝐫𝐠 𝐯𝟐 June 12-13, 2025, Prenzlauer Berg, Berlin.

Happy Chusok It's been a fascinating decade since I took this photo in Pyongyang.

@hyprturing The segment of market that's able to 'shop around' seems like it may be small enough that it wouldn't really be able to threaten relative advancement?