lighthouse

cerc-io/lighthouse

Fork 0

Commit Graph

Author	SHA1	Message	Date
Pawan Dhananjay	3721f3a83c	Fix doppelganger script (#3988 ) ## Issue Addressed N/A ## Proposed Changes The doppelganger tests were failing silently since the `PROPOSER_BOOST` config was not set. Sets the config and script returns an error if any subprocess fails.	2023-02-21 23:45:43 +00:00
realbigsean	ae5b141dc4	Updates to tests and local testnet for Ganache 7 (#3056 ) ## Issue Addressed #2961 ## Proposed Changes -- update `--chainId` -> `--chain.chainId` -- remove `--keepAliveTimeout` -- fix log to listen for -- rename `ganache-cli` to `ganache` everywhere Co-authored-by: realbigsean <sean@sigmaprime.io>	2022-03-20 22:48:14 +00:00
realbigsean	c5786a8821	Doppelganger detection (#2230 ) ## Issue Addressed Resolves #2069 ## Proposed Changes - Adds a `--doppelganger-detection` flag - Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64 - If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default. ## Additional Info I'd like to add tests and would appreciate feedback. TODO: handle validators started via the API, potentially make this default behavior Co-authored-by: realbigsean <seananderson33@gmail.com> Co-authored-by: Michael Sproul <michael@sigmaprime.io> Co-authored-by: Paul Hauner <paul@paulhauner.com>	2021-07-31 03:50:52 +00:00

Author

SHA1

Message

Date

Pawan Dhananjay

3721f3a83c

Fix doppelganger script (#3988 )

## Issue Addressed

N/A

## Proposed Changes

The doppelganger tests were failing silently since the `PROPOSER_BOOST` config was not set. Sets the config and script returns an error if any subprocess fails.

2023-02-21 23:45:43 +00:00

realbigsean

ae5b141dc4

Updates to tests and local testnet for Ganache 7 (#3056 )

## Issue Addressed

#2961

## Proposed Changes

-- update `--chainId` -> `--chain.chainId`
-- remove `--keepAliveTimeout`
-- fix log to listen for
-- rename `ganache-cli` to `ganache` everywhere


Co-authored-by: realbigsean <sean@sigmaprime.io>

2022-03-20 22:48:14 +00:00

realbigsean

c5786a8821

Doppelganger detection (#2230 )

## Issue Addressed

Resolves #2069 

## Proposed Changes

- Adds a `--doppelganger-detection` flag
- Adds a `lighthouse/seen_validators` endpoint, which will make it so the lighthouse VC is not interopable with other client beacon nodes if the `--doppelganger-detection` flag is used, but hopefully this will become standardized. Relevant Eth2 API repo issue: https://github.com/ethereum/eth2.0-APIs/issues/64
- If the `--doppelganger-detection` flag is used, the VC will wait until the beacon node is synced, and then wait an additional 2 epochs. The reason for this is to make sure the beacon node is able to subscribe to the subnets our validators should be attesting on. I think an alternative would be to have the beacon node subscribe to all subnets for 2+ epochs on startup by default.

## Additional Info

I'd like to add tests and would appreciate feedback. 

TODO:  handle validators started via the API, potentially make this default behavior

Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: Michael Sproul <michael@sigmaprime.io>
Co-authored-by: Paul Hauner <paul@paulhauner.com>

2021-07-31 03:50:52 +00:00

3 Commits