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.

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

docs: Consistently Indicate Slasher Under Development and Inactive #36

Merged
merged 10 commits into from
Nov 3, 2023
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# AVS Smart Contract Architecture

<p align="center"><b><font size="+1">
🚧 The Slasher contract is under active development and its interface expected to change. We recommend writing slashing logic without integrating with the Slasher at this point in time. 🚧
</font></b><p>

## Introduction

EigenLayer AVSs are a new type of protocol that makes use of EigenLayer’s restaking primitive. AVSs are different from current chains and other smart contract protocols in that they are validated by EigenLayer operators. There are 3 specific types of conditions that AVSs implement in smart contracts onchain:
Expand Down
1 change: 1 addition & 0 deletions src/BLSRegistryCoordinatorWithIndices.sol
Original file line number Diff line number Diff line change
Expand Up @@ -378,6 +378,7 @@ contract BLSRegistryCoordinatorWithIndices is EIP712, Initializable, IBLSRegistr
BN254.G1Point memory pubkey,
string memory socket
) internal virtual returns(uint32[] memory) {
// TODO after slashing: revert registration when operator is slashable in the EigenLayer Slasher
stevennevins marked this conversation as resolved.
Show resolved Hide resolved
// require(
// slasher.contractCanSlashOperatorUntilBlock(operator, address(serviceManager)) == type(uint32).max,
// "StakeRegistry._registerOperator: operator must be opted into slashing by the serviceManager"
Expand Down