EigenLayer is soon turning on the ability for the slashed funds to be distributed to the AVS building on top, as opposed to burning the slashed funds (which is what L1s that have slashing do today).
This enables whole new categories of applications to be built on top of EigenLayer: categories of financial applications we had not designed it for.
EigenLayer was originally designed with the intent to build verifiable services to augment the crypto developer ecosystem. We invented a new model for PoS security: StakeSure which is a mechanism for redistributing slashed funds for an L1 to its harmed users. Redistribution in EigenLayer is a mechanism to achieve this property. When staking to an operator, slashing is usually for malicious behavior of the operator - thus the stakers are underwriting "operator risk".
The market is inventing new mechanisms for utilizing the stake in EigenLayer and using it to underwrite other "financial risks": slashing if an operator does not meet a financial target. With these newer risks come higher rewards.
On this new frontier, there are new rewards to be earned along with new risks. We strongly encourage every staker and operator to clearly understand and evaluate their risk profile to see if any specific AVS meets their risk / reward tradeoffs. EigenLayer is a permissionless protocol, which means the protocol does not have agency; instead the protocol passes on this agency to the stakers and operators.
Excited for this new emergent frontier in EigenLayer! I cannot help but feel this is what Ethereum devs must have felt when restaking emerged on top allowing validators to do other things. With this feature, EigenLayer stakers can do more than serve "actively validated services" they can serve any financial use case - an unexpected and emergent frontier.
@capmoney_ is pioneering a radically innovative design in this category and pushing the frontier. We are excited they chose to build their product on @eigenlayer. Happy exploration to the pioneers and delighted to have @capmoney_ lead the charge!
In this thread, I will present the story of our journey to build EigenDA from a personal vantage point. This story will lay out our longstanding interest in scaling network bandwidth as well as offer some inside anecdotes.
My interest in “cooperative” p2p networks dates before blockchains. Here is a 2008 paper, where we designed new network “erasure” coding schemes for wireless networks:
I had moved on from p2p wireless in my PhD to work on computational genomics by 2013. For example, in this paper with @xiaojie_qiu, we design new methods for gene regulatory network inference using single cell RNA sequencing data: cell.com/cell-systems/p…
Definition: coprocessor is a stateless offchain system and rollup is a stateful offchain system.
When does a coprocessor suffice? When the computation inputs are fully specified onchain and the state change has to be actuated onchain.
Let’s start with a motivating example.
Imagine you want to build a @Uniswap LP strategy or v4 hook that adjusts the price or fees based on a AI model factoring the history of onchain transaction toxicity. (Cc @haydenzadams @danrobinson @0x94305).
Refined view: There are 5 properties that together make a *confirmation rule* secure. We colloquially talk about a chain being secure but really it is the confirmation rule to which the security property attaches.
This difference occurs because a single chain can admit multiple confirmation rules. For example, in Bitcoin, different nodes can use different depths in their confirmation rules and they will accordingly have different probabilities of safety violations.
A starker contrast occurs in Ethereum, in the gasper protocol, there are two distinct confirmation rules - an available rule (based on the heaviest chain) and a finalized rule (based on blocks confirmed by the gadget).
We welcome this excellent analysis of the different kinds of risks using restaking for different use cases a la @eigenlayer by @VitalikButerin. It is consistent with what we have been advocating with Eigenlayer. A brief summary here:
a) don’t build complex financial primitives on restaking - they can spiral out
b) don’t rely on Ethereum to fork for application layer errors - this is a super important principle
c) do not use subjective slashing - as it is subject to tyranny of the dishonest majority
Low risks
a) Use restaking for highly objective attributable misbehaviors such as double signing
b) Use restaking purely for getting the decentralization benefits of Ethereum without slashing
We recently announced the Series A for @eigenlayer led by @blockchaincap. In this thread I will highlight several key investors in the seed round, which was co-led by @polychaincap and @etherealvc.
The first investment offer for @eigenlayer came from @etherealvc, back in Sep 2021. It has been an absolutee privilege to work with @_MinTeo and @bees_neeth at Ethereal ventures. They have been a close working partner and a strong pillar of support from the very beginning!
P.S. Mycelia are fungi that help connect roots of trees in order to help them exchange nutrients. We think this is an apt metaphor for restaking!
I covered four different usecases: A1) event driven actions, A2) partial block auctions, A3) threshold cryptography, A4) long term block auctions, and their composibility A1234) in the talk.