# EigenCloud is now BASED

**Published by:** [Coordinated](https://paragraph.com/@coordinated/)
**Published on:** 2025-07-25
**Categories:** eigencloud, eigenlayer, base, ethereum, rollup, l1, l2
**URL:** https://paragraph.com/@coordinated/eigencloud-is-now-based

## Content

eigencloud just went multi-chain. this changes everything. for months, AVS builders have been bottlenecked. no matter how good your infra, you could only serve dapps and apps on ethereum mainnet. because the core verification logic, the stake weights, operator sets, slashing rules lived there. any attempt to build outside mainnet meant rebuilding everything from scratch: bridges, syncing logic, security assumptions. a few tried. most gave up. too costly, too slow, too brittle. that’s done now. EigenCloud @eigenlayer EigenCloud is going Multi-Chain. Today, we’re launching Multi-Chain Verification with our first integration on @base, bringing verifiable security to one of the fastest-growing ecosystems in crypto. This update enables AVSs to verify across L2s while preserving 219 9:08 PM • Jul 24, 2025 multi-chain verification (ELIP-008)eigenlayer just rolled out multi-chain verification, a protocol-level feature that lets any AVS extend its services to L2s and other chains, without losing ethereum-aligned trust. this means:you still get the same operator set and stake weightsyou don’t need to bridge slashing info manuallyyour AVS works across chains without rewriting core logicall this is powered by a minimal config change at the contract level. once you opt-in, the protocol takes care of the rest.cool but how does it work?at the heart of this feature is a shared verification interface, standardized across chains. no more chain-specific rewrites. AVSs use the same interface to fetch:current operator setsstake weights per operatorslashing updates, ejections, and penaltiesthese updates are synced to L2s by eigenlayer itself. in the current public preview, stake data on Base Sepolia is updated daily. if an operator gets slashed or ejected, the changes are broadcast instantly. no delay, no rollup dependence. AVSs can start integrating right away by configuring the new verification source on Base Sepolia. more chains and higher update frequencies will roll out in the next phases. Sreeram Kannan @sreeramkannan For trust to scale, it must be portable. With EigenCloud’s Multi-Chain Verification, Ethereum’s trust guarantees extend across its full ecosystem. Today, we launch our first integration on @base, bringing Ethereum-aligned security to one of crypto’s fastest-growing ecosystems. EigenCloud @eigenlayer EigenCloud is going Multi-Chain. Today, we’re launching Multi-Chain Verification with our first integration on @base, bringing verifiable security to one of the fastest-growing ecosystems in crypto. This update enables AVSs to verify across L2s while preserving 105 2:42 AM • Jul 25, 2025 but why does it matter for devs?this isn't about "going multi-chain" for the sake of it. this unlocks real stuffs.lower gas costs → deploy heavy computation on cheap chainsfaster UX → serve users in low-latency environmentsdev velocity → build and iterate without L1 bottlenecksnew markets → plug your AVS directly into the most active L2sretain trust → no compromise on security guaranteeseigencloud becomes the source of truth for trust. verification becomes portable.who's first? and what’s next?the first chain to get integrated is Base. no surprise. it's one of the most active ecosystems, with a huge dev base and strong infra alignment. preview is on Base Sepolia. mainnet support is coming Q3. AVSs can opt-in now, start testing, and be ready for full-scale multi-chain deployment when GA hits. feedback loop is open via the [ELIP-008 forum post].this makes eigencloud truly horizontalbefore this release, eigenlayer was powerful, but boxed in. you had security, but no flexibility. verification was pinned to one chain. if your AVS wanted to be composable, scalable, and fast, you were on your own. now, eigencloud isn’t just the most active dev ecosystem, it's also unbound by L1. you can build once, verify anywhere. link your service to eigencloud. extend trust to every chain. start with base. move everywhere.

## Publication Information

- [Coordinated](https://paragraph.com/@coordinated/): Publication homepage
- [All Posts](https://paragraph.com/@coordinated/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@coordinated): Subscribe to updates