EigenLayer as a verifiable cloud: the AVS model explained
Thread411 words
Explains EigenLayer as a cloud for programmable trust: it accumulates stake and lets anyone rent security on demand, giving rise to AVSs. Lists oracle, DA, ZK proving, interop and rollup coordination AVS categories.
Key claims
EigenLayer has roughly $12B in restaked capital
Cloud aggregates compute whereas EigenLayer accumulates stake to secure networks
AVS categories include oracles, DA, ZK proving, interop and fast finality
๐๐๐ซ๐ข๐๐ข๐๐๐ฅ๐ ๐๐๐๐ ๐ฉ๐จ๐ฐ๐๐ซ๐๐ ๐๐ฒ ๐๐ข๐ ๐๐ง๐๐๐ฒ๐๐ซ โพโจ
โ
@eigencloud's AVS-centric model enables super-specialized infra services that serve applications with specific functionality at scale.
โ
Think of @eigencloud as a cloud platform for programmable trust to build verifiable infra services.
โ
๐๐ฒ๐ ๐บ๐ฒ ๐ฒ๐
๐ฝ๐น๐ฎ๐ถ๐ป. โคต๏ธ
The cloud aggregates compute and allows anyone to use compute on demand to run their apps.
โ
@eigencloud on the other hand accumulates stake (crypto-economic security) and lets anyone use this security on demand to secure decentralized networks.
โ
Until today, @eigencloud has accumulated roughly $12B in restaked capital, which fuels the programmable trust layer that is @eigencloud.
โ
This design gives rise to what is referred to as "Actively Validated Services (AVS)", that leverage @eigencloud's shared security layer.
โ
Permissionlessly created, decentralized services can then be integrated to create arbitrary applications.
This vision is derived from what is already a reality in Web2.
โ
In Web2 developing a web app essentially means piecing together different services and APIs.
โ
Within this highly abstracted environment, the developers can focus solely on the application design and don't have to care about the infra level complexities.
โ
In Web3 on the other hand, developers that want to build on decentralized platforms still lack a lot of services, which makes blockchain app development significantly more complex.
โ
Often, app developers have to build infrastructure from scratch, which is costly and time-consuming, even rendering some use cases prohibitively difficult to implement.
โ
Having specialized service providers with APIs and SDKs that ultimately serve as the core building blocks of applications on the layer above, abstracts significant complexity and allows builders to focus exclusively on the app logic and their competitive edge.
โ
๐ฆ๐ผ, ๐๐ต๐ฎ๐ ๐ถ๐ ๐๐ถ๐ด๐ฒ๐ป๐๐ฎ๐๐ฒ๐ฟ?
โ
@eigencloud's "verifiable cloud", is a developer platform that fixes this problem by lowering the barriers of entry to build these services.
In the weeks and months to come, we will see all sorts of services emerge on top of @eigencloud.
โ
This includes:
โ
โ Oracles (e.g. @eoracle_network)
โ DA Layers (e.g. @eigen_da)
โ ZK Proving (e.g. @lagrangedev or @brevis_zk)
โ ZK Verification (e.g. @alignedlayer)
โ DePIN Coordination (e.g. @witnesschain)
โ Incident Response (e.g. @DroseraNetwork)
โ Interoperability (e.g. @hyperlane)
โ Rollup Coordination (e.g. @EspressoSys)
โ TEE-based Provers (e.g. @AutomataNetwork)
โ Fast Finality (e.g. @nufflelabs)
โ +++
โ
Open innovation. โพโจ
โ
Powered by @eigencloud.
โ
DYOR anon.
For a full list of @eigencloud AVS protocols, have a look at my ecosystem overview below! โคต๏ธ
x.com/zerokn0wledge_/status/1833514839823815040
3 images on X
What came next ยท since 13 Sep 2024
Since then
Zero has written 11 more pieces on EigenLayer since this one.