Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update Cosmos Keyring setup links in peggo documentation #22

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .gitbook/nodes/validators/mainnet/peggo.md
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ Please note that the default keyring backend is `file` and that as such peggo wi

To use the default injectived key configuration, you should set the keyring path to the home directory of your injectived node, e.g., `~/.injectived`.

You can also read more about the Cosmos Keyring setup [here](https://docs.cosmos.network/main/run-node/keyring.html).
You can also read more about the Cosmos Keyring setup [here](https://docs.cosmos.network/v0.46/run-node/keyring.html).

#### **Option 2. Cosmos Private Key (Unsafe)**

Expand Down Expand Up @@ -279,7 +279,7 @@ journalctl -f -u peggo
This is an advanced DevOps topic, consult with your sysadmin.
{% endhint %}

Learn more about Cosmos Keyring setup [here](https://docs.cosmos.network/master/run-node/keyring.html). Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually the keyring is located within node's homedir, i.e. `~/.injectived/keyring-file`.
Learn more about Cosmos Keyring setup [here](https://docs.cosmos.network/v0.46/run-node/keyring.html). Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually the keyring is located within node's homedir, i.e. `~/.injectived/keyring-file`.

Some sections of the Injective Staking documentation will guide you through using this key for governance purposes, i.e. submitting transactions and setting up an Ethereum bridge. In order to protect the keys from unauthorized access, even when the keyring passphrase is leaked via configs, you can set OS permissions to allow disk access to `injectived` / `peggo` processes only.

Expand Down
4 changes: 2 additions & 2 deletions .gitbook/nodes/validators/testnet/testnet-peggo.md
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ Please note that the default keyring backend is `file` and that, as such, peggo

To use the default injectived key configuration, you should set the keyring path to the home directory of your injectived node, e.g. `~/.injectived`.

You can also read more about the Cosmos Keyring setup [here](https://docs.cosmos.network/master/run-node/keyring.html).
You can also read more about the Cosmos Keyring setup [here](https://docs.cosmos.network/v0.46/run-node/keyring.html).

#### **Option 2. Cosmos Private Key (Unsafe)**

Expand Down Expand Up @@ -372,7 +372,7 @@ journalctl -f -u peggo
This is an advanced DevOps topic, consult with your sysadmin.
{% endhint %}

Learn more about Cosmos Keyring setup [here](https://docs.cosmos.network/master/run-node/keyring.html). Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually, the keyring is located within node's homedir, i.e. `~/.injectived/keyring-file`.
Learn more about Cosmos Keyring setup [here](https://docs.cosmos.network/v0.46/run-node/keyring.html). Once you've launched your node, the default keyring will have the validator operator key stored on disk in the encrypted form. Usually, the keyring is located within node's homedir, i.e. `~/.injectived/keyring-file`.

Some sections of the Injective Staking documentation will guide you through using this key for governance purposes, i.e., submitting transactions and setting up an Ethereum bridge. In order to protect the keys from unauthorized access, even when the keyring passphrase is leaked via configs, you can set OS permissions to allow disk access to `injectived` / `peggo` processes only.

Expand Down