0c529b8d52
## Issue Addressed Closes #2048 ## Proposed Changes * Broadcast slashings when the `--slasher-broadcast` flag is provided. * In the process of implementing this I refactored the slasher service into its own crate so that it could access the network code without creating a circular dependency. I moved the responsibility for putting slashings into the op pool into the service as well, as it makes sense for it to handle the whole slashing lifecycle.
19 lines
658 B
TOML
19 lines
658 B
TOML
[package]
|
|
name = "slasher_service"
|
|
version = "0.1.0"
|
|
authors = ["Michael Sproul <michael@sigmaprime.io>"]
|
|
edition = "2018"
|
|
|
|
[dependencies]
|
|
beacon_chain = { path = "../../beacon_node/beacon_chain" }
|
|
directory = { path = "../../common/directory" }
|
|
eth2_libp2p = { path = "../../beacon_node/eth2_libp2p" }
|
|
network = { path = "../../beacon_node/network" }
|
|
slasher = { path = ".." }
|
|
slog = "2.5.2"
|
|
slot_clock = { path = "../../common/slot_clock" }
|
|
state_processing = { path = "../../consensus/state_processing" }
|
|
task_executor = { path = "../../common/task_executor" }
|
|
tokio = { version = "0.3.5", features = ["full"] }
|
|
types = { path = "../../consensus/types" }
|