From cce153e2177d31ffa5e1800de5a8b098d9cad25b Mon Sep 17 00:00:00 2001 From: z-bowen Date: Thu, 23 Aug 2018 16:39:49 +0200 Subject: [PATCH] Problem: Docs needed a more specific description of how to input the path to the private-key file Solution: Changed the wording a bit --- docs/server/source/server-reference/bigchaindb-cli.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/server/source/server-reference/bigchaindb-cli.md b/docs/server/source/server-reference/bigchaindb-cli.md index 9bff3463..9f5c87d3 100644 --- a/docs/server/source/server-reference/bigchaindb-cli.md +++ b/docs/server/source/server-reference/bigchaindb-cli.md @@ -117,8 +117,8 @@ If the command succeeds, it will create an election and return an `election_id`. ```bash $ bigchaindb upsert-validator approve --private-key PATH_TO_YOUR_PRIVATE_KEY ``` - Here, `` is the transaction id of the election the approval should be given for. `--private-key` should be -the path to wherever the private key for your validator node is stored, (*not* the private key itself). + Here, `` is the transaction id of the election the approval should be given for. `--private-key` should be the path to Tendermint's private key which can be generally found at `/home/user/.tendermint/config/priv_validator.json`. + Example usage, ```bash $ bigchaindb upsert-validator approve 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa --private-key /home/user/.tendermint/config/priv_validator.json