Layr-Labs / eigenda-operator-setup

Quick start setup guide for EigenDA
MIT License
80 stars 78 forks source link

No "el_slasher_address" and "bls_public_key_compendium_address" were provided by the team #83

Closed eferbarn closed 5 months ago

eferbarn commented 5 months ago

Issue Summary

I was considering the transition from the Goerli network to the Holesky network.

el_slasher_address=[slasher_address]
bls_public_key_compendium_address=[bpkc_address]

These two essential parameters in the operator.yaml file, which were supposed to be provided by the team are not included in the official documentation, and this has caused container execution to face issues. In fact, those who managed to register have used corresponding contracts in the Guerli network, leading to many operators being registered, but unable to return signatures.

Official Doc URL


Environment

Actual Behavior

Thrown error: Failed to fetch Slasher address: no contract code at given address when trying to register in EigenLayer.

nod3dev commented 5 months ago

Hello eferbarn How about use this?

First, delete the existing operator.yaml file by running rm -rf operator.yaml. After that, create a new operator.yaml file using the command eigenlayer operator config create. A new operator.yaml file will be generated. Then, open the newly created operator.yaml file with nano operator.yaml and enter your code.

shrimalmadhur commented 5 months ago

the new cli required el_delegation_manager_address Please open issue in https://github.com/Layr-Labs/eigenlayer-cli/issues for any cli related issues.