Lion ⟠ dapplion .eth

@trent_vanepps @ProtocolGuild Thank you for everything <3

as of last friday, I no longer work at the EF nothing but respect for the brilliant people i worked with over the last 5 years on network upgrades + funding efforts I intend to continue working on @ProtocolGuild and Ethereum political economy as long as funding is available

Fusaka HF activated and finalized on Gnosis, GG Just a ~6% participation drop, so update your nodes if you haven't!

Gnosis validators update your nodes! Fulu fork in 7 hours 🔥

Ethereum should not adopt the Poseidon hash for the foreseeable future. ZK provers can deal with EL hashing, we it’s unclear the benefit of efficient proofs for consensus clients

Vibehouse: The New Ethereum Consensus Vibecoded Client by @dapplion from Lighthouse Vibehouse is an Ethereum consensus client built almost entirely by AI agents. Forked from Lighthouse, it shipped a complete ePBS implementation in under 72 hours — all spec tests passing, finality on a multi-node devnet. This talk covers how vibecoding works for consensus-critical code and what happens when you let AI ship a hard fork. Full Video Below 👇🧵

For more on ZK Execution Proofs for vibehouse 👇 github.com/dapplion/vibeh…

I'll present ~Vibehouse~ at ETHDenver Thu 19 11:15am The client is already running Gloas ePBS on a multi-node local devnet + implementing ZK execution validity proofs and other fun features!

@thefrozenfire send PRs!

@dapplion I asked Claude Code to explore the repo, and it immediately started working on fixing bugs.

Introducing ~vibehouse~ An Ethereum consensus client with zero devs, Lighthouse v8.0 fork, that ships faster, breaks things sometimes, and accepts feature requests from literally anyone. Participate in the experiment and open an issue! github.com/dapplion/vibeh…

@BattleJeff1 Just soft supervision initially, I'll see my self an advisor more than anything

@dapplion Aren't you the dev in this case?

I'm running an experiment to mantain an Ethereum consensus client with no devs, only ~vibes~ and opus 4.6

Openclaw is so frustrating for sustained dev work... I just want a simple Ralph Loop that communicates to me over Telegram. 75 lines of bash, no deps can do that, and it's not frustrating :) Try it out github.com/dapplion/clawsh

@nero_eth Now you can watch in real time the ETH lost by not playing timing games

Bids.pics now shows the proposer as well. Watching the MEV-Boost market in real time is fascinating: every 12 seconds, builders compete to have their block chosen, continuously outbidding one another. The result is a live view into price discovery for block space as it happens.

A guide for smart contract developers and security engineers navigating Fusaka and its impact on security assumptions. blog.sigmaprime.io/fusaka-contrac…

Ethereal news weekly #0 ⛽️ Gas limit increased to 60M 🦓 Fusaka upgrade December 3 ❎ FOCIL not in Glamsterdam upgrade

Single binary Reth + Lighthouse soon?! 🤯🤯

"Telemetry is fucking cracked" - @dapplion You read it here first!

@ameensol With hard censorship the will of the majority overrules the minority. When the non-censoring 10% of stakers produce a block with un-wanted transactions that block eventually gets re-orged out. So tornado txns will never be included / validated

@dapplion well, that's their choice censorship resistance doesn't mean it can't possibly happen, it just means it's hard also even when tornado txns were blocked by 90% of the stakers, it just meant tornado txns took 10x as long to validate

The case against FOCIL (which I learned about today): ETH devs, I love you. You mean well. But when you create an EIP to solve the problem of "filtering out transactions with sanctioned addresses" and your solution is "to allow validators to impose constraints on builders by force-including transactions in their blocks"... we have a problem. A big problem. And if you don't see it, you're either being naive or reckless. So far, the censorship resistance story on Ethereum has gone something like this: 1) ETH staking is permissionless to join 2) stakers can decide to include txns... so even if 99% of staking nodes censored tornado cash txns for example, it would just take 100x longer This has worked out, in my opinion, more or less OK. Even at peak Tornado Cash censorship, only 90% of nodes were censoring TC txns, so txns should have taken 150s instead of 15s. This setup allowed node operators in the US who could potentially face legal risk for interacting with and facilitating txns to the sanctioned addresses (up to 20 years in prison for a sanctions violation) to simply filter them out and continue participating in the Ethereum network. Even with the block builder oligopoly, only 2 out of 3 of the block builders are censoring, and as the OP mentioned, 90% of the rest of the validator set is NOT engaging in censorship. What FOCIL does is FORCE INCLUDE TRANSACTIONS FROM SANCTIONED ADDRESSES, such that VALIDATORS CAN NO LONGER CHOOSE TO FILTER THEM OUT. This is potentially a big problem for US validators, who now could face legal penalties for staking. It appears the "plan" is to attempt to limit the legal liability of the validator chosen for each block by distributing the responsibility of deciding on txn inclusion across a set of attesters (other validators who are not chosen for the block) such that each block's validator can claim "well look, I didn't choose the txns in the blocks, I'm just validating them." I don't have great faith in this plan. The US government could: 1. Decide it doesn't care about the whole "attester" business and go after known validators who include sanctioned address txns in their blocks anyway. 2. Decide to go after the known attesters who decided to include a sanctioned address txn in the block. 3. Go after the core devs who designed a system to coerce the validators into including sanctioned address txns. If you don't think they won't do #3, that's weird, because I didn't see you at either Alexey's or Roman's trial. If I was the US gov, I would actually be 100% in favor of FOCIL. You mean to tell me the ETH validators are all going to be *forced* to incriminate themselves by validating blocks with sanctioned address txns? Well great, that means I can go after any ETH validator on US soil whenever I want, seize all their ETH, and prosecute them for a sanctions violation. And you're telling me the ETH core devs made their *intent* to coerce validators into violating sanctions publicly available on the ETH research forum? Amazing, now I can even round up any relevant ETH core devs that might pass through the US and prosecute them for conspiracy as well. It also doesn't help that, while FOCIL is currently not designed to provide any incentives validators to include specific txns, instead relying on "altruism" (here, altruism means the willingness to include txns from sanctioned addresses, bc of course it does 🤦‍♀️) this is also not the plan forever. Currently, the plan is Option 1 - to simply rely on "altruistic" validators to attest to the sanctioned address txns, and not provide incentives to the attesters. But I don't think the plan is for things to stay this way forever, as there is an active research effort into figuring out the best way to reward the attesters for their service. The paper below was published May 2025, and includes Julian Ma, one of the original authors of the OP. In conclusion: This isn't 2019 anymore. We can't afford to be naive about the implications of the systems we design and build anymore. FOCIL would coerce ETH validators to include sanctioned address txns, and in doing so, could call into question the legality of ETH staking generally. FOCIL could even incur legal liability on the core devs who designed and implemented it, because it was *explicitly* designed to stop validators from filtering out sanctioned address txns. I love you all, but let's not. cc @soispoke @barnabemonnot @fradamt @_julianma

@SchorLukas There are teams working on this problem already :) with alternative telecommunications networks es.wikipedia.org/wiki/Guifi.net

Ethereum has been completely shut down in Afghanistan. I think we neglect how dependent Ethereum is on internet access. A censorship-resistant "always-on" ledger isn’t much help if a government can just pull the plug by shutting down the internet.