Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing Slashable Stake example detail #18

Merged
merged 2 commits into from
Feb 3, 2025
Merged

Fixing Slashable Stake example detail #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8fa969
fixing slashable stake example detail
wesfloyd Jan 15, 2025
d5ca48a
Fixed
non-fungible-nelson Feb 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ELIPs/ELIP-002.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ In figure 3 below, Operator 1 has a delegation of 100 staked ETH for the ETH Str
![Operator Allocations to Operator Sets](../assets/elip-002/figure-3.png)
***Figure 3: Operator Allocations to Operator Sets***

The 85 allocated ETH is slashable exclusively by the AVS originating each Operator Set. In this case, AVS 2, 3, and 4 can slash their associated Operator Sets 2, 3, and 4, respectively.
The 85 allocated ETH is slashable exclusively by the AVS originating each Operator Set. In this case, AVS 2, 3, and 4 can slash their associated Operator Sets 3, 4, and 5, respectively.

Let’s consider another example with three Operators. Figure 4 illustrates two Operator Sets instantiated by AVS 1. AVS 1 has created two Operator Sets for different tasks. For example, this AVS may use Operator Set 1 for assigning generation of ZK proofs to Operators, an expensive computation, and Operator Set 2 for verification of those proofs, a cheaper computation.

Expand Down