FLCL | 0xf1c1.eth 🦇🔊

@prywatnik Cool stuff! Vibecoded a page to test it flcl42.github.io/eml-trees/

Polski naukowiec napisał ciekawą pracę - i nie bójmy się nazwać jej przełomową. Przez setki lat matematyka miała dziesiątki “podstawowych” funkcji jak sinus, cosinus, logarytm, pierwiastek, eksponenta. Znacie to ze szkoły. Wiadomo o co chodzi. Fizyk z Uniwersytetu Jagiellońskiego właśnie pokazał, że to wszystko jeden operator: E(x, y) = exp(x) - ln(y), oraz 1. Sin, cos, π - wszystko z tego pięknie wynika, wystarczy odpowiednio zagnieździć. Natura ukryła najprostszy możliwy zapis rzeczywistości. I znaleźliśmy go przez przypadek. Całość jest piękna i wspaniała, a słowo „przełomowe” nie stanowi tu marketingowego buzzworda. Przykładowo zamiast pisać π czy 3.14 można teraz elegancko E(E(E(1,E(E(1,E(1,E(E(1,E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(E(E(E(E(1,E(E(1,E(1,E(E(1,E(E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(E(1,E(E(1,E(E(1,E(E(1,1),1)),E(E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(1,1)),1))),1)),1)),1)),1))),1)),E(E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(E(1,E(E(1,E(1,E(E(1,E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(1,1))),1))),1)),1)),1)),1),1),1))),1))),1)),E(E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(E(1,E(E(1,E(1,E(E(1,E(E(1,E(E(1,E(1,E(E(1,1),1))),1)),E(1,1))),1))),1)),1)),1)),1)

@ben_a_adams @DamianEdwards @davidfowl @danroth27 @shanselman @axboe Non-zero chance Ben will invent neutrino transmitters at some point to make it faster

It is time. Let's go faster! Let's use io_uring for dotnet System​.Net.Sockets on Linux! PR124374 Replaces epoll with managed C# io_uring engine: batching, multishot accept/recv, zero-copy send, registered buffers, SQPOLL (zero-syscall), and more 🚀

@VitalikButerin I think we need to create distributed data solution like portal, but index-centric, generic enough to easily add new indexes, well incentivized. Hold there historical data including expiring state

Hyper-scaling Ethereum state by creating new forms of state: ethresear.ch/t/hyper-scalin… Summary: * We want 1000x scale on Ethereum L1. We roughly know how to do this for execution and data. But scaling state is fundamentally harder. * The most practical path for Ethereum may actually be to scale existing state only a medium amount, and at the same time introduce newer forms of state that would be extremely cheap but also more restrictive in how you can use them. * In such a design, the present-day state tree would over time become dominated by user accounts, defi hub contracts, code, and other high-value objects, while all kinds of individual per-user state objects (eg. ERC20s balances, NFTs, CDPs) would be handled with cheaper but more restrictive tools. Making the developer abstractions to make this easy to implement for the use cases that make up >90% of state today seems very doable.

2026 is the year that we take back lost ground in terms of self-sovereignty and trustlessness. Some of what this practically means: Full nodes: thanks to ZK-EVM and BAL, it will once again become easier to locally run a node and verify the Ethereum chain on your own computer. Helios: actually verify the data you're receiving from RPCs instead of blindly trusting it. ORAM, PIR: ask for data from RPCs without revealing which data you're asking, so you can access dapps without your access patterns being sold off to dozens of third parties all around the world. Social recovery wallets and timelocks: wallets that don't make you lose all your money if you misplace your seedphrase, or if an online or offline attacker extracts your seedphrase, and *also* don't make all your money backdoored by Google. Privacy UX: make private payments from your wallet, with the same user experience as making public payments. Privacy censorship resistance: private payments with the ERC-4337 mempool, and soon native AA + FOCIL, without relying on the public broadcaster ecosystem. Application UIs: use more dapps from an onchain UI with IPFS, without relying on trusted servers that would lock you our of practical recovery of your assets if they went offline, and would give you a hijacked UI that steals your funds if they get hacked for even a millisecond. In many of these areas, over the last ten years we have seen serious backsliding in Ethereum. Nodes went from easy to run to hard to run. Dapps went from static pages to complicated behemoths that leak all your data to a dozen servers. Wallets went from routing everything through the RPC, which could be any node of your choice including on your own computer, to leaking your data to a dozen servers of their choice. Block building became more centralized, putting Ethereum transaction inclusion guarantees under the whims of a very small number of builders. In 2026, no longer. Every compromise of values that Ethereum has made up to this point - every moment where you might have been thinking, is it really worth diluting ourselves so much in the name of mainstream adoption - we are making that compromise no longer. It will be a long road. We will not get everything we want in the next Kohaku release, or the next hard fork, or the hard fork after that. But it will make Ethereum into an ecosystem that deserves not only its current place in the universe, but a much greater one. In the world computer, there is no centralized overlord. There is no single point of failure. There is only love. Milady.

🎉Fusaka is on, more blobs very soon! 🎉

Keep in mind you will need @dotnet 10 SDK for compiling master now: dotnet.microsoft.com/en-us/download…

Nethermind 🫱🏿‍🫲🏽 Besu interop on block access list local devnet 🚀 Exciting first steps towards Amsterdam fork!

@VitalikButerin We need a different hardware platform. Brain is 3D, chips should be too. Memory and CPU should be the same simple unit in a 3d matrix of myriads of them. This will cause the real revolution, especially in AI

Memory access is O(N^[1/3]) vitalik.eth.limo/general/2025/1…

First goes Holesky, October 1. Update your nodes!

In the upcoming Fusaka hardfork, Ethereum will modify the gas costs and allowed inputs for the ModExp precompile through two EIPs: EIP-7883 and EIP-7823. We encourage all developers and infrastructure providers to review their smart contracts, gas estimation algorithms, and related tooling for potential impacts. For a detailed impact analysis, refer to the reports by @nero_eth: 🔍 github.com/nerolation/eth… github.com/nerolation/eth…

Stress-test ePBS (EIP-7732) vs. Electra on 1 GigaGas L1 (avg 200 MGas blocks ~4 s exec) w/ @potuz_eth over 4 epochs: Electra: 28 orphaned blocks (lost rewards) ePBS: 0 orphaned blocks EIP-7732 is a game-changer for Ethereum L1 scaling! 🔥

@jcouv What benefits of wrapping it in `static class`? Could it be just `public extension of S`

We merged a C# 14 feature into .NET 10 preview 7: extension operators. We'd previously merged extension methods and properties (static and instance) but I forgot to tweet that. Example and spec below.

@bogdanoffi I like this graph. Every time someone says homestackers are not important, I have hard time understanding why that dude even joins the calls or chats

Fun fact: Ethereum is by far the most decentralized turing complete blockchain. There are currently 3,400 validator nodes hosted on residential connections. A ~77% increase from 1,900 in just 3 months. These home stakers make up nearly 40% of Ethereum's validator set. A permissionless network where anyone can join the validator set on affordable hardware. Whereas every other Ethereum competitor relies on a small group of validators hosted on enterprise grade hardware, data centers, or cloud providers. The Ethereum community has always prioritized decentralization, and multiple protocols were developed to reduce the cost and increase accessibility for anyone interested. For example using distributed validator tech via @Obol_Collective & @ssv_network, running a @Rocket_Pool validator with only 8 ETH, or a @LidoFinance CSM validator with only 2.4 ETH. No other chain comes close to Ethereum's commitment to decentralization, and entities that value it will continue to build on Ethereum.

@potuz_eth Prepare some cool dashboards about EOF efficiency, share with public, commit to fork with EOF months after fusaka ????? Profit

Regardless of right or wrong, having a large subset of the client devs feeling frustration or even anger is not dismissible. It makes for an unhealthy work environment one that is already stressful. This has to be addressed urgently 1/2

What are the performance benefits of EOF (EVM Object Format)? At the @SuccinctLabs residency, my benchmarks reveal ZK proving EOF is ~3x more efficient and runs 2.69x faster than the current EVM version ⛽ (link below)

Update everyone! Hardfork season is getting to it's final stage. Happy hardfork!

The next step is to make another devnet where multiple Fusaka EIPs are activated, moving towards more and more real setup that we will have on mainnet.

Observe the train: …rkmon.peerdas-devnet-6.ethpandaops.io Participate in the devnet: peerdas-devnet-6.ethpandaops.io Spawn your own PeerDAS network: @ethpandaops/peerdas-devnet-6#Kurtosis-Interop-Conifg-Pre-devnet-testing" target="_blank" rel="nofollow noopener">notes.ethereum.org/@ethpandaops/p…

This train can't be stopped: PeerDAS is available for devs on new peerdas-devnet-6! PeerDAS scales blobs a lot and goes live in Fusaka, a fork landing soon after Pectra.