Ethereum consensus client in Rust
Go to file
divma d727e55abe Move some rpc processing to the beacon_processor (#1936)
## Issue Addressed
`BlocksByRange` requests were the main culprit of a series of timeouts to peer's requests in general because they produce build up in the router's processor. Those were moved to the blocking executor but a task is being spawned for each; also not ideal since the amount of resources we give to those is not controlled

## Proposed Changes
- Move `BlocksByRange` and `BlocksByRoots` to the `beacon_processor`. The processor crafts the responses and sends them.
- Move too the processing of `StatusMessage`s from other peers. This is a fast operation but it can also build up and won't scale if we keep it in the router (processing one at the time). These don't need to send an answer, so there is no harm in processing them "later" if that were to happen. Sending responses to status requests is still in the router, so we answer as soon as we see them.
- Some "extras" that are basically clean up:
  - Split the `Worker` logic in sync methods (chain processing and rpc blocks), gossip methods (the majority of methods) and rpc methods (the new ones)
  - Move the `status_message` function previously provided by the router's processor to a more central place since it is used by the router, sync, network_context and beacon_processor
 - Some spelling

## Additional Info
What's left to decide/test more thoroughly is the length of the queues and the priority rules. @paulhauner suggested at some point to put status above attestations, and @AgeManning had described an importance of "protecting gossipsub" so my solution is leaving status requests in the router and RPC methods below attestations. Slashings and Exits are at the end.
2020-11-19 23:33:44 +00:00
.github Remove macos tests (#1687) 2020-09-30 01:27:36 +00:00
account_manager Bump to v0.3.5 (#1927) 2020-11-18 00:44:28 +00:00
beacon_node Move some rpc processing to the beacon_processor (#1936) 2020-11-19 23:33:44 +00:00
book Document system requirements (#1934) 2020-11-19 21:23:56 +00:00
boot_node Bump to v0.3.5 (#1927) 2020-11-18 00:44:28 +00:00
common [Remote signer] Add signer consumer lib (#1763) 2020-11-19 04:04:52 +00:00
consensus Avoid string initialization in network metrics and replace by &str where possible (#1898) 2020-11-18 23:31:37 +00:00
crypto Add validation to kdf parameters (#1930) 2020-11-19 08:52:51 +00:00
hooks Add a flag to make lighthouse portable across machines (#1423) 2020-07-31 05:00:39 +00:00
lcli Bump to v0.3.5 (#1927) 2020-11-18 00:44:28 +00:00
lighthouse Bump to v0.3.5 (#1927) 2020-11-18 00:44:28 +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
testing [Remote signer] Add signer consumer lib (#1763) 2020-11-19 04:04:52 +00:00
validator_client Reject invalid utf-8 characters during encryption (#1928) 2020-11-19 00:37:43 +00:00
.dockerignore Ensure .git is copied into docker (#1462) 2020-08-05 03:05:36 +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 [Remote signer] Add signer consumer lib (#1763) 2020-11-19 04:04:52 +00:00
Cargo.toml [Remote signer] Add signer consumer lib (#1763) 2020-11-19 04:04:52 +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 Add link to Lighthouse mailing list (#1913) 2020-11-16 06:28:11 +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

🚨🚨🚨 Note: Lighthouse is not yet ready to produce mainnet deposits. The developers will require some time to test against the mainnet deposit contract, once it is released. DO NOT SUBMIT VALIDATOR DEPOSITS WITH LIGHTHOUSE. 🚨🚨🚨

Overview

Lighthouse is:

  • Fully open-source, licensed under Apache 2.0.
  • Security-focused. Fuzzing has begun and security reviews are underway.
  • 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 and private individuals.
  • Actively involved in the specification and security analysis of the Ethereum 2.0 specification.

Like all Ethereum 2.0 clients, Lighthouse is a work-in-progress.

Eth2 Deposit Contract

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

Development Status

Current development overview:

  • Specification v1.0.0 implemented, optimized and passing test vectors.
  • Rust-native libp2p with Gossipsub and Discv5.
  • RESTful JSON API via HTTP server.
  • Events via WebSocket.
  • Metrics via Prometheus.

Roadmap

  • April 2019: Inital single-client testnets.
  • September 2019: Inter-operability with other Ethereum 2.0 clients.
  • Q1 2020: lighthouse-0.1.0 release: All major phase 0 features implemented.
  • Q2 2020: Public, multi-client testnet with user-facing functionality.
  • Q2 2020: Third-party security review.
  • Q4 2020: Long-lived, multi-client Beacon Chain testnet
  • Q4 2020: Additional third-party security reviews.
  • Q4 2020: Production Beacon Chain (tentative).

Documentation

The Lighthouse Book contains information for testnet users and developers.

If you'd like some background on Sigma Prime, please see the Lighthouse Update #00 blog post or sigmaprime.io.

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).