Ethereum consensus client in Rust
Go to file
Michael Sproul 3dc1eb5eb6 Ignore inactive validators in validator monitor (#2396)
## Proposed Changes

A user on Discord (`@ChewsMacRibs`) reported that the validator monitor was logging `WARN Attested to an incorrect head` for their validator while it was awaiting activation.

This PR modifies the monitor so that it ignores inactive validators, by the logic that they are either awaiting activation, or have already exited. Either way, there's no way for an inactive validator to have their attestations included on chain, so no need for the monitor to report on them.

## Additional Info

To reproduce the bug requires registering validator keys manually with `--validator-monitor-pubkeys`. I don't think the bug will present itself with `--validator-monitor-auto`.
2021-06-17 02:10:48 +00:00
.github Enable Compatibility with Windows (#2333) 2021-05-19 23:05:16 +00:00
account_manager Add an account command to enable/disable validators (#2386) 2021-06-16 09:16:51 +00:00
beacon_node Ignore inactive validators in validator monitor (#2396) 2021-06-17 02:10:48 +00:00
book Monitoring service api (#2251) 2021-05-26 05:58:41 +00:00
boot_node v1.4.0 (#2402) 2021-06-10 01:44:49 +00:00
common Reorg events (#2090) 2021-06-17 02:10:46 +00:00
consensus Reorg events (#2090) 2021-06-17 02:10:46 +00:00
crypto VC: accept unknown fields in chain spec (#2277) 2021-03-26 04:53:57 +00:00
lcli v1.4.0 (#2402) 2021-06-10 01:44:49 +00:00
lighthouse Add an account command to enable/disable validators (#2386) 2021-06-16 09:16:51 +00:00
remote_signer Fix remote signer test (#2400) 2021-06-16 10:42:55 +00:00
scripts Add NETWORK_ID variable (#2330) 2021-05-12 00:51:20 +00:00
slasher Enable Compatibility with Windows (#2333) 2021-05-19 23:05:16 +00:00
testing Fix remote signer test (#2400) 2021-06-16 10:42:55 +00:00
validator_client Monitoring service api (#2251) 2021-05-26 05:58:41 +00:00
.dockerignore Use OS file locks in validator client (#1958) 2020-11-26 11:25:46 +00:00
.editorconfig Add editorconfig template 2019-03-11 15:09:57 +11:00
.gitignore Delete uncompressed genesis states (#2092) 2020-12-16 03:44:05 +00:00
.gitmodules Replace EF tests submodule with a makefile 2019-09-08 04:19:54 +10:00
bors.toml Add Windows to Bors config (#2358) 2021-05-20 00:23:08 +00:00
Cargo.lock v1.4.0 (#2402) 2021-06-10 01:44:49 +00:00
Cargo.toml Tune GNU malloc (#2299) 2021-05-28 05:59:45 +00:00
CONTRIBUTING.md Update CONTRIBUTING.md (#751) 2020-01-03 10:45:53 +11:00
Cross.toml Ensure RUSTFLAGS is passed through on cross compile (#1529) 2020-08-17 10:06:06 +00:00
Dockerfile Revert "Network protocol upgrades (#2345)" (#2388) 2021-06-02 01:07:28 +00:00
Dockerfile.cross Multiarch docker GitHub actions (#2065) 2020-12-09 06:06:37 +00:00
LICENSE Update License to Apache 2.0 2019-04-15 16:47:35 +10:00
Makefile VC: accept unknown fields in chain spec (#2277) 2021-03-26 04:53:57 +00:00
README.md Fix readme typo (#2312) 2021-04-14 02:30:54 +00:00

Lighthouse: Ethereum 2.0

An open-source Ethereum 2.0 client, written in Rust and maintained by Sigma Prime.

Build Status Book Status Chat Badge

Documentation

Banner

Overview

Lighthouse is:

  • Ready for use on Eth2 mainnet.
  • Fully open-source, licensed under Apache 2.0.
  • Security-focused. Fuzzing techniques have been continuously applied and several external security reviews have been performed.
  • Built in Rust, a modern language providing unique safety guarantees and excellent performance (comparable to C++).
  • Funded by various organisations, including Sigma Prime, the Ethereum Foundation, ConsenSys, the Decentralization Foundation and private individuals.
  • Actively involved in the specification and security analysis of the Ethereum 2.0 specification.

Eth2 Deposit Contract

The Lighthouse team acknowledges 0x00000000219ab540356cBB839Cbe05303d7705Fa as the canonical Eth2 deposit contract address.

Documentation

The Lighthouse Book contains information for users and developers.

The Lighthouse team maintains a blog at lighthouse.sigmaprime.io which contains periodical progress updates, roadmap insights and interesting findings.

Branches

Lighthouse maintains two permanent branches:

  • stable: Always points to the latest stable release.
    • This is ideal for most users.
  • unstable: Used for development, contains the latest PRs.
    • Developers should base their PRs on this branch.

Contributing

Lighthouse welcomes contributors.

If you are looking to contribute, please head to the Contributing section of the Lighthouse book.

Contact

The best place for discussion is the Lighthouse Discord server. Alternatively, you may use the sigp/lighthouse gitter.

Sign up to the Lighthouse Development Updates mailing list for email notifications about releases, network status and other important information.

Encrypt sensitive messages using our PGP key.

Donations

Lighthouse is an open-source project and a public good. Funding public goods is hard and we're grateful for the donations we receive from the community via:

  • Gitcoin Grants.
  • Ethereum address: 0x25c4a76E7d118705e7Ea2e9b7d8C59930d8aCD3b (donation.sigmaprime.eth).