Introduce delegate-stake.sh for adding stake to a validator.sh (#5380)

This commit is contained in:
Michael Vines
2019-08-01 13:48:00 -07:00
committed by GitHub
parent 4d14abbd04
commit 870503ee36
4 changed files with 150 additions and 36 deletions

View File

@@ -222,7 +222,6 @@ $ solana-keygen pubkey ~/.local/share/solana/install/active_release/config/valid
$ solana-keygen pubkey ./config/validator-vote-keypair.json
```
#### Validator Metrics
Metrics are available for local monitoring of your validator.
@@ -282,3 +281,33 @@ Keybase:
`https://keybase.pub/<KEYBASE_USERNAME>/solana/validator-<PUBKEY>`
3. Add or update your `solana-validator-info` with your Keybase username. The
CLI will verify the `validator-<PUBKEY>` file
### Staking
When your validator starts it will have no stake, which means it will ineligible to become leader.
Adding stake can be accomplished by using the `solana-wallet` command. First
obtain the public key for your validator's vote account with:
```bash
$ solana-keygen pubkey ~/validator-config/vote-keypair.json
```
This will output a base58-encoded value that looks similar to
`DhUYZR98qFLLrnHg2HWeGhBQJ9tru7nwdEfYm8L8HdR9`. Then create a stake account
keypair with `solana-keygen`:
```bash
$ solana-keygen new -o ~/validator-config/stake-keypair.json
```
and use the wallet's `delegate-stake` command to stake your validator with 42 lamports:
```bash
$ solana-wallet delegate-stake ~/validator-config/stake-keypair.json [VOTE PUBKEY] 42
```
Note that stake changes are applied at Epoch boundaries so it can take an hour
or more for the change to take effect.
Stake can be deactivate by running:
```bash
$ solana-wallet deactivate-stake ~/validator-config/stake-keypair.json
```
Note that a stake account may only be used once, so after deactivation use the
wallet's `withdraw-stake` command to recover the previously staked lamports.