Ethereum consensus client in Rust
Go to file
blacktemplar 38b15deccb Fallback nodes for eth1 access (#1918)
## Issue Addressed

part of  #1883

## Proposed Changes

Adds a new cli argument `--eth1-endpoints` that can be used instead of `--eth1-endpoint` to specify a comma-separated list of endpoints. If the first endpoint returns an error for some request the other endpoints are tried in the given order.

## Additional Info

Currently if the first endpoint fails the fallbacks are used silently (except for `try_fallback_test_endpoint` that is used in `do_update` which logs a `WARN` for each endpoint that is not reachable). A question is if we should add more logs so that the user gets warned if his main endpoint is for example just slow and sometimes hits timeouts.
2020-11-27 08:37:44 +00:00
.github Update docs whenever unstable changes (#1969) 2020-11-25 03:20:23 +00:00
account_manager Use OS file locks in validator client (#1958) 2020-11-26 11:25:46 +00:00
beacon_node Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +00:00
book Add metrics to VC (#1954) 2020-11-26 01:10:51 +00:00
boot_node Update ENR construction and mainnet bootnodes (#1968) 2020-11-25 22:48:07 +00:00
common Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +00:00
consensus Implement slasher (#1567) 2020-11-23 03:43:22 +00:00
crypto Implement slasher (#1567) 2020-11-23 03:43:22 +00:00
hooks Add a flag to make lighthouse portable across machines (#1423) 2020-07-31 05:00:39 +00:00
lcli Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +00:00
lighthouse Fix #1964: remove mainnet warnings which no longer apply (#1970) 2020-11-25 23:56:21 +00:00
remote_signer Update remote signer README (#1870) 2020-11-07 03:06:17 +00:00
scripts Release v0.3.4 (#1894) 2020-11-13 06:06:35 +00:00
slasher Tweak slasher DB schema and pruning (#1948) 2020-11-23 21:33:51 +00:00
testing Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +00:00
validator_client Use OS file locks in validator client (#1958) 2020-11-26 11:25:46 +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 Implement slashing protection interchange format (#1544) 2020-10-02 01:42:27 +00:00
.gitmodules Replace EF tests submodule with a makefile 2019-09-08 04:19:54 +10:00
bors.toml Remove macos tests (#1687) 2020-09-30 01:27:36 +00:00
Cargo.lock Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +00:00
Cargo.toml Fallback nodes for eth1 access (#1918) 2020-11-27 08:37:44 +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 Release v0.3.4 (#1894) 2020-11-13 06:06:35 +00:00
LICENSE Update License to Apache 2.0 2019-04-15 16:47:35 +10:00
Makefile [Remote signer] Fold signer into Lighthouse repository (#1852) 2020-11-06 06:17:11 +00:00
README.md Update security details in README (#1956) 2020-11-24 10:29:39 +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 thier 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).