cerc-io/lighthouse
10
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Add a note about doppelganger protection interoperability to the docs (#2607)

Browse Source 
## Issue Addressed

N/A

## Proposed Changes

Add a note to the Doppelganger Protection docs about how it is not interoperable until an endpoint facilitating it is standardized (https://github.com/ethereum/beacon-APIs/pull/131).

## Additional Info

N/A


Co-authored-by: realbigsean <seananderson33@gmail.com>
This commit is contained in:
realbigsean 2021-09-20 22:28:37 +00:00
parent a73dcb7b6d
commit fb1df2c926
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
book/src/validator-doppelganger.md
View File

@ -15,6 +15,10 @@ instances of a validator operating on the network before any slashable offences
achieves this by staying silent for 2-3 epochs after a validator is started so it can listen for achieves this by staying silent for 2-3 epochs after a validator is started so it can listen for
other instances of that validator before starting to sign potentially slashable messages. other instances of that validator before starting to sign potentially slashable messages.
> Note: Doppelganger Protection is not yet interoperable, so if it is configured on a Lighthouse
> validator client, the client must be connected to a Lighthouse beacon node. Because Infura
> uses Teku, Lighthouse's Doppelganger Protection cannot yet be used with Infura's Eth2 service.
## Initial Considerations ## Initial Considerations
There are two important initial considerations when using DP: There are two important initial considerations when using DP: