ethereum / ethereum/trinity-eth2
Slashing protection in the validator client
Open
- Dominant language
- Python
- Stars
- 16
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Important tasks to implement slashing protection:
- [ ] Move from in-memory database to persistent database to track signatures the client has created
- [ ] integrity of writing those signatures to disk (make sure there are no atomicity issues w/ e.g. leveldb)
- [ ] There is no real attestation slashing protection as of ethereum/trinity#1482 .
- [ ] add tests to validate attestation and block slashing protections
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.