Next year will be such a breakthrough for Ethereum UX and security that it's hard to put into a single tweet all the benefits we'll get. Key rotation, native multisigs, huge security advances via transaction assertions, native post quantum signing schemes, ...

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.

ok someone finally deployed the DAO proposal to add 0.01, 0.03, 0.3, 3, and 30 ETH Tornado Cash pools (we've asked the Tornado Cash community a few days ago to deploy this if anyone thinks it's valuable); personally i strongly second this proposal as it will help retail users and increase usage (particularly the 0.01 ETH pool). i hope the DAO voters see the merit of this proposal and will accept it.

imho one critical missing piece for tornado cash to become more usuable on a _daily_ basis is having a 0.01 ETH pool. we could simply clone the existing working pool code, adjust for 0.01 ETH (only nit adjustments needed actually), and make a proposal to governance (so the pool can be registered via the official router) that (CREATE2-)deploys this pool when the proposal is executed and we're good to go. ui code would need an update as well, but this is solveable. (and after this happened we dissolve TC governance 😉, but this is another topic lol). thoughts?