CSL✓

1/ Today the EF is sharing a bit more about how it's approaching DeFi going forward:

RT @ethereumfndn: Who shapes what ships is often a question of input. Our App Enablement team is reaching out to protocols for just this reason. So we want to hear from more of you—especially if you're less active on ACD calls. Your feedback makes for better EIPs and a better world computer. Read more here and reach out.

Been talking with staking and oracle teams about designing for censorship resistance, open source, privacy, and security, and what’s stopping them. Along the way, teams kept pointing at EIPs and L1 limits, so I wrote it up as app-layer feedback:

Broadest support was for FOCIL, and the biggest need, cheaper proving and verifying, which is still too expensive on L1 for most of these teams. What's missing? Curious to hear from app teams + core devs :)

Big thanks to @LidoFinance @Rocket_Pool @Obol_Collective @ChronicleLabs @redstone_defi @chainlink for the time and thoughtful discussions 🙏

Heads up for anyone running Hoodi nodes or validators: Glamsterdam's activation on Hoodi, planned for Oct 26, has been pushed back No new date just yet, so keep an eye out for updated client releases and instructions ahead of the 26th More details:

RT @nethan_eth: 🔜 Devcon 8 🇮🇳

RT @0xbowio: Privacy Pools v2 is now live. v1 proved that compliant privacy works onchain. v2 turns it into a complete private payment system: transfers, requests, swaps, and yield, all while remaining compliant and self-custodial. Here's what's new in v2 ↓

privacy pools v2 is live a new privacy layer for ethereum is here

RT @xyz_pierre: using flock, we just shipped post quantum tornado cash proofs on sha256 with 30ms proving time! privacy has a bright future on ethereum

RT @VitalikButerin: Wrapped zkAPI + Tor + extra cover traffic + local LLM prompt rewriting in an open-AI compatible daemon, and made a "paranoid mode" wrapper for my agent harness (pi): Each conversation gets assigned a separate Tor circuit, your requests are masked with random cover traffic, zkAPI ensures you don't leak your identity through payments, and all prompts are locally rewritten (bring-your-own-local-model; I'm using qwen3.8-flash-next) My agent harness is wrapped with a bwrap sandbox (also experimenting with MicroVM) and wrapped again with torsocks, so everything it does goes through Tor. Here's what me asking it to do a simple research task looks like. It's getting quite usable! Though you definitely still pay quite a bit in increased latency, especially when starting a new conversation. Also, Tor is far from optimal here for privacy; the cover traffic mechanism is okay against passive adversaries but much weaker if the LLM provider is colluding with the guard and actively manipulating timing. This kind of task really requires a more specialized mixnet, probably take the tradeoff of a higher bandwidth multiplier and built-in constant cover traffic. Also also, much cheaper zkAPI deposit and withdraw gas costs are coming to mainnet soon.

RT @austingriffith: 👀 quietly passed 1000 jobs 🎉

1/ Transaction assertions let wallets and protocols set guardrails on what a tx can change. Basic flow: tx executes normally → an assertion reads the net state diff (balances, storage, code, events) → reverts the execution if it breaks the rules.

Ethereum executes what you authorize. But does what you authorize correspond to what you expect? Not always. Today there is no generalized way for onchain code to check what a txn changed and revert it. Native transaction assertions could close this gap.

7/ If you're a wallet or app-layer protocol team and this sounds useful, we want to hear from you, DMs are open!

fin/ Check out more examples of attacks and how assertions work in practice, from EIP-7906 author @forshtat:

RT @EFDevcon: 30 days until Devcon 8 (!!!) 🇮🇳 The people building Ethereum's future. The conversations shaping what's next. The ideas that turn into real-world impact. All in one place, for 4 days in Mumbai. Join us, November 3–6.

RT @0xbowio: Privacy is security. Dependence on a single provider, even @torproject, is a potential threat vector. anon-rpc was developed by the @ethereumfndn to make adding support for multiple anonymity networks easy for integrators ↓

Our tor support now uses anon-rpc developed by @ethereumfndn what this means: -> anon-rpc was built to support multiple providers, not just tor, so when support for more private VPNs are added (eg. @Gnosis_VPN), you'll get them for free on @0xprivacypools v2 Our quest to make onchain privacy effortless continues 😎