jefflau.eth
12K posts

jefflau.eth
@Jefflau
Building @ensdomains. Distilling the complicated into the simple. Curious about ZK, dabbling in crypto(graphy)

My self-sovereign / local / private / secure LLM setup, April 2026 vitalik.eth.limo/general/2026/0…






re: [Temp Check] ENS v2 Pricing: 5-Character Name Price Adjustment & Multi-Year Discounts "We’ve been listening closely to everyone’s feedback... ... We’ve amended our proposal as follows:" discuss.ens.domains/t/temp-check-e…


defiunited.eth is now open for contributions. All contributions are going towards DeFi United relief efforts to restore rsETH and safe DeFi. defiunited.world








Etherscan reports that Ethereum address poisoning has become industrialized. Driven by lower costs post-Fusaka upgrade (Dec 3), USDT dust transfers surged 612%. Historical data (July 2022–June 2024) reveals ~17 million attempts and over $79.3M in losses. Attackers leverage automated lookalike addresses and dust/zero-value transfers to pollute transaction histories. Despite a marginal 0.01% success rate, the massive scale of these operations ensures high profitability. x.com/etherscan/stat…



Launching a new .whatever namespace is easy. Building naming infrastructure that works across wallets, apps, exchanges, and the web is much harder. Why ENS chose to extend the existing internet namespace instead of inventing new roots ⤵️ ens.domains/blog/post/ens-…

It's a good decision! ENS names and records are a form of state that is central to the Ethereum ecosystem, the state is limited in size and there is high value in it being as accessible as possible from anywhere. It's also a semi-financial application, in the sense that buying and holding ENS names has a cost, and ENS names can become very valuable objects. With the expanded scaling roadmap, Ethereum L1 is the ideal place for these applications. More generally, I expect that the optimal architecture for decentralized identity and social (the general space I see ENS being in) is to have this kind of per-user account and profile data on L1, and to have special-purpose L2s, likely much simpler than full EVMs, to handle user actions (eg. actions on social platforms).




