Context and Chronology

In a concise public note linked to his social feed, Vitalik Buterin reframed Ethereum as a builder of “sanctuary technologies” — open, resilience‑oriented systems that prioritize privacy and user autonomy over productized polish. Unlike a protocol specification, the post is an organizing signal: it ties high‑level goals to a visible 2026 campaign that developers and foundation planners are actively sketching out.

That campaign pairs normative shifts with concrete technical trajectories already discussed in developer channels: inclusion‑enforcement proposals (commonly referenced as EIP‑7805 or FOCIL), account abstraction follow‑ups (e.g., EIP‑8141), and a push to widen who can verify the chain through lightweight clients such as Helios and privacy frameworks like Kohaku. The roadmap language used in planning conversations includes H1 2026 coordination points (nicknamed “Glamsterdam”) and later forks (sometimes called “Hegota”) to stage capacity, UX and consensus changes rather than landing them all at once.

Technically, the package mixes several strands: mempool privacy (encrypted or delayed‑decryption submissions and anonymized routing), randomized inclusion rights to blunt centralized sequencer capture, ZK‑friendly execution and storage primitives, and post‑quantum (PQ) readiness work with multi‑client devnets. Public planning discussions have floated materially higher block gas ceilings (community targets have ranged from ~100,000,000 toward figures near ~180,000,000 gas) and exploratory ideas such as a lightweight “Beam” execution path or RISC‑V investigations to ease future ZK tooling.

Buterin explicitly links these engineering choices to governance and product framing: simplify the base layer by pruning rarely used legacy behaviors (institutionalize “garbage collection”), migrate optional logic into contracts, and build explicit migration tooling so demotions and removals are first‑class upgrade actions. That work is intended to reduce verifier costs, narrow audit surface, and make claims of L1 equivalence by rollups and L2s more testable.

For wallets and UX, the agenda emphasizes account abstraction, social‑recovery designs, and native smart‑wallet primitives so ordinary users can run trust‑minimizing software without leaking metadata to centralized hosts. Complementary infrastructure gaps — oracles, DAO operational primitives and reliable on‑chain tooling — are flagged as priorities for foundations and grantmakers.

Taken together, the technical and narrative package aims to shift where design work and funding flow: privacy‑first middleware, lightweight verifier tooling, encrypted‑submission services and decentralized routing will become higher‑priority pieces of an ecosystem that previously optimized for polished, centralized UX.

However, the proposals surface clear trade‑offs. Inclusion enforcement raises potential operational and legal exposures for validators asked to honor curated inclusion lists; mempool encryption and anonymized routing introduce latency, coordination complexity and the risk that well‑resourced actors could re‑concentrate advantage. Post‑quantum migration is expensive and currently reports only partial cross‑client progress (~20% in some planning materials), so readiness is multi‑year work.

Near‑term effects likely appear in discourse, grant decisions and specification work rather than immediate protocol rewrites. Market actors should watch EIP filings, treasury proposals, and hiring patterns for privacy and lightweight client expertise as the first hard signals. Medium‑term, clearer categories of trust and mandatory disclosure of guarantees could reprice some layer‑2 narratives and shift which teams capture value in the block‑assembly and middleware stacks.