Skip to content

Commit

Permalink
Update faq.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@adr-sk
adr-sk authored Jun 25, 2024
1 parent ad8a9b0 commit bdd9f4d
Showing 1 changed file with 105 additions and 32 deletions.
137 changes: 105 additions & 32 deletions docs/gno-infrastructure/validators/faq.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,45 +8,86 @@ id: validators-faq

### What is a Gno.land validator?

Gno.land is based on [Tendermint2](https://docs.gno.land/concepts/tendermint2) that relies on a set of validators selected based on [Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) to secure the network. Validators are tasked with participating in consensus by committing new blocks and broadcasting votes. Validators are compensated with a portion of transaction fees generated in the network. In Gno.land, the voting power of all validators are equally weighted to achieve a high nakamoto coefficient and fairness.
Gno.land is based on [Tendermint2](https://docs.gno.land/concepts/tendermint2) that relies on a set of validators selected based
on [Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) to secure the network. Validators are tasked with
participating in consensus by committing new blocks and broadcasting votes.
Validators are compensated with a portion of transaction fees generated in the
network. In Gno.land, the voting power of all validators are equally weighted
to achieve a high nakamoto coefficient and fairness.

### What is Tendermint2?

[Tendermint2](https://docs.gno.land/concepts/tendermint2) (TM2) is the consensus protocol that powers Gno.land. TM2 is a successor of [Tendermint Core](https://github.com/tendermint/tendermint2), a de facto consensus framework for building Proof of Stake blockchains. The design philosophy of TM2 is to create “complete software” without any vulnerabilities with development focused on minimalism, dependency removal, and modularity.
[Tendermint2](https://docs.gno.land/concepts/tendermint2) (TM2) is the consensus protocol that powers Gno.land. TM2 is a successor
of [Tendermint Core](https://github.com/tendermint/tendermint2), a de facto consensus framework for building Proof of Stake
blockchains. The design philosophy of TM2 is to create “complete software”
without any vulnerabilities with development focused on minimalism, dependency
removal, and modularity.

### What is Proof of Contribution?

[Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) is a novel consensus mechanism that secures Gno.land. PoC weighs expertise and alignment with the project to evaluate the contribution of individuals or teams who govern and operate the chain. Unlike Proof of Stake (PoS), validators are selected via governance of Contributors based on their reputation and technical proficiency. The voting power of the network is equally distributed across all validators for higher decentralization. A portion of all transaction fees paid to the network are evenly shared between all validators to provide a fair incentive structure.
[Proof of Contribution](https://docs.gno.land/concepts/proof-of-contribution) (PoC) is a novel consensus mechanism that secures
Gno.land. PoC weighs expertise and alignment with the project to evaluate the
contribution of individuals or teams who govern and operate the chain. Unlike
Proof of Stake (PoS), validators are selected via governance of Contributors
based on their reputation and technical proficiency. The voting power of the
network is equally distributed across all validators for higher decentralization.
A portion of all transaction fees paid to the network are evenly shared between
all validators to provide a fair incentive structure.

### How does Gno.land differ from the Cosmos Hub?

In Cosmos Hub, validators are selected based on the amount of staked `ATOM` tokens delegated. This means that anyone with enough capital can join as a validator only to seek economic incentives without any alignment or technical expertise. This system leads to an undesirable incentive structure in which validators are rewarded purely based on the capital delegated, regardless of the quality of their infrastructure or service.
In Cosmos Hub, validators are selected based on the amount of staked `ATOM`
tokens delegated. This means that anyone with enough capital can join as a
validator only to seek economic incentives without any alignment or technical
expertise. This system leads to an undesirable incentive structure in which
validators are rewarded purely based on the capital delegated, regardless of
the quality of their infrastructure or service.

On the contrary, validators in Gno.land must be reviewed and verified to have made significant contributions in order to join the validator set. This property resembles the validator selection mechanism in [Proof of Authority](https://openethereum.github.io/Proof-of-Authority-Chains). Furthermore, all validators are evenly rewarded to ensure that the entire validator set is fairly incentivized to ensure the sustainability of the network.
On the contrary, validators in Gno.land must be reviewed and verified to have
made significant contributions in order to join the validator set. This property
resembles the validator selection mechanism in [Proof of Authority](https://openethereum.github.io/Proof-of-Authority-Chains). Furthermore,
all validators are evenly rewarded to ensure that the entire validator set
is fairly incentivized to ensure the sustainability of the network.

### What stage is the Gno.land project in?

Gno.land is currently in Testnet 3, the single-node testnet stage. The next version, Testnet 4, is scheduled to go live in Q2 2024, which will include a validator set implementation for a multinode environment.
Gno.land is currently in Testnet 3, the single-node testnet stage. The next
version, Testnet 4, is scheduled to go live in Q2 2024, which will include a
validator set implementation for a multinode environment.

## Becoming a Validator

### How do I join the testnet as a validator?

Out of many official Gno testnets, Testnet4 (`test4`) is the purpose-built network for testing the multi-node validator environment prior to mainnet launch. Testnet4 is scheduled to go live in Q2 2024 with genesis validators consisting of the Gno Core Team, partners, and external contributors.
Out of many official Gno testnets, Testnet4 (`test4`) is the purpose-built
network for testing the multi-node validator environment prior to mainnet
launch. Testnet4 is scheduled to go live in Q2 2024 with genesis validators
consisting of the Gno Core Team, partners, and external contributors.

For more information about joining testnet4, visit [the relevant issue](https://github.com/gnolang/hackerspace/issues/69). For more information about different testnets, visit [Gno Testnets](https://docs.gno.land/concepts/testnets).
For more information about joining testnet4, visit [the relevant issue](https://github.com/gnolang/hackerspace/issues/69). For more
information about different testnets, visit [Gno Testnets](https://docs.gno.land/concepts/testnets).

### What are the incentives for running a validator?

Network transaction fees paid on the Gno.land in `GNOT` are collected, from which a portion is directed to reward validators for their work. All validators fairly receive an equal amount of rewards.
Network transaction fees paid on the Gno.land in `GNOT` are collected, from
which a portion is directed to reward validators for their work. All validators
fairly receive an equal amount of rewards.

### How many validators will there be in mainnet?

The exact plans for mainnet are still TBD. Based on the latest discussions between contributors, the mainnet will likely have a validator set size of 20~50, which will gradually scale with the development and decentralization of the Gno.land project.
The exact plans for mainnet are still TBD. Based on the latest discussions
between contributors, the mainnet will likely have an inital validator set size
of 20~50, which will gradually scale with the development and decentralization
of the Gno.land project.

### How do I make my first contribution?

Gno.land is in active development and external contributions are always welcome! If you’re looking for tasks to begin with, we suggest you visit the [Bounties &](https://github.com/orgs/gnolang/projects/35/views/3) [Worx](https://github.com/orgs/gnolang/projects/35/views/3) board and search for open tasks up for grabs. Start from small challenges and work your way up to the bigger ones. Every contribution is acknowledged and highly regarded in PoC. We look forward to having you onboard as a new Contributor!
Gno.land is in active development and external contributions are always welcome!
If you’re looking for tasks to begin with, we suggest you visit the [Bounties &](https://github.com/orgs/gnolang/projects/35/views/3)
[Worx](https://github.com/orgs/gnolang/projects/35/views/3) board and search for open tasks up for grabs. Start from small challenges
and work your way up to the bigger ones. Every contribution is acknowledged and
highly regarded in PoC. We look forward to having you onboard as a new
Contributor!

## Technical Guides

Expand All @@ -60,46 +101,78 @@ Gno.land is in active development and external contributions are always welcome!

### What is a full node and a pruned node?

A full node fully validates transactions and blocks of a blockchain and keeps a full record of all historic activity. A pruned node is a lighter node that processes only block headers and does not keep all historical data of the blockchain post-verification. Pruned nodes are less resource intensive in terms of storage costs. Although validators may run either a full node or a pruned node, it is important to retain enough blocks to be able to validate new blocks.
A full node fully validates transactions and blocks of a blockchain and keeps a
full record of all historic activity. A pruned node is a lighter node that
processes only block headers and does not keep all historical data of the
blockchain post-verification. Pruned nodes are less resource intensive in terms
of storage costs. Although validators may run either a full node or a pruned
node, it is important to retain enough blocks to be able to validate new blocks.

## Technical References

### [How to generate a genesis.json](../../gno-tooling/cli/gnoland.md#gnoland-genesis-generate-flags)
### How do I generate `genesis.json`?

- Initialize the file that creates the initial state of the chain.
`genesis.json` is the file that is used to create the initial state of the chain.
To generate `genesis.json`, use the `gnoland genesis generate` command. Refer
to [this section](../../gno-tooling/cli/gnoland.md#gnoland-genesis-generate-flags) for various flags that allow you to manipulate the file.

### [How to add a validator to the genesis.json](../../gno-tooling/cli/gnoland.md#gnoland-genesis-validator-add-flags)
//TODO: Add tips or warnings for devs who are manipulating this file here, such as "blocks will not be produced if this file is corrupt"

- Add validators to create, validate, and propagate blocks.
### How do I add or remove validators from `genesis.json`?

### [How to add the balance information(addr and ugnot amount) to the genesis.json](../../gno-tooling/cli/gnoland.md#gnoland-genesis-balances-add-flags)
Validators inside `genesis.json` will be included in the validator set at
genesis. To manipulate the genesis validator set, use the
`gnoland genesis validator` command with the `add` or `remove` subcommands. Refer
to [this section](../../gno-tooling/cli/gnoland.md#gnoland-genesis-validator-flags) for flags that allow you to configure the name or the voting power
of the validator.

- Add wallet addresses to the chain initial state that will hold a certain amount of UGNOT coins.
### How do I add the balance information to the `genesis.json`?

### [How to initialize gno secrets](../../gno-tooling/cli/gnoland.md#gnoland-secrets-init-flags-)
You may premine coins to various addresses. To modify the balances of addresses
at genesis, use the `gnoland genesis balances` command with the `add` or `remove`
subcommands. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-genesis-balances-add-flags) for various flags that allow you to update
the entire balance sheet with a file or modify the balance of a single address.

- Initializes the secret information needed to run the validator, including the validator's private key, state, and node ID.
//TODO: Add tips or warnings here, such as "the only updatable coin is UGNOT" (or if any native coins are accepted)

### [How to get gno secrets](../../gno-tooling/cli/gnoland.md#gnoland-secrets-get-flags-)
### How do I initialize `gno secrets`?

- Retrieve the verifier's secret information.
The `gno secrets init` command allows you to initialize the private information
required to run the validator, including the validator node's private key, the
state, and the node ID. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-secrets-init-flags) for various flags that
allow you to define the output directory or to overwrite the existing secrets.

### [How to initialize gno node configuration](../../gno-tooling/cli/gnoland.md#gnoland-config-init-flags)
### How do I get `gno secrets`?

- Initialize the configs required to run a node.
To retrieve the private information of your validator node, use the
`gnoland-secrets-get` command. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-secrets-get-flags) for a flag that
allows you to define the output directory.

### [How to get gno node configuration](../../gno-tooling/cli/gnoland.md#gnoland-config-get)
### How do I initialize the gno node configurations?

- Retrieve the specific value of gno configs.
To initialize the configurations required to run a node, use the
`gnoland config init` command. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-config-init-flags) for various flags that
allow you to define the path or to overwrite the existing configurations.

### [How to edit gno node configuration](../../gno-tooling/cli/gnoland.md#gnoland-config-set)
### How do I get the current gno node configurations?

- Edit the specific value of gno configs.
To retrieve the specific values the current gno node configurations, use the
`gnoland config get` command. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-config-get) for a flag that allows
you to define the path to the configurations file.

### [How to start fresh gno chain with initializing](./start-a-new-gno-chain-and-validator.md)
### How do I edit the gno node configurations?

- Start a new chain after the initialization process.
To edit the specific value of gno node configurations, use the `gnoland-config set`
command. Refer to [this section](../../gno-tooling/cli/gnoland.md#gnoland-config-set) for a flag that allows
you to define the path to the configurations file.

### [How to connect existing gno chain](./connect-to-an-existing-gno-chain.md)
### How do I initialize and start a new gno chain?

- Connect exsiting gno chain.
To start an independent gno chain, follow the initialization process available
in [this section](./start-a-new-gno-chain-and-validator.md).

### How do I connect to an existing gno chain?

To join the validator set of a gno chain, you must first establish a connection.
Refer to [this section](./connect-to-an-existing-gno-chain.md) for a step-by-step
guide on how to connect to an existing gno chain.

0 comments on commit bdd9f4d

Please sign in to comment.