Skip to content

Commit fb1df2c

Browse files
committed
Add a note about doppelganger protection interoperability to the docs (#2607)
## 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 (ethereum/beacon-APIs#131). ## Additional Info N/A Co-authored-by: realbigsean <[email protected]>
1 parent a73dcb7 commit fb1df2c

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

book/src/validator-doppelganger.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ instances of a validator operating on the network before any slashable offences
1515
achieves this by staying silent for 2-3 epochs after a validator is started so it can listen for
1616
other instances of that validator before starting to sign potentially slashable messages.
1717

18+
> Note: Doppelganger Protection is not yet interoperable, so if it is configured on a Lighthouse
19+
> validator client, the client must be connected to a Lighthouse beacon node. Because Infura
20+
> uses Teku, Lighthouse's Doppelganger Protection cannot yet be used with Infura's Eth2 service.
21+
1822
## Initial Considerations
1923

2024
There are two important initial considerations when using DP:

0 commit comments

Comments
 (0)