Skip to content

Commit

Permalink
Fix docs
Browse files Browse the repository at this point in the history
  • Loading branch information
pawanjay176 committed Oct 22, 2020
1 parent 8c32281 commit fbf0bf5
Show file tree
Hide file tree
Showing 6 changed files with 10 additions and 10 deletions.
1 change: 1 addition & 0 deletions account_manager/src/validator/create.rs
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,7 @@ pub fn cli_run<T: EthSpec>(
ensure_dir_exists(&validator_dir)?;
ensure_dir_exists(&secrets_dir)?;

eprintln!("validator-dir path: {:?}", validator_dir);
eprintln!("secrets-dir path {:?}", secrets_dir);
eprintln!("wallets-dir path {:?}", wallet_base_dir);

Expand Down
1 change: 1 addition & 0 deletions account_manager/src/validator/import.rs
Original file line number Diff line number Diff line change
Expand Up @@ -86,6 +86,7 @@ pub fn cli_run(matches: &ArgMatches, validator_dir: PathBuf) -> Result<(), Strin
)
})?;

eprintln!("validator-dir path: {:?}", validator_dir);
// Collect the paths for the keystores that should be imported.
let keystore_paths = match (keystore, keystores_dir) {
(Some(keystore), None) => vec![keystore],
Expand Down
1 change: 1 addition & 0 deletions account_manager/src/validator/list.rs
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> {
}

pub fn cli_run(validator_dir: PathBuf) -> Result<(), String> {
eprintln!("validator-dir path: {:?}", validator_dir);
let mgr = ValidatorManager::open(&validator_dir)
.map_err(|e| format!("Unable to read --{}: {:?}", VALIDATOR_DIR_FLAG, e))?;

Expand Down
3 changes: 3 additions & 0 deletions account_manager/src/validator/recover.rs
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,9 @@ pub fn cli_run(matches: &ArgMatches, validator_dir: PathBuf) -> Result<(), Strin
let mnemonic_path: Option<PathBuf> = clap_utils::parse_optional(matches, MNEMONIC_FLAG)?;
let stdin_inputs = matches.is_present(STDIN_INPUTS_FLAG);

eprintln!("validator-dir path: {:?}", validator_dir);
eprintln!("secrets-dir path: {:?}", secrets_dir);

ensure_dir_exists(&validator_dir)?;
ensure_dir_exists(&secrets_dir)?;

Expand Down
1 change: 1 addition & 0 deletions account_manager/src/validator/slashing_protection.rs
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ pub fn cli_run<T: EthSpec>(
env: Environment<T>,
validator_base_dir: PathBuf,
) -> Result<(), String> {
eprintln!("validator-dir path: {:?}", validator_base_dir);
let slashing_protection_db_path = validator_base_dir.join(SLASHING_PROTECTION_FILENAME);

let genesis_validators_root = env
Expand Down
13 changes: 3 additions & 10 deletions book/src/voluntary-exit.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,30 +23,23 @@ To understand the phased rollout strategy for Eth2, please visit <https://ethere

In order to initiate an exit, users can use the `lighthouse account validator exit` command.

The `--validator` flag is used to specify the validator for which the user wants to initiate an exit transaction.
The `--keystore` flag is used to specify the path to the EIP-2335 voting keystore for the validator.

The `--beacon-node` flag is used to specify a beacon chain HTTP endpoint that confirms to the [Eth2.0 Standard API](https://ethereum.github.io/eth2.0-APIs/) specifications. That beacon node will be used to validate and propagate the voluntary exit. The default value for this flag is `http://localhost:5052`.

The `--testnet` flag is used to specify a particular testnet (default is `medalla`).

The `exit` command will search for the provided validator in the `validators-dir` (default `~/.lighthouse/{testnet}/validators`) directory and for the validator's password file in `secrets-dir` (default ` ~/.lighthouse/{testnet}/secrets`).

If the corresponding password file is not found in the `secrets-dir`, the user will be prompted for a password on the terminal.

[//]: # (Word this better or remove datadir part entirely)
Alternately, users can specify custom directories using `--validator-dir` and `--secrets-dir` flags or a custom parent directory using `--datadir`.

After validating the password, the user will be prompted to enter a special exit phrase as a final confirmation after which the voluntary exit will be published to the beacon chain.

The exit phrase is the following:
> Exit my validator


Below is an example for initiating a voluntary exit for validator `0xabcd` on the zinken testnet.
Below is an example for initiating a voluntary exit on the zinken testnet.

```
$ lighthouse --testnet zinken account validator exit --validator 0xabcd --beacon-node http://localhost:5052
$ lighthouse --testnet zinken account validator exit --keystore /path/to/keystore --beacon-node http://localhost:5052
Running account manager for zinken testnet
validator-dir path: ~/.lighthouse/zinken/validators
Expand Down

0 comments on commit fbf0bf5

Please sign in to comment.