2020-09-29 03:46:54 +00:00
|
|
|
[package]
|
|
|
|
|
name = "http_metrics"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
authors = ["Paul Hauner <paul@paulhauner.com>"]
|
2022-02-25 00:10:17 +00:00
|
|
|
edition = "2021"
|
2020-09-29 03:46:54 +00:00
|
|
|
|
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
2021-11-18 05:08:42 +00:00
|
|
|
warp = "0.3.2"
|
2020-10-05 08:22:19 +00:00
|
|
|
serde = { version = "1.0.116", features = ["derive"] }
|
2020-09-29 03:46:54 +00:00
|
|
|
slog = "2.5.2"
|
|
|
|
|
beacon_chain = { path = "../beacon_chain" }
|
|
|
|
|
store = { path = "../store" }
|
Rename eth2_libp2p to lighthouse_network (#2702)
## Description
The `eth2_libp2p` crate was originally named and designed to incorporate a simple libp2p integration into lighthouse. Since its origins the crates purpose has expanded dramatically. It now houses a lot more sophistication that is specific to lighthouse and no longer just a libp2p integration.
As of this writing it currently houses the following high-level lighthouse-specific logic:
- Lighthouse's implementation of the eth2 RPC protocol and specific encodings/decodings
- Integration and handling of ENRs with respect to libp2p and eth2
- Lighthouse's discovery logic, its integration with discv5 and logic about searching and handling peers.
- Lighthouse's peer manager - This is a large module handling various aspects of Lighthouse's network, such as peer scoring, handling pings and metadata, connection maintenance and recording, etc.
- Lighthouse's peer database - This is a collection of information stored for each individual peer which is specific to lighthouse. We store connection state, sync state, last seen ips and scores etc. The data stored for each peer is designed for various elements of the lighthouse code base such as syncing and the http api.
- Gossipsub scoring - This stores a collection of gossipsub 1.1 scoring mechanisms that are continuously analyssed and updated based on the ethereum 2 networks and how Lighthouse performs on these networks.
- Lighthouse specific types for managing gossipsub topics, sync status and ENR fields
- Lighthouse's network HTTP API metrics - A collection of metrics for lighthouse network monitoring
- Lighthouse's custom configuration of all networking protocols, RPC, gossipsub, discovery, identify and libp2p.
Therefore it makes sense to rename the crate to be more akin to its current purposes, simply that it manages the majority of Lighthouse's network stack. This PR renames this crate to `lighthouse_network`
Co-authored-by: Paul Hauner <paul@paulhauner.com>
2021-10-19 00:30:39 +00:00
|
|
|
lighthouse_network = { path = "../lighthouse_network" }
|
2020-09-29 03:46:54 +00:00
|
|
|
slot_clock = { path = "../../common/slot_clock" }
|
|
|
|
|
lighthouse_metrics = { path = "../../common/lighthouse_metrics" }
|
|
|
|
|
lighthouse_version = { path = "../../common/lighthouse_version" }
|
|
|
|
|
warp_utils = { path = "../../common/warp_utils" }
|
2021-05-28 05:59:45 +00:00
|
|
|
malloc_utils = { path = "../../common/malloc_utils" }
|
2020-09-29 03:46:54 +00:00
|
|
|
|
|
|
|
|
[dev-dependencies]
|
2021-11-18 05:08:42 +00:00
|
|
|
tokio = { version = "1.14.0", features = ["sync"] }
|
2021-02-10 23:29:49 +00:00
|
|
|
reqwest = { version = "0.11.0", features = ["json"] }
|
2020-09-29 03:46:54 +00:00
|
|
|
environment = { path = "../../lighthouse/environment" }
|
|
|
|
|
types = { path = "../../consensus/types" }
|