Content
@
https://warpcast.com/~/channel/eigenlayer
0 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
Let's check the Unique Stake Model through the Issues of the Shared Stake Model of EigenLayer and the ELIP-002 proposal to solve them. ELIP-002: https://github.com/eigenfoundation/ELIPs/blob/main/ELIPs/ELIP-002.md
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
The shared stake model had an issue: when operators joined multiple AVS, their delegated stake could be slashed by all chosen AVS. This exposed the same stake to multiple slashing risks, where slashing by one AVS could indirectly affect others. The model failed to guarantee AVS' access to slashable stakes when needed, requiring a global veto committee to prevent systematic slashing risks.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
ELIP-002 addresses these issues by introducing the Unique Stake and Operator Sets Model. This model enables operators to allocate specific portions of their stakes to individual AVS, ensuring that slashing events remain isolated. For example, if an operator allocates 10% of their stake to AVS A and 20% to AVS B, slashing in AVS A only affects its 10% allocation, leaving AVS B's 20% untouched.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
The protocol uses Magnitude as an accounting unit to track the percentage of delegated stake assigned to each AVS. for example with each Operator total Magnitude fixed at 1x10^18, the sum of Magnitudes assigned across operators cannot exceed this value, preventing double allocation since AVS cannot slash the same stake.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
Implementing delay mechanisms for Unique Stake Allocation, Deallocation, and Withdrawal actions protects against synchronous timing attacks. • ALLOCATION_DELAY: Creates a delay between when operators allocate stake to AVS and when it becomes a slashing target, giving stakers time to withdraw if they disagree with new allocations. • DEALLOCATION_DELAY: Implements a delay between stake deallocation and non-slashable status, allowing AVS time to execute slashing for past operations. • WITHDRAWAL_DELAY: establishes a delay between withdrawal requests and completion, during which stake remains a slashing target, enabling AVS to address past misconduct.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
I've created a diagram to help easily understand how Magnitude changes based on Unique Stake Looking at allocation/deallocation, when allocating 2,000 Magnitude to the "EigenDA_EIGEN" Operator, it remains in a "Pending Allocation" state as shown below. In this case, the previously mentioned ALLOCATION_DELAY is initiated.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
If we deallocate about 50% for the Operator, it remains in a "Pending Deallocation" state as shown below. Similarly, a DEALLOCATION_DELAY is initiated.
1 reply
0 recast
0 reaction
zer0luck.base.eth
@zer0luck
consider it from a slashing perspective - in the previous deallocation example, if we slash the Operator by 50%, both the current allocation amount and pending deallocations will be reduced by the slashing ratio.
1 reply
0 recast
0 reaction
