ChainSafe / ChainSafe/lodestar

Lazy slasher beacon node

Open
#7,961 1 comment 0 reactions 0 assignees View on GitHub
good EPF issue help wanted meta-feature-request prio-medium
Dominant language
TypeScript
Stars
1.4k
Forks
483
Avg merge
1d 16h
Merged PRs (30d)
150

Description

https://ethresear.ch/t/a-lazy-approach-to-slashers/22041

[Discord thread](https://discord.com/channels/593655374469660673/1352244636122353696)

This issue is to track development of a lazy slasher on the beacon node by default that would help with slashings should other slashers fail due to computational overhead as seen on the Holesky incident. This will ensure that in times of heavy network instability, lazy slashers should be able to execute their duties in an effective, resource efficient way.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.