Posting on behalf of @swp0x0 from Nethermind
Hey, restakers! With EigenLayer, we envision a future where a solo operator might run 10 or even 100s of nodes on their machine. Managing many nodes with their AVS-specific interfaces and tooling will take a lot of work.
We at Nethermind, in collaboration with the EigenLabs team and other AVSs, are working towards making the node operators’ experience seamless. We are initially tackling the fragmentation problem for on-premise setups to enhance the node operators’ experience.
Our solution is two-fold:
- A specification for the AVS node software. The specification covers aspects of installing, updating, metrics collection etc.
- A CLI tool to automate many of the interactions of the node operator with AVSs. We are still working on the architecture for the CLI tool. We will share more details soon.
EigenLayer enables the creation of AVSs of many forms, which makes it impossible to predict all the needs of the AVSs. So our guiding principle while designing the specification was to make minimal assumptions about the AVS node software.
The node software specification now covers the most pressing aspects of running and managing a node. We presented our node specification to many AVS teams and some operator teams. You can find a link to the presentation recording here. We encourage you to provide your valuable feedback. Feel free to make an issue on the repo: GitHub - NethermindEth/el-node-spec
Thanks to @smartprogrammer, @adrian and @antid2ta for contributing to this project!
AVS: Actively Validated Service