Skip to content
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
2 changes: 1 addition & 1 deletion crates/mgo/node.md
Original file line number Diff line number Diff line change
Expand Up @@ -274,7 +274,7 @@ It is recommended and often required that the `mgo` binary release/version match

### Updating On-chain Metadata

You can leverage [Validator Tool](validator_tool.md) to perform majority of the following tasks.
You can leverage [Validator Tool](validator.md) to perform majority of the following tasks.

An active/pending validator can update its on-chain metadata by submitting a transaction. Some metadata changes take effect immediately, including:

Expand Down
4 changes: 2 additions & 2 deletions crates/mgo/validator.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ $mgo validator update-metadata --help
```

#### Operation Cap
Operation Cap allows a validator to authorizer another account to perform certain actions on behalf of this validator. Read about [Operation Cap here](mgo_for_node_operators.md#operation-cap).
Operation Cap allows a validator to authorizer another account to perform certain actions on behalf of this validator. Read about [Operation Cap here](node.md).

The Operation Cap holder (either the valdiator itself or the delegatee) updates its Gas Price and reports validator peers with the Operation Cap.

Expand Down Expand Up @@ -180,7 +180,7 @@ $mgo validator make-validator-info <name> <description> <image-url> <project-url
```

This will generate a `validator.info` file and key pair files. The output of this command includes:
1. Four key pair files (Read [more here](mgo_for_node_operators.md#key-management)). ==Set their permissions with the minimal visibility (chmod 600, for example) and store them securely==. They are needed when running the validator node as covered below.
1. Four key pair files (Read [more here](node.md)). ==Set their permissions with the minimal visibility (chmod 600, for example) and store them securely==. They are needed when running the validator node as covered below.
a. If you follow this guide thoroughly, this key pair is actually copied from your `mgo.keystore` file.
2. `validator.info` file that contains your validator info. **Double check all information is correct**.

Expand Down
10 changes: 5 additions & 5 deletions mgo-ecology/docs/docs/references/cli.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,8 @@ Options:
-V, --version Print version
```

- **[MGO Client CLI](cli/client):** : Interact with the MGO network using the `mgo client` command.
- **[MGO Console CLI](cli/console):** : Open an interactive console with the currently active network using the `mgo console` command.
- **[MGO keytool CLI](cli/keytool):** : Utilize cryptographic tools using the `mgo keytool` command.
- **[MGO Move CLI](cli/move):** : Work with the Move programming language using the `mgo move` command.
- **[MGO Validator CLI](cli/validator):** : Access tools useful for MGO validators with the `mgo validator` command.
- **[MGO Client CLI](cli/client.mdx):** : Interact with the MGO network using the `mgo client` command.
- **[MGO Console CLI](cli/console.mdx):** : Open an interactive console with the currently active network using the `mgo console` command.
- **[MGO keytool CLI](cli/keytool.mdx):** : Utilize cryptographic tools using the `mgo keytool` command.
- **[MGO Move CLI](cli/move.mdx):** : Work with the Move programming language using the `mgo move` command.
- **[MGO Validator CLI](cli/validator.mdx):** : Access tools useful for MGO validators with the `mgo validator` command.