EthStorage
858 posts
@EthStorage
🌟A modular and decentralized storage Layer 2 that offers programmable key-value storage 🌟Scaling Storage of the World Computer 🌟Received grants from ESP
The Ethereum Foundation Bug Bounty Program (bounty.ethereum.org) has increased its maximum payout from $250K to $1M.
the synthesis is coming.
📣 Institutional Onchain: Stablecoins, RWAs & AI is coming to Hong Kong. 📅 11th February | 04:00 PM – 07:00 PM 📍 Hong Kong During Consensus Hong Kong Co-Hosted by @unpaidcompany with incredible Partner line up from @FOFO_HFintech @st0x_io @PerleLabs @pharos_network @lagrangedev @redstone_defi @KiteAIFDN @debridge @1inch @MetisL2 @JSquare_co @Conflux_Network @QuillAudits_AI @KiraPayOfficial @Quark_Chain @EthStorage @geniusprhq @Rapidz_io @ActionModelAI @hectofinance @MindoAI Bringing together institutions, funds and protocol teams.
There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.
OpenSea has added support for web3:// (ERC-4804) Most NFTs today still rely on off-chain infrastructure to be accessed and understood. When those access layers disappear, the asset itself becomes unreachable. ERC-4804 introduces a native way to resolve NFT metadata directly from Ethereum — removing reliance on gateways, DNS, or centralized access points. This standard was originally proposed and advanced by the QuarkChain team to address this long-standing gap in Web3. For QuarkChain, this aligns directly with the Super World Computer vision: a system where decentralization extends beyond execution to include how applications and data are accessed — forming a truly end-to-end decentralized stack. 🔗 OpenSea Metadata Standards docs.opensea.io/docs/metadata-… 🔗 Bankless on ERC-4804 bankless.com/read/erc-4804-… 🔗 web3:// web3url.io
Welcome to 2026! Milady is back. Ethereum did a lot in 2025: gas limits increased, blob count increased, node software quality improved, zkEVMs blasted through their performance milestones, and with zkEVMs and PeerDAS ethereum made its largest step toward being a fundamentally new and more powerful kind of blockchain (more on this later) But we have a challenge: Ethereum needs to do more to meet its own stated goals. Not the quest of "winning the next meta" regardless of whether it's tokenized dollars or political memecoins, not arbitrarily convincing people to help us fill up blockspace to make ETH ultrasound again, but the mission: To build the world computer that serves as a central infrastructure piece of a more free and open internet. We're building decentralized applications. Applications that run without fraud, censorship or third-party interference. Applications that pass the walkaway test: they keep running even if the original developers disappear. Applications where if you're a user, you don't even notice if Cloudflare goes down - or even if all of Cloudflare gets hacked by North Korea. Applications whose stability transcends the rise and fall of companies, ideologies and political parties. And applications that protect your privacy. All this - for finance, and also for identity, governance and whatever other civilizational infrastructure people want to build. These properties sound radical, but we must remember that a generation ago any wallet, kitchen appliance, book or car would fulfill every single one of them. Today, all of the above are by default becoming subscription services, consigning you to permanent dependence on some centralized overlord. Ethereum is the rebellion against this. To achieve this, it needs to be (i) usable, and usable at scale, and (ii) actually decentralized. This needs to happen at both (a) the blockchain layer, including the software we use to run and talk to the blockchain, and (b) the application layer. All of these pieces must be improved - they are already being improved, but they must be improved more. Fortunately, we have powerful tools on our side - but we need to apply them, and we will. Wishing everyone an exciting 2026. Milady.
Fusaka is live on Ethereum mainnet! - PeerDAS now unlocks 8x data throughput for rollups - UX improvements via the R1 curve & pre-confirmatons - Prep for scaling the L1 with gas limit increase & more Community members will continue to monitor for issues over the next 24 hrs.
AItopia [EN] No.001 "When the Internet Breaks: Can Web3 Survive a Cloudflare-Scale Outage?" Time: Friday, November 28 · 10:00 PM (GMT+8) Cloudflare’s global outage reminded the industry of an uncomfortable truth: even Web3 still depends on centralized routing, DNS, and edge layers it aims to transcend. AItopia No.001 begins with a simple question — what actually stays online when the backbone of the Internet fails? Hosted by: Vincent — Committee Member, @499_DAO Confirmed Speakers: • Vikas Pandey @buidloor — Head of Protocol, @GoKiteAI • Anthurine @anthurine — Co-Founder, @EthStorage • Kate @ionetkate — Head of Partnerships, @ionet Tune in here: x.com/i/spaces/1jmjg… X Community: x.com/i/communities/… Telegram Group: t.me/+xMlOO3VQH-piZ… AItopia will dive into: • How the outage exposed dependency chains across compute, storage, inference, and routing • Which layers of decentralized infra would fail today—and which could stay operational • Whether decentralized networks can offer Cloudflare-grade reliability without recreating central choke points • The system-level design needed for a genuinely outage-tolerant Web3
