[Remote signer] Fold signer into Lighthouse repository (#1852)

The remote signer relies on the `types` and `crypto/bls` crates from Lighthouse. Moreover, a number of tests of the remote signer consumption of LH leverages this very signer, making any important update a potential dependency nightmare.

Co-authored-by: Paul Hauner <paul@paulhauner.com>
This commit is contained in:
Herman Junge
2020-11-06 06:17:11 +00:00
parent e2ae5010a6
commit e004b98eab
38 changed files with 3211 additions and 6 deletions

View File

@@ -125,6 +125,7 @@ fn main() {
.subcommand(boot_node::cli_app())
.subcommand(validator_client::cli_app())
.subcommand(account_manager::cli_app())
.subcommand(remote_signer::cli_app())
.get_matches();
// Debugging output for libp2p and external crates.
@@ -292,7 +293,7 @@ fn run<E: EthSpec>(
.shutdown_sender()
.try_send("Failed to start beacon node");
}
})
});
}
("validator_client", Some(matches)) => {
let context = environment.core_context();
@@ -316,7 +317,17 @@ fn run<E: EthSpec>(
.shutdown_sender()
.try_send("Failed to start validator client");
}
})
});
}
("remote_signer", Some(matches)) => {
if let Err(e) = remote_signer::run(&mut environment, matches) {
crit!(log, "Failed to start remote signer"; "reason" => e);
let _ = environment
.core_context()
.executor
.shutdown_sender()
.try_send("Failed to start remote signer");
}
}
_ => {
crit!(log, "No subcommand supplied. See --help .");