You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then navigate to `localhost:3000` in your browser.
92
92
93
93
To build documentation as a static website run `npm run build`. You will find the website in `build` directory.
94
+
After building the docs website you can start it with `npm run serve`.
94
95
95
-
## Search
96
96
97
-
We are using [Algolia](https://www.algolia.com) to power full-text search. This uses a public API search-only key in the `config.js` as well as a [cosmos_network.json](https://github.com/algolia/docsearch-configs/blob/master/configs/cosmos_network.json) configuration file that we can update with PRs.
98
-
99
-
### Update and Build the RPC docs
97
+
## Update and Build the RPC docs
100
98
101
99
1. Execute the following command at the root directory to install the swagger-ui generate tool.
Copy file name to clipboardexpand all lines: docs/docs/getting-started/installation.md
+48-19
Original file line number
Diff line number
Diff line change
@@ -20,29 +20,33 @@ Install `make` and `gcc`.
20
20
**Ubuntu:**
21
21
22
22
```bash
23
-
sudo apt-get update
23
+
sudo apt update
24
24
25
-
sudo apt-get install -y make gcc
25
+
sudo apt install -y make gcc build-essential
26
26
```
27
27
28
28
## Install Go
29
29
30
30
:::tip
31
-
**Go 1.21+** is required.
31
+
**Go 1.22+** is required.
32
32
:::
33
33
34
34
We suggest the following two ways to install Go. Check out the [official docs](https://golang.org/doc/install) and Go installer for the correct download for your operating system. Alternatively, you can install Go yourself from the command line. Detailed below are standard default installation locations, but feel free to customize.
35
35
36
+
Since the introduction of CosmWasm in Gaia v18 it is recommended to build the binaries with `CGO` enabled - simply set `CGO_ENABLED=1` in your terminal befre building the binary.
37
+
38
+
Building the `gaiad` binary on Windows is not supported due to [dependency issues](https://github.com/CosmWasm/wasmvm).
39
+
36
40
**[Go Binary Downloads](https://go.dev/dl/)**
37
41
38
42
**Ubuntu:**
39
43
40
-
At the time of this writing, the latest release is `1.21.7`. We're going to download the tarball, extract it to `/usr/local`, and export `GOROOT` to our `$PATH`
44
+
At the time of this writing, the latest release is `1.22.3`. We're going to download the tarball, extract it to `/usr/local`, and export `GOROOT` to our `$PATH`
In case you need to build a binary with all dependencies statically linked please check our [Dockerfile](https://github.com/cosmos/gaia/blob/main/Dockerfile).
122
+
123
+
You must have `libwasmvm` available on your machine.
124
+
Choose the build that matches your platform and OS:
The Cosmos Hub is based on [CometBFT](https://docs.cometbft.com/v0.37/introduction/what-is-cometbft) that relies on a set of validators that are responsible for committing new blocks in the blockchain. These validators participate in the consensus protocol by broadcasting votes that contain cryptographic signatures signed by each validator's private key.
12
9
13
-
Validator candidates can bond their own ATOM and have ATOM ["delegated"](../delegators/delegator-guide-cli.md), or staked, to them by token holders. The Cosmos Hub has <Varchildren={currentParams.staking.MaxValidators} /> validators, see Proposal <Varchildren={currentParams.proposals.numberOfValidatorsProp} />, but over time the number of validators can be increased with governance proposals. The validators are determined by the total number of ATOM tokens delegated to them — the top <Varchildren={currentParams.staking.MaxValidators} /> validator candidates with the most voting power are the current Cosmos validators.
10
+
Validator candidates can bond their own ATOM and have ATOM ["delegated"](../delegators/delegator-guide-cli.md), or staked, to them by token holders. The Cosmos Hub has 180 active validators, but over time the number of validators can be changed through governance (`MaxValidators` parameter). Validator voting power is determined by the total number of ATOM tokens delegated to them. Validators that do not have enough voting power to be in the top 180 are considered inactive. Inactive validators can become active if their staked amount increases so that they fall into the top 180 validators.
14
11
15
12
Validators and their delegators earn ATOM as block provisions and tokens as transaction fees through execution of the Tendermint consensus protocol. Note that validators can set a commission percentage on the fees their delegators receive as additional incentive. You can find an overview of all current validators and their voting power on [Mintscan](https://www.mintscan.io/cosmos/validators).
0 commit comments