diff --git a/docs/DOCS_README.md b/docs/DOCS_README.md index 0ceca6269ec..5ddfb8e6fb7 100644 --- a/docs/DOCS_README.md +++ b/docs/DOCS_README.md @@ -17,7 +17,7 @@ built from the files in this (`/docs`) directory for [main](https://github.com/c ### How It Works -There is a [Github Action](https://github.com/cosmos/gaia/blob/main/.github/workflows/docs.yml) +There is a [Github Action](https://github.com/cosmos/gaia/blob/main/.github/workflows/deploy-docs.yml) listening for changes in the `/docs` directory, on the `main` branch. Any updates to files in this directory on that branch will automatically trigger a website deployment. Under the hood, `make build-docs` is run from the diff --git a/docs/README.md b/docs/README.md index 420d6daaa1e..92175bea2d0 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1,27 +1,21 @@ - - # Cosmos Hub Documentation Welcome to the documentation of the **Cosmos Hub application: `gaia`**. ## What is Gaia? -- [Intro to the `gaia` software](./getting-started/what-is-gaia.md) -- [Interacting with the `gaiad` binary](./hub-tutorials/gaiad.md) +- [Intro to the `gaia` software](./docs/getting-started/what-is-gaia.md) +- [Interacting with the `gaiad` binary](./docs/hub-tutorials/gaiad.md) ## Join the Cosmos Hub Mainnet -- [Install the `gaia` application](./getting-started/installation.md) -- [Set up a full node and join the mainnet](./hub-tutorials/join-mainnet.md) -- [Upgrade to a validator node](./validators/validator-setup.md) +- [Install the `gaia` application](./docs/getting-started/installation.md) +- [Set up a full node and join the mainnet](./docs/hub-tutorials/join-mainnet.md) +- [Upgrade to a validator node](./docs/validators/validator-setup.md) ## Join the Cosmos Hub Public Testnet -- [Join the testnet](./hub-tutorials/join-testnet.md) +- [Join the testnet](./docs/hub-tutorials/join-testnet.md) ## Setup Your Own `gaia` Testnet @@ -29,10 +23,10 @@ Welcome to the documentation of the **Cosmos Hub application: `gaia`**. ## Additional Resources -- [Validator Resources](./validators/README.md): Contains documentation for `gaia` validators. -- [Delegator Resources](./delegators/README.md): Contains documentation for delegators. -- [Other Resources](./resources/README.md): Contains documentation on `gaiad`, genesis file, service providers, ledger wallets, ... -- [Cosmos Hub Archives](./resources/archives.md): State archives of past iteration of the Cosmos Hub. +- [Validator Resources](./docs/validators/README.md): Contains documentation for `gaia` validators. +- [Delegator Resources](./docs/delegators/README.md): Contains documentation for delegators. +- [Other Resources](./docs/resources/README.md): Contains documentation on `gaiad`, genesis file, service providers, ledger wallets, ... +- [Cosmos Hub Archives](./docs/resources/archives.md): State archives of past iteration of the Cosmos Hub. # Contribute diff --git a/docs/docs/architecture/adr/adr-002-globalfee.md b/docs/docs/architecture/adr/adr-002-globalfee.md index 0647da5e670..d7e1e32d2f1 100644 --- a/docs/docs/architecture/adr/adr-002-globalfee.md +++ b/docs/docs/architecture/adr/adr-002-globalfee.md @@ -98,17 +98,22 @@ Checking `feeCoinsNonZeroDenom` against `nonZeroCoinFeesReq`: } ``` -Here is an example of how the coins split and checked in fee antehandler:\ -**assumption**:\ +Here is an example of how the coins split and checked in fee antehandler: + +**assumption**: + `globalfee=[1photon, 0uatom, 1stake]` and `local min-gas-prices=[0.5stake]` -**fee requirement**:\ +**fee requirement**: + `combinedFeeRequirement=[1photon, 0uatom, 1stake]` -**split fee requirement**:\ +**split fee requirement**: + the `combinedFeeRequirement` into `nonZeroCoinFeesReq=[0uatom]`, and `nonZeroCoinFeesReq=[1photon, 1stake]` -**split the paid fees**:\ +**split the paid fees**: + if `paidFee=[1uatom, 0.5photon]`, the `splitCoinsByDenoms` splits the paidFee into `feeCoinsZeroDenom=[1uatom]` (the same denom as zero coins in `combinedFeeRequirement`), and `feeCoinsNonZeroDenom=[0.5stake]` then `feeCoinsZeroDenom=[1uatom]` is checked by `nonZeroCoinFeesReq=[1photon, 1stake]`. @@ -121,7 +126,7 @@ Please note that `feeCoins` does not contain zero coins. The fee coins are split ### Fee Checks in `DeliverTx` Implementing fee checks within the `DeliverTx` function introduces a few requirements: -- **Deterministic Minimum Fee Requirement**: For the `DeliverTx` process, it is essential to have a deterministic minimum fee requirement. In `CheckTx`, fee is checked by the `CombinedFeeRequirement(globalFees, localFees)`, which considers both `minimum-gas-prices` from `config/app.toml` and `MinimumGasPricesParam` from the globalfee Params (For more details, see [globalfee.md](/modules/globalfee.md)). `CombinedFeeRequirement` contains non-deterministic part: `minimum-gas-prices` from `app.toml`. Therefore, `CombinedFeeRequirement` cannot be used in `DeliverTx`. In `DeliverTx`, only `MinimumGasPricesParam` in globalfee Params is used for fee verification. The code implementation is shown below. +- **Deterministic Minimum Fee Requirement**: For the `DeliverTx` process, it is essential to have a deterministic minimum fee requirement. In `CheckTx`, fee is checked by the `CombinedFeeRequirement(globalFees, localFees)`, which considers both `minimum-gas-prices` from `config/app.toml` and `MinimumGasPricesParam` from the globalfee Params (For more details, see [globalfee](../../modules/globalfee.md)). `CombinedFeeRequirement` contains non-deterministic part: `minimum-gas-prices` from `app.toml`. Therefore, `CombinedFeeRequirement` cannot be used in `DeliverTx`. In `DeliverTx`, only `MinimumGasPricesParam` in globalfee Params is used for fee verification. The code implementation is shown below. ```go func (mfd FeeDecorator) GetTxFeeRequired(ctx sdk.Context, tx sdk.FeeTx) (sdk.Coins, error) { @@ -162,4 +167,4 @@ The introduction of FeeDecorator has replaced the usage of `MempoolFeeDecorator` ## References -* [Documentation of the globalfee module](/modules/globalfee.md) +* [Documentation of the globalfee module](../../modules/globalfee) diff --git a/docs/docs/architecture/templates/adr-template.md b/docs/docs/architecture/templates/adr-template.md index e49f676f951..b1c376897e4 100644 --- a/docs/docs/architecture/templates/adr-template.md +++ b/docs/docs/architecture/templates/adr-template.md @@ -12,7 +12,7 @@ order: false {DRAFT | PROPOSED} Not Implemented -> Please have a look at the [PROCESS](/architecture/adr/PROCESS.md#adr-status) page. +> Please have a look at the [PROCESS](../adr/PROCESS#adr-status) page. > Use DRAFT if the ADR is in a draft stage (draft PR) or PROPOSED if it's in review. ## Abstract diff --git a/docs/docs/changelogs/v15.1.0.md b/docs/docs/changelogs/v15.1.0.md index d2a367ee143..46808c78ec8 100644 --- a/docs/docs/changelogs/v15.1.0.md +++ b/docs/docs/changelogs/v15.1.0.md @@ -1,6 +1,5 @@ --- title: v15.1.0 -order: 1 --- This document outlines API breaking changes that were introduced in `gaia v15.1.0`. diff --git a/docs/docs/changelogs/v16.0.0.md b/docs/docs/changelogs/v16.0.0.md new file mode 100644 index 00000000000..b87b54c212a --- /dev/null +++ b/docs/docs/changelogs/v16.0.0.md @@ -0,0 +1,57 @@ +--- +title: v16.0.0 +order: 1 +--- + +This document changes that were introduced in `gaia v16.0.0`. + +This release is based on cosmos-sdk `v0.47.x`, ibc-go `v7.x` and cometBFT `v0.37.5`. + +You can find the comprehensive API docs at: +* https://docs.cosmos.network/api + +Module reference manuals (with CLI instructions) can be found at: +* https://docs.cosmos.network/v0.47/build/modules + +Comprehensive list of changes: +* https://github.com/cosmos/gaia/blob/v16.0.0/CHANGELOG.md + +## Supported modules: +cosmos-sdk `v0.47.13-ics-lsm` +* x/auth +* x/authz +* x/bank +* x/capability +* x/consensus +* x/crisis +* x/distribution +* x/evidence +* x/feegrant +* x/gov +* x/mint +* x/params +* x/slashing +* x/staking (with LSM changes) +* x/upgrade + +ibc protocols +* transfer +* ica host +* ica controller +* interchain-security/provider `v4.1.0-lsm` + +ibc-middleware +* packetforward `v7.x` +* [ibcfee](https://ibc.cosmos.network/v7/middleware/ics29-fee/overview) `v7.x` +* [ibc-rate-limiting](https://github.com/Stride-Labs/ibc-rate-limiting) + +gaia +* x/globalfee +* x/metaprotocols + +# Important changes + +This version enables relayer incentivization for newly created IBC channels, adds ICA controller functionality and imposes limits on the amount of outgoing ATOM IBC transfers. + +With the upgrade of the ICS provider module, the amount of relayer traffic gets significantly reduced due to the introduction of epochs. With epochs, the ICS protocol aggregates validator set updates and sends them every 600 blocks (1 packet/hour) instead of every block. This feature is intended to reduce relayer costs and encourage relayer participation. + \ No newline at end of file diff --git a/docs/docs/delegators/delegator-faq.md b/docs/docs/delegators/delegator-faq.md index 63cc8d87279..d53fd575590 100644 --- a/docs/docs/delegators/delegator-faq.md +++ b/docs/docs/delegators/delegator-faq.md @@ -5,7 +5,7 @@ order: 4 ## What is a delegator? -People that cannot or do not want to operate [validator nodes](/validators/overview.mdx) can still participate in the staking process as delegators. Indeed, validators are not chosen based on their self-delegated stake but based on their total stake, which is the sum of their self-delegated stake and of the stake that is delegated to them. This is an important property, as it makes delegators a safeguard against validators that exhibit bad behavior. If a validator misbehaves, their delegators will move their Atoms away from them, thereby reducing their stake. Eventually, if a validator's stake falls under the top 180 addresses with highest stake, they will exit the validator set. +People that cannot or do not want to operate [validator nodes](../validators/overview.mdx) can still participate in the staking process as delegators. Indeed, validators are not chosen based on their self-delegated stake but based on their total stake, which is the sum of their self-delegated stake and of the stake that is delegated to them. This is an important property, as it makes delegators a safeguard against validators that exhibit bad behavior. If a validator misbehaves, their delegators will move their Atoms away from them, thereby reducing their stake. Eventually, if a validator's stake falls under the top 180 addresses with highest stake, they will exit the validator set. **Delegators share the revenue of their validators, but they also share the risks.** In terms of revenue, validators and delegators differ in that validators can apply a commission on the revenue that goes to their delegator before it is distributed. This commission is known to delegators beforehand and can only change according to predefined constraints (see [section](#choosing-a-validator) below). In terms of risk, delegators' Atoms can be slashed if their validator misbehaves. For more, see [Risks](#risks) section. diff --git a/docs/docs/delegators/delegator-guide-cli.md b/docs/docs/delegators/delegator-guide-cli.md index 550da38fc77..3525dbc2fde 100644 --- a/docs/docs/delegators/delegator-guide-cli.md +++ b/docs/docs/delegators/delegator-guide-cli.md @@ -58,7 +58,7 @@ Please exercise extreme caution! [**Download the binaries**] Not available yet. -[**Install from source**](../getting-started/installation.md) +[**Install from source**](../getting-started/installation) :::tip `gaiad` is used from a terminal. To open the terminal, follow these steps: @@ -259,7 +259,7 @@ In order to query the state and send transactions, you need a way to access the This is the most secure option, but comes with relatively high resource requirements. In order to run your own full-node, you need good bandwidth and at least 1TB of disk space. -You will find the tutorial on how to install `gaiad` [here](../getting-started/installation.md), and the guide to run a full-node [here](../hub-tutorials/join-mainnet.md). +You will find the tutorial on how to install `gaiad` [here](../getting-started/installation), and the guide to run a full-node [here](../hub-tutorials/join-mainnet). ### Connecting to a Remote Full-Node @@ -397,7 +397,7 @@ gaiad tx bank send [from_key_or_address] [to_address] [amount] [flags] ::: :::warning -**Before bonding Atoms, please read the [delegator faq](https://cosmos.network/resources/delegators) to understand the risk and responsibilities involved with delegating** +**Before bonding Atoms, please read the [delegator faq](https://hub.cosmos.network/delegators/delegator-faq) to understand the risk and responsibilities involved with delegating** ::: :::warning diff --git a/docs/docs/delegators/delegator-security.md b/docs/docs/delegators/delegator-security.md index 44f7c8130e8..261045aa36c 100644 --- a/docs/docs/delegators/delegator-security.md +++ b/docs/docs/delegators/delegator-security.md @@ -7,7 +7,7 @@ The launch of any public blockchain is an incredibly exciting time, and it's def ## Social Engineering -[Social engineering](https://en.wikipedia.org/wiki/Social_engineering_(security)) has existed for about as long as human beings have been on the planet, and in the technical era, it usually takes in the form of [phishing](https://ssd.eff.org/en/module/how-avoid-phishing-attacks) or [spearphishing](https://en.wikipedia.org/wiki/Phishing#Spear_phishing) . Both of these attacks are wildly successful forms of trickery that are responsible for over 95% of account security breaches, and they don't just happen via email: these days, opportunistic and targeted phishing attempts take place [anywhere that you have an inbox](https://www.umass.edu/it/security/phishing-fraudulent-emails-text-messages-phone-calls) . It doesn't matter if you're using Signal, Telegram, SMS, Twitter, or just checking your DMs on forums or social networks, attackers have a [plethora of opportunities](https://jia.sipa.columbia.edu/weaponization-social-media-spear-phishing-and-cyberattacks-democracy) to gain foothold in your digital life in effort to separate you from valuable information and assets that you most definitely don't want to lose. If a deal pops up that [sounds too good to be true](https://www.psychologytoday.com/us/blog/mind-in-the-machine/201712/how-fear-is-being-used-manipulate-cryptocurrency-markets) , or a message shows up asking for information that should never, ever be shared with someone else, you can always verify it before engaging with it by navigating to our official website or an official Cosmos communication channel on your own. +[Social engineering](https://en.wikipedia.org/wiki/Social_engineering_(security)) has existed for about as long as human beings have been on the planet, and in the technical era, it usually takes in the form of [phishing](https://ssd.eff.org/en/module/how-avoid-phishing-attacks) or [spearphishing](https://en.wikipedia.org/wiki/Phishing#Spear_phishing) . Both of these attacks are wildly successful forms of trickery that are responsible for over 95% of account security breaches, and they don't just happen via email: these days, opportunistic and targeted phishing attempts take place [anywhere that you have an inbox](https://www.umass.edu/it/security/phishing-fraudulent-emails-text-messages-phone-calls) . It doesn't matter if you're using Signal, Telegram, SMS, Twitter, or just checking your DMs on forums or social networks, attackers have a [plethora of opportunities](https://lucris.lub.lu.se/ws/portalfiles/portal/85420559/The_Weaponization_of_Social_Media_Bossetta_2018_.pdf) to gain foothold in your digital life in effort to separate you from valuable information and assets that you most definitely don't want to lose. If a deal pops up that [sounds too good to be true](https://www.psychologytoday.com/us/blog/mind-in-the-machine/201712/how-fear-is-being-used-manipulate-cryptocurrency-markets) , or a message shows up asking for information that should never, ever be shared with someone else, you can always verify it before engaging with it by navigating to our official website or an official Cosmos communication channel on your own. * **Be skeptical of unexpected attachments, or emails that ask you to visit a suspicious or unfamiliar website in the context of blockchains or cryptocurrency.** An attacker may attempt to lure you to a [compromised site](https://blog.malwarebytes.com/cybercrime/2013/02/tools-of-the-trade-exploit-kits/) designed to steal sensitive information from your computer. If you're a Gmail user, test your resilience against the latest email-based phishing tactics [here](https://phishingquiz.withgoogle.com/) . diff --git a/docs/docs/getting-started/installation.md b/docs/docs/getting-started/installation.md index 9fccaef73f8..52ba392e9b6 100644 --- a/docs/docs/getting-started/installation.md +++ b/docs/docs/getting-started/installation.md @@ -1,6 +1,6 @@ --- title: Installing Gaia -order: 2 +sidebar_position: 2 --- This guide will explain how to install the `gaiad` binary and run the cli. With this binary installed on a server, you can participate on the mainnet as either a [Full Node](../hub-tutorials/join-mainnet.md) or a [Validator](../validators/validator-setup.md). @@ -121,4 +121,4 @@ The `replace` clause you add to `go.mod` must provide the correct import path: ## Next -Now you can [join the mainnet](../hub-tutorials/join-mainnet.md), [the public testnet](../hub-tutorials/join-testnet.md). +Now you can [join the mainnet](../hub-tutorials/join-mainnet), [the public testnet](../hub-tutorials/join-testnet). diff --git a/docs/docs/getting-started/quickstart.mdx b/docs/docs/getting-started/quickstart.mdx index 2e167042e27..0b6388563da 100644 --- a/docs/docs/getting-started/quickstart.mdx +++ b/docs/docs/getting-started/quickstart.mdx @@ -1,6 +1,6 @@ --- title: Quick Start - Join Mainnet -order: 3 +sidebar_position: 3 --- import Tabs from '@theme/Tabs'; diff --git a/docs/docs/getting-started/system-requirements.md b/docs/docs/getting-started/system-requirements.md index fbb13d0dbeb..e7c4357a637 100644 --- a/docs/docs/getting-started/system-requirements.md +++ b/docs/docs/getting-started/system-requirements.md @@ -1,3 +1,8 @@ +--- +title: System requirements +sidebar_position: 4 +--- + # System requirements diff --git a/docs/docs/getting-started/what-is-gaia.md b/docs/docs/getting-started/what-is-gaia.md index 0a7f09749cb..bda526d78c0 100644 --- a/docs/docs/getting-started/what-is-gaia.md +++ b/docs/docs/getting-started/what-is-gaia.md @@ -1,24 +1,56 @@ --- title: What is Gaia? -order: 1 +sidebar_position: 1 --- -`gaia` is the name of the Cosmos SDK application for the Cosmos Hub. It comes with 2 main entrypoints: +The Cosmos Hub is a public Proof-of-Stake chain that uses ATOM as its native staking token. It is the first blockchain launched in the Cosmos Network and developed using the [cosmos-sdk](https://docs.cosmos.network/) development framework and [ibc-go](https://ibc.cosmos.network/). -- `gaiad`: The Gaia Daemon and command-line interface (CLI). runs a full-node of the `gaia` application. +Cosmos hub is also the first security aggregation platform that leverages the [interchain-security](https://cosmos.github.io/interchain-security/) protocol ([ICS-28](https://github.com/cosmos/ibc/tree/main/spec/app/ics-028-cross-chain-validation)) to facilitate the launch of cosmos-sdk blockchain projects. -`gaia` is built on the Cosmos SDK using the following modules: -- `x/auth`: Accounts and signatures. -- `x/bank`: Token transfers. -- `x/staking`: Staking logic. -- `x/mint`: Inflation logic. -- `x/distribution`: Fee distribution logic. -- `x/slashing`: Slashing logic. -- `x/gov`: Governance logic. -- `ibc-go/modules`: Inter-blockchain communication. Hosted in the `cosmos/ibc-go` repository. -- `x/params`: Handles app-level parameters. +:::tip +Interchain security features deployed on the Cosmos Hub blockchain allow anyone to launch a blockchain using a subset, or even the entire validator set of the Cosmos Hub blockchain. +::: + + +:::info +* `gaia` is the name of the Cosmos SDK application for the Cosmos Hub. + +* `gaiad` is the daemon and command-line interface (CLI) that operates the `gaia` blockchain application. +::: + + +The `gaia` blockchain uses the following cosmos-sdk, ibc-go and interchain-security modules, alongside some others: + +## cosmos-sdk +* [x/auth](https://docs.cosmos.network/v0.47/build/modules/auth) +* [x/authz](https://docs.cosmos.network/v0.47/build/modules/authz) +* [x/bank](https://docs.cosmos.network/v0.47/build/modules/bank) +* [x/capability](https://docs.cosmos.network/v0.47/build/modules/capability) +* [x/consensus](https://docs.cosmos.network/v0.47/build/modules/consensus) +* [x/crisis](https://docs.cosmos.network/v0.47/build/modules/crisis) +* [x/distribution](https://docs.cosmos.network/v0.47/build/modules/distribution) +* [x/evidence](https://docs.cosmos.network/v0.47/build/modules/evidence) +* [x/feegrant](https://docs.cosmos.network/v0.47/build/modules/feegrant) +* [x/gov](https://docs.cosmos.network/v0.47/build/modules/gov) +* [x/mint](https://docs.cosmos.network/v0.47/build/modules/mint) +* [x/params](https://docs.cosmos.network/v0.47/build/modules/params) +* [x/slashing](https://docs.cosmos.network/v0.47/build/modules/slashing) +* [x/staking (with LSM changes)](https://docs.cosmos.network/v0.47/build/modules/staking) +* [x/upgrade](https://docs.cosmos.network/v0.47/build/modules/upgrade) + +## ibc-go +* [transfer](https://ibc.cosmos.network/main/apps/transfer/overview) +* [interchain accounts - host](https://ibc.cosmos.network/v8/apps/interchain-accounts/client#host) +* [interchain accounts - controller](https://ibc.cosmos.network/v8/apps/interchain-accounts/client#controller) +* [interchain-security/provider](https://github.com/cosmos/interchain-security/tree/main/x/ccv/provider) +* [packetforward](https://github.com/cosmos/ibc-apps/tree/main/middleware/packet-forward-middleware) +* [ibcfee](https://ibc.cosmos.network/v7/middleware/ics29-fee/overview) +* [ibc-rate-limiting](https://github.com/Stride-Labs/ibc-rate-limiting) + +## gaia specific modules +* [x/globalfee](https://github.com/cosmos/gaia/tree/main/x/globalfee) +* [x/metaprotocols](https://github.com/cosmos/gaia/tree/main/x/metaprotocols) -About the Cosmos Hub: The Cosmos Hub is the first Hub to be launched in the Cosmos Network. The role of a Hub is to facilitate transfers between blockchains. If a blockchain connects to a Hub via IBC, it automatically gains access to all the other blockchains that are connected to it. The Cosmos Hub is a public Proof-of-Stake chain. Its staking token is called the Atom. Next, learn how to [install Gaia](./installation.md). diff --git a/docs/docs/governance/proposal-types/params-change/Auth.mdx b/docs/docs/governance/proposal-types/changes-archive/Auth.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Auth.mdx rename to docs/docs/governance/proposal-types/changes-archive/Auth.mdx diff --git a/docs/docs/governance/proposal-types/params-change/Crisis.mdx b/docs/docs/governance/proposal-types/changes-archive/Crisis.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Crisis.mdx rename to docs/docs/governance/proposal-types/changes-archive/Crisis.mdx diff --git a/docs/docs/governance/proposal-types/params-change/Distribution.mdx b/docs/docs/governance/proposal-types/changes-archive/Distribution.mdx similarity index 94% rename from docs/docs/governance/proposal-types/params-change/Distribution.mdx rename to docs/docs/governance/proposal-types/changes-archive/Distribution.mdx index 53d92d666f6..37b5ade99e1 100644 --- a/docs/docs/governance/proposal-types/params-change/Distribution.mdx +++ b/docs/docs/governance/proposal-types/changes-archive/Distribution.mdx @@ -42,7 +42,7 @@ Increasing the value of the `community_tax` parameter will increase the rate tha **The fixed base reward bonus for the validator proposing a block, as a proportion of transaction fees.** -All validators in the active set share the rewards for producing a block equally, except for the proposer of a valid block: that validator receives a bonus of `0.010000000000000000` (1%) more in transaction fees. The proposer must include a minimum of 2/3 of precommit signatures from the other validators in the active set in order for the block to be valid and to receive the `base_proposer_reward` bonus. All in Bits has published more in-depth information [here](https://hub.cosmos.network/main/validators/validator-faq.html#how-are-fees-distributed). +All validators in the active set share the rewards for producing a block equally, except for the proposer of a valid block: that validator receives a bonus of `0.010000000000000000` (1%) more in transaction fees. The proposer must include a minimum of 2/3 of precommit signatures from the other validators in the active set in order for the block to be valid and to receive the `base_proposer_reward` bonus. All in Bits has published more in-depth information [here](https://hub.cosmos.network/validators/validator-faq#how-are-fees-distributed). - on-chain value: - `cosmoshub-4` default: `0.010000000000000000` @@ -64,7 +64,7 @@ The Cosmos Hub transaction fee volume is proportionally very low in value compar **The maximum additional reward bonus for the validator proposing a block, as a proportion of transaction fees.** -All validators in the active set share the rewards for producing a block equally, except for the proposer of a valid block. If that validator includes more than a minimum of 2/3 of precommit signatures from the other validators in the active set, they are eligible to receive the `bonus_proposer_reward` of up to 4% (`0.040000000000000000`), beyond the 1% `base_proposer_reward`. The bonus proposer reward amount that a validator receives depends upon how many precommit signatures are included in the proposed block (additional to the requisite 2/3). All in Bits has published more in-depth information [here](https://hub.cosmos.network/main/validators/validator-faq.html#how-are-fees-distributed). +All validators in the active set share the rewards for producing a block equally, except for the proposer of a valid block. If that validator includes more than a minimum of 2/3 of precommit signatures from the other validators in the active set, they are eligible to receive the `bonus_proposer_reward` of up to 4% (`0.040000000000000000`), beyond the 1% `base_proposer_reward`. The bonus proposer reward amount that a validator receives depends upon how many precommit signatures are included in the proposed block (additional to the requisite 2/3). All in Bits has published more in-depth information [here](../../../validators/validator-faq#how-are-fees-distributed). - on-chain value: - `cosmoshub-4` default: `0.040000000000000000` @@ -84,7 +84,7 @@ The Cosmos Hub transaction fee volume is proportionally very low in value compar #### Example -**Note** that "reserve pool" refers to the community pool. In this example from the [All in Bits website](https://hub.cosmos.network/main/validators/validator-faq.html#how-are-fees-distributed), there are 10 validators with equal stake. Each of them applies a 1% commission rate and has 20% of self-delegated Atoms. Now comes a successful block that collects a total of 1025.51020408 Atoms in fees. +**Note** that "reserve pool" refers to the community pool. In this example from the [All in Bits website](../../../validators/validator-faq#how-are-fees-distributed), there are 10 validators with equal stake. Each of them applies a 1% commission rate and has 20% of self-delegated Atoms. Now comes a successful block that collects a total of 1025.51020408 Atoms in fees. First, a 2% tax is applied. The corresponding Atoms go to the reserve pool (aka community pool). Reserve pool's funds can be allocated through governance to fund bounties and upgrades. diff --git a/docs/docs/governance/proposal-types/params-change/Governance.mdx b/docs/docs/governance/proposal-types/changes-archive/Governance.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Governance.mdx rename to docs/docs/governance/proposal-types/changes-archive/Governance.mdx diff --git a/docs/docs/governance/proposal-types/params-change/Mint.mdx b/docs/docs/governance/proposal-types/changes-archive/Mint.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Mint.mdx rename to docs/docs/governance/proposal-types/changes-archive/Mint.mdx diff --git a/docs/docs/governance/proposal-types/params-change/Slashing.mdx b/docs/docs/governance/proposal-types/changes-archive/Slashing.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Slashing.mdx rename to docs/docs/governance/proposal-types/changes-archive/Slashing.mdx diff --git a/docs/docs/governance/proposal-types/params-change/Staking.mdx b/docs/docs/governance/proposal-types/changes-archive/Staking.mdx similarity index 100% rename from docs/docs/governance/proposal-types/params-change/Staking.mdx rename to docs/docs/governance/proposal-types/changes-archive/Staking.mdx diff --git a/docs/docs/governance/proposal-types/params-change/param-index.mdx b/docs/docs/governance/proposal-types/changes-archive/param-index.mdx similarity index 98% rename from docs/docs/governance/proposal-types/params-change/param-index.mdx rename to docs/docs/governance/proposal-types/changes-archive/param-index.mdx index 73af67e8208..2158e310b6e 100644 --- a/docs/docs/governance/proposal-types/params-change/param-index.mdx +++ b/docs/docs/governance/proposal-types/changes-archive/param-index.mdx @@ -1,6 +1,6 @@ --- title: Legacy subspace parameters -order: 2 +order: 1 --- import { KeyValueTable } from "@site/src/js/KeyValueTable"; diff --git a/docs/docs/governance/proposal-types/community-pool-spend.md b/docs/docs/governance/proposal-types/community-pool-spend.md index 51f306805f3..046c3ae397c 100644 --- a/docs/docs/governance/proposal-types/community-pool-spend.md +++ b/docs/docs/governance/proposal-types/community-pool-spend.md @@ -26,7 +26,7 @@ The current paramater `Community Tax` parameter of 2% may be modified with a gov You may directly query the Cosmos Hub 4 for the balance of the Community Pool: -```gaiad q distribution community-pool --chain-id cosmoshub-4 --node https://rpc.cosmos.network:443``` +```gaiad q distribution community-pool --chain-id cosmoshub-4 --node ``` Alternatively, popular Cosmos explorers such as [Big Dipper](https://cosmos.bigdipper.live) and [Mintscan](https://www.mintscan.io/cosmos) display the ongoing Community Pool balance. diff --git a/docs/docs/governance/proposal-types/param-change.md b/docs/docs/governance/proposal-types/param-change.md index 333b38a5779..12c4a8c52cc 100644 --- a/docs/docs/governance/proposal-types/param-change.md +++ b/docs/docs/governance/proposal-types/param-change.md @@ -1,32 +1,36 @@ --- -title: Parameter Change +title: Parameter Changes order: 4 --- -This Cosmos Hub educational documentation aims to outline the Hub's parameters, describe their functions, and describe the potential implications of modifying each parameter. This documentation also aims to provide guidelines for creating and assessing parameter-change proposals. +This documentation aims to provide guidelines for creating and assessing parameter-change proposals. Drafting and submitting a parameter-change governance proposal involves two kinds of risk: losing proposal deposit amounts and the potential to alter the function of the Cosmos Hub network in an undesirable way. ## What parameters can be changed? -The complete parameters of the Cosmos Hub are split up into different modules, each of which has its own set of parameters. Any of them can be updated with a Param Change Proposal. If you are technically inclined, this is the full [list of modules](https://github.com/cosmos/cosmos-sdk/tree/master/x) in the Cosmos SDK. The Cosmos Hub is built using the Cosmos SDK, but not all available modules are in use on the Hub. +The complete parameters of the Cosmos Hub are split up into different modules, each of which has its own set of parameters. Most parameters can be updated by submitting a governance proposal. -There are currently 8 modules active in the Cosmos Hub with parameters that may be altered via governance proposal. New modules may be introduced in the future. +List of modules whose parameters can be changed via governance: +* x/auth +* x/bank +* x/distribution +* x/evidence +* x/feegrant +* x/gov +* x/mint +* x/slashing +* x/staking +* ibc-go/transfer +* interchain-security/provider -1. [auth](/governance/proposal-types/params-change/Auth.mdx) - Authentication of accounts and transactions -2. [gov](/governance/proposal-types/params-change/Governance.mdx) - On-chain governance proposals and voting -3. [staking](/governance/proposal-types/params-change/Staking.mdx) - Proof-of-stake layer -4. [slashing](/governance/proposal-types/params-change/Slashing.mdx) - Validator punishment mechanisms -5. [distribution](/governance/proposal-types/params-change/Distribution.mdx) - Fee distribution and staking token provision distribution -6. [crisis](/governance/proposal-types/params-change/Crisis.mdx) - Halting the blockchain under certain circumstances (ie. if an invariant is broken) -7. [mint](/governance/proposal-types/params-change/Mint.mdx) - Creation of new units of staking token - +Each cosmos-sdk module uses `MsgUpdateParams` for providing parameter changes. You can learn more about it in the cosmos-sdk documentation of each module (e.g. https://docs.cosmos.network/v0.47/build/modules/staking#msgupdateparams) ## What are the current parameter values? -There are ways to query the current settings for each module's parameter(s). Some can be queried with the command line program [`gaiad`](../../getting-started/installation.md). +There are ways to query the current settings for each module's parameter(s). Some can be queried with the command line program [`gaiad`](../../getting-started/installation). -You can begin by using the command `gaia q [module] -h` to get help about the subcommands for the module you want to query. For example, `gaiad q staking params --chain-id --node ` returns the settings of relevant parameters: +You can begin by using the command `gaiad q [module] -h` to get help about the subcommands for the module you want to query. For example, `gaiad q staking params` returns the settings of relevant parameters: ```sh bond_denom: uatom @@ -60,8 +64,8 @@ This documentation was originally created by Gavin Birch ([Figment Networks](htt **Special thanks** to the following for providing credible information: - Aleks (All in Bits; Fission Labs) for answering countless questions about these parameters -- Alessio (All in Bits) for explaining how [`SigVerifyCostED25519`](https://hub.cosmos.network/main/governance/proposal-types/params-change/Auth.html#4-sigverifycosted25519) & [`SigVerifyCostSecp256k1`](https://hub.cosmos.network/main/governance/proposal-types/params-change/Auth.html#5-sigverifycostsecp256k1) work, and detailed answers to my many questions -- Vidor for volunteering to explain [`ConstantFee`](https://hub.cosmos.network/main/governance/proposal-types/params-change/Crisis.html#1-constantfee) and answering my many questions in detail -- Hyung (B-Harvest) for volunteering how [`InflationRateChange`](https://hub.cosmos.network/main/governance/proposal-types/params-change/Mint.html#2-inflationratechange) works +- Alessio (All in Bits) for explaining how [`SigVerifyCostED25519`](./changes-archive/Auth.mdx#sig_verify_cost_ed25519) & [`SigVerifyCostSecp256k1`](./changes-archive/Auth.mdx#sig_verify_cost_secp256k1) work, and detailed answers to my many questions +- Vidor for volunteering to explain [`ConstantFee`](./changes-archive//Crisis.mdx#constantfee) and answering my many questions in detail +- Hyung (B-Harvest) for volunteering how [`InflationRateChange`](./changes-archive/Mint.mdx#inflation_rate_change) works - Joe (Chorus One) for explaining the security details involved with using full nodes for transactions -- Sunny (All in Bits; Sikka) for volunteering an explanation of the purpose of [`withdrawaddrenabled`](https://hub.cosmos.network/main/governance/proposal-types/params-change/Distribution.html#4-withdrawaddrenabled) +- Sunny (All in Bits; Sikka) for volunteering an explanation of the purpose of [`withdrawaddrenabled`](./changes-archive/Distribution.mdx#withdrawaddrenabled) diff --git a/docs/docs/governance/proposals/2020-10-blocks-per-year/README.md b/docs/docs/governance/proposals/2020-10-blocks-per-year/README.md deleted file mode 100644 index 7fa88fc7064..00000000000 --- a/docs/docs/governance/proposals/2020-10-blocks-per-year/README.md +++ /dev/null @@ -1,73 +0,0 @@ ---- -title: Cosmos Hub Inflation variable modification - Blocks Per Year ---- - - - -**Quick Summary of issue** - -There are 6 main variables that control the maximum, minimum, & change of the -atom inflation rate for the cosmos hub. Description of these variables can be -found under the [mint module in the parameters -wiki](https://github.com/cosmos/governance/blob/master/params-change/Mint.md). - -In this proposal we will be looking at adjusting the blocks per year parameter. - -Currently the variable named “blocks per year” is set at 4,855,015. This works -out to one block every 6.5 seconds roughly, which as many Atom holders know, is -not a very good approximation. This leads to the stated inflation rate of the -cosmos hub to not match reality. - -**How to fix the issues** - -The goal is to select a value that is as close as possible to the future block -throughput for the cosmos hub. To do that I will look at current (past couple -days) and historical time frames to try and get as close of an approximation as -possible. - -**Past Blocks per Year Data** - -Using Big Dipper, CosmosScan, or any one of the popular cosmos hub explorers, -the time stamp for each block can be found. The typical cosmos hub block comes -in between 7-8 seconds, with the majority being closer to 7. If you look over -the past day (written on 10/14/2020) you can see an average block time coming in -around 7.29 seconds. Looking on an hourly & minute level, 7.25-7.3 seconds per -block can be seen fairly consistently. Big Dipper has also conveniently provided -the all time (for cosmos hub-3) block time data, which is coming in around 7.18 -second. Considering the slight discrepancy, I figured shooting right in the -middle would be an appropriate starting point, which could later be adjusted for -finer accuracy if need be. Now to find how many seconds are in a year, which -equals 365.25 (days / year) X 24 (Hours / Day) x 60 (Minutes / Hour) X 60 -(Seconds / minute) = 31.5576 million seconds per year. A quick google search can -confirm the math. So finally, taking 31.5576 Million / 7.24 we get a value of -4.358 Million blocks per year, which can be rounded up to **4.36 Million blocks -per year**. - -**Possible Risks / Benefits** - -I will split this up into two sections, doing nothing & doing the proposed -changes. - -1a) Doing nothing Risks / Benefits: There are no structural risks per se doing -nothing, but the stated inflation rate of the hub will continue to not match -reality. There are very little benefits of doing nothing; besides the fact its -working just fine now as long as you don’t care how close stated inflation is vs -real inflation. - -1b) Changing to recommended value Risks / Benefits: Again, I don’t think there -are structural / game theory risks to making the blocks per year more closely -match reality. On the other hand, changing this variable to more closely match -reality is beneficial to all participants when doing any sort of economic -calculus. Currently the true inflation rate is actually lower than the stated -rate by a factor of 10ish % (4.36 Mil blocks per year / 4.85 Mil blocks per -year). So while the target rate is 7%, the actual current rate is more like -~6.29%. - -**Conclusion** - -I know there isn’t a right answer for blocks per year. I fully expect this value -to be fine tuned over the coming years / decades. This seems like a very good -starting place and a greatly beneficial change before we enter the post star -gate world ☺ - - diff --git a/docs/docs/governance/proposals/2020-10-blocks-per-year/proposal.json b/docs/docs/governance/proposals/2020-10-blocks-per-year/proposal.json deleted file mode 100644 index decee79af6a..00000000000 --- a/docs/docs/governance/proposals/2020-10-blocks-per-year/proposal.json +++ /dev/null @@ -1,17 +0,0 @@ -{ - "title": "Adjust Blocks Per Year to 4.35M", - "description": "While the current inflation rate is set at 7%, the effective inflation rate is more like ~6.29%. This is because blocks have slowed down somewhat from ~6.5s to ~7.24s per block, and thus the current blocks per year value of 4855015 is too high. Here we propose to adjust the blocks per year value from 4855015 to 4360000 to bring it in line with current block times, which should realign the effective inflation rate. More details were drafted on and are available on ", - "changes": [ - { - "subspace": "mint", - "key":"BlocksPerYear", - "value": "4360000" - } - ], - "deposit": [ - { - "denom": "uatom", - "amount": "1000000" - } - ] -} diff --git a/docs/docs/governance/proposals/2020-11-inflation-rate-change/README.md b/docs/docs/governance/proposals/2020-11-inflation-rate-change/README.md deleted file mode 100644 index 562d29e4bfa..00000000000 --- a/docs/docs/governance/proposals/2020-11-inflation-rate-change/README.md +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: Cosmos Hub Inflation variable modification - Inflation Rate Change ---- - - - -**Quick Summary of issue** - -There are 6 main variables that control the maximum, minimum, & change of the atom inflation rate for the cosmos hub. These variables can be found inside the mint module via the attached hyperlink: [https://github.com/gavinly/CosmosParametersWiki/blob/master/Mint.md](https://github.com/gavinly/CosmosParametersWiki/blob/master/Mint.md) - -In this proposal we will be looking at adjusting the inflation rate change variable. - -- When the cosmos hub inflation dynamics were originally designed, the goal was for the hub to go from the minimum rate (7%) to the maximum rate (20%) in roughly one year after a shock had unbond occurred. Thus, for the variable “inflation rate change” a value of .13 was chosen. Unfortunately, in practice the variable didn’t work as intended due to the fact the change in the inflation rate for the hub is proportional to the Target Bonded / current bonded ratio. - - -**How to select “inflation rate change” AKA Maximum Slope of the inflation curve** - -The purpose of changing the network's inflation rate is to protect it from unbonding shocks that can threaten to compromise the security of the network. When the bonded ratio gets below the goal bonded ratio (currently at 66% on the hub) the inflation rate & effective yield of staked atoms goes up in order to incentivize holders to bond new ATOMs with a view to securing the network. Inversely, if we regain a desired amount of staked tokens, the yield will drop and thusly decrease effective yields for all delegators. Ideally the inflation rate starts changing fast, optimizing network security over monetary hardness. To figure out what an appropriate selection for the cosmos hub would be, I created excel sheets to run through all the different scenarios to find what value made the inflation rate react in an optimal manner. **I came to the conclusion that 1 (AKA 100% per year is the maximum slope of the inflation curve) gave the most ideal characteristics, with the added benefit of simplifying the equation**. I’ll give some examples on how it would react. Since unbonding is what we are protecting against, I will look at flash unbonds while the inflation rate is at the floor due to that being the #1 time of vulnerability. - -**Scenarios of Shock Unbonds** -#1. Cosmos hub Bonded ratio flash crashes to 60%, which is not bad, but still 10% below the target. With our current variable of .13, it would take approx. 9.6 years to make it to the ceiling rate of 20%. On the other hand, if this variable was 1, the hub would reach it ceiling 17.2 months after the unbond shock (assuming bonded % stays at 60% the entire time for simplicity). - - -#2 Cosmos hub Bonded ratio flash crashes to 50%, starting to get a little scary, but only 25% below the 66% target. With our current variable of .13, it would take aprox. 4 years to make it to the ceiling rate of 20%. On the other hand, if this variable was 1, the hub would reach it ceiling 6.4 months after the unbond. - -#3 Cosmos hub Bonded ratio flash crashes to 35%, NOT GOOD!!!! We need to get more atoms staked ASAP! With our current variable of .13, it would take aprox 25 months to reach the ceiling rate of 20%. On the other hand, if this variable was 1, the hub would reach its ceiling 3.3 months after the unbond and the inflation rate would be increasing at a rate of 3.91% per month. - -All of the data above, graphs, and much more can be found at [https://docs.google.com/spreadsheets/d/1ZJWNzkNB7HUG3fsom9UO8bXODao8cJfFHkgdZ12IOnA/edit#gid=0](https://docs.google.com/spreadsheets/d/1ZJWNzkNB7HUG3fsom9UO8bXODao8cJfFHkgdZ12IOnA/edit#gid=0) - -**Possible Risks / Benefits** - -I will split this up into two sections, doing nothing & doing the proposed changes. - -Inflation rate Change (Max Slope of inflation curve) - -1a) Doing nothing Risks / Benefits: In this case, I do believe there are risks to do nothing. Currently the inflation rate of the hub is not very reactive to unbond shocks (as seen above). This can lead to network security risks if an economic actor with bad intent wanted to try and destabilize the hub. On the other hand, changing any variable within a system can cause unwanted consequences. There is no way to get rid of this risk entirely, luckily the inflation mechanics are fairly simple and easy to model with excel spreadsheets. Additionally, none of these changes will affect the consensus mechanism, they will just impact the minting of new atoms. - -1b) Changing rate to 1 Risks / Benefits: As stated above, there are always risks to changing variables within complex systems. Changing this variable will undoubtedly greatly increase the reactivity of the hub to unbonding shocks. Overall, this seems very beneficial due to the extremely slow reaction time of the hub currently. Also, it brings the hub closer to the original goal of 1 year from the min to the max in a unbonding shock scenario. Due to the fact the inflation curve slope is proportional to the goal vs current bonded ratio, it isn’t possible to hit the original goal directly, but this brings it much closer to reality. - -**Conclusion** - -I know there isn’t a right answer for maximum slope. I fully expect this to be fine-tuned over the coming years / decades. Future proposals may adjust this number by a factor of (.5 – 2+) but this gets us in the right ball park just in time for Stargate. ☺ - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2020-11-inflation-rate-change/proposal.json b/docs/docs/governance/proposals/2020-11-inflation-rate-change/proposal.json deleted file mode 100644 index 133e4ee623b..00000000000 --- a/docs/docs/governance/proposals/2020-11-inflation-rate-change/proposal.json +++ /dev/null @@ -1,17 +0,0 @@ -{ - "title": "Adjust InflationRateChange to 1", - "description": "When the number of bonded atoms falls below the target ratio (ie currently 67% of total supply), the inflation rate is increased to incentivize more bonding. The inflation changes at a rate parameterized by the InflationRateChange, currently set at 0.13. It seems this parameter is mis-specified, since this generally leads to slow response to shock unbonding - eg. if the bonded atoms fall to only 34% of the supply, will take 2 years to get from the minimum 7% inflation to the maximum 20% rate. Here we propose to increase this parameter to 1, which enables incentives to adapt much more quickly to shock unbonds. More details were drafted on and are available on ", - "changes": [ - { - "subspace": "mint", - "key":"InflationRateChange", - "value": "1" - } - ], - "deposit": [ - { - "denom": "uatom", - "amount": "1000000" - } - ] -} diff --git a/docs/docs/governance/proposals/2021-01-atom2021_marketing/README.md b/docs/docs/governance/proposals/2021-01-atom2021_marketing/README.md deleted file mode 100644 index 8b4df9b41d7..00000000000 --- a/docs/docs/governance/proposals/2021-01-atom2021_marketing/README.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Proposal 34, Luna Mission - Funding $ATOM ---- - - - -**ABSTRACT:** - -This proposal is the by-product of an ambitious community driven initiative. Its purpose is to orchestrate and coordinate an effort to increase awareness on the value proposition of $ATOM and the Cøsmos Hub, informing communities, individuals, entities about the dynamics of $ATOM in the light of the upcoming Stargate upgrade. We aim to achieve this through undertaking a marketing campaign contracted to AiB. We propose that the community pool allocate **129,208 $ATOM** to this initiative with immediate effect upon the proposal’s passing. The funds will be used towards the following actions: - -**i.** One set of actions for incentivising, educating thought leaders so as to engage through media (Twitter, YouTube) for a period of 3 months and educate their audiences about $ATOM without any unnecessary hyperboles, something that would go against the values and ethos of our project; - -**ii.** One set of actions for engaging the blockchain and crypto communities for 3 months via 3 monthly meme contests whose intention is to make $ATOM going viral on Twitter. - -**iii.** One set of actions for a 3 month header banner and/or homepage banner advertising campaigns on 4 platforms with high and/or relevant traffic to the Cosmos Hub such as CMC, Coingecko, Blockfolio and Staking Rewards platforms, whichever of them have available spots. - -**iv.** A maximum of 10% from the budget will be used to engage a high profile PR Agency to help with the Media and Marketing efforts. AiB and/or committee members will request and share offers from different PR Agencies and the offer containing the best marketing plan will be selected by the committee members through vote. - -AiB will maintain the relation with the PR Agency and will report to the committee on the status of deliverables. - -We have requested and shall receive the assistance of AiB (Tendermint). We believe AiB (Tendermint) is one of those entities that have demonstrated an unparalleled dedication to the Cosmos Hub. - -A multi-sig committee of 5 community members will lead coordination of the effort, and approve the above specified actions and forward funds to AiB upon completion of objectives. - -Unspent funds will be refunded to the community pool by the committee. - -**MultiSig Address: cosmos16plylpsgxechajltx9yeseqexzdzut9g8vla4k** - -**FULL TEXT OF DRAFT PROPOSAL** - -**Preamble** - -***"We reject siloed and centralised hegemonies; we believe in the promise of Cosmos for a truly interoperable and decentralised future for governance and finance; we provide the building blocks for the future of finance and beyond.”*** - -We, the community of the Cosmos Hub ($ATOM) have patiently been awaiting the time when IBC, the protocol that will signal the second era of the Blockchain Revolution goes live. - -We understand that it had been of the utmost importance to opt for and pursue excellence over marketing or shilling a (nonetheless amazing) project that was not yet finalised. This, in our view, aligned with the views and ethos of the founding fathers of this great project although we firmly believe that getting the merits of this project known is of equal importance. - -This is for a reason: we have been students and true believers in the value proposition and fundamentals of this amazing technology since we laid our eyes on it and learnt about its merits/properties. - -To us, Cosmos Hub is providing the building blocks for the future of DLT and beyond it. We believe that its impact on the world can be enormous. For us, it is hard to resist Cosmos once you get involved with the idea. But like all great ideas it has to be disseminated. - -Thus, we have long come upon the realisation that it has not received the attention it deserves. We also realise we build in a space where reason and real values are not a given or guarantee for success. There have been many examples in the past, not just in this space where a great idea or execution thereof was not enough for a venture’s success. -We have decided that it is high time we coordinated, orchestrated efforts so that we see $ATOM becoming known to this space and beyond, We are convinced that people who see the potential, inherent value and ethos of this project will not be able to unsee and that they will be converted to believers and evangelists like ourselves. - -We need to have the support of all: community members, delegators, validators and teams that have tirelessly worked to ensure the flawless, successful completion of the Cosmos stack and vision of its roadmap. - -We will need more than their vocal support. We will need their vote. We will need their subsequent support for this initiative. We all need to do nothing more than spread the knowledge. Disseminate this great idea. - -We also need AiB (Tendermint)'s help to execute on this ambitious effort. - -Our proposal is requesting from the entire cosmos family to grant access to a portion of the community pool and allow a community spend of 129,208 $ATOM for marketing contracts over a course of 3 months starting immediately upon its passing. - -We are convinced that, by this community spend, we will increase awareness across blockchain space and get the $ATOM spaceship ready for its intergalactic journey that few - but us - have foreseen. This is not about shilling a project with no fundamentals, this is about making the best project out there known across blockchain space and beyond. - -We also think that this initiative is not only helping the Cosmos Hub and ATOM, ultimately it is a great initiative with benefits for the massive and ever expanding galaxy of the Cosmos ecosystem. Yet we are aligned with the ATOM2021 initiative and understand that for us - $ATOM holders - the utility of $ATOM should become known and strengthened via similar initiatives. - -Ultimately we deem imperative that this initiative coincides with the Stargate upgrade. - -**4 Types of Promotional Activities to be funded with 129,208 $ATOM:** - -In order to achieve the goal of strengthening the public perception about the ATOM’s utility and understanding of communities about the value proposition of the Hub we have 4 main campaigns in mind for which we request your approval. The campaigns are detailed below: - -**i.** One set of actions for incentivising, educating thought leaders so as to engage through media (Twitter, YouTube) for a period of 3 months and educate their audiences about $ATOM without any unnecessary hyperboles, something that would go against the values and ethos of our project. - -**ii.** One set of actions for engaging the blockchain and crypto communities for 3 months via 3 monthly meme contests whose intention is to make $ATOM going viral on Twitter. - -**iii.** One set of actions for a 3 month header banner and/or homepage banner advertising campaigns on 4 platforms with high and/or relevant traffic to the Cosmos Hub such as CMC, Coingecko, Blockfolio and Staking Rewards platforms, whichever of them have available spots. - -**iv.** A maximum of 10% from the budget will be used to engage a high profile PR Agency to help with the Media and Marketing efforts. AiB and/or committee members will request and share offers from different PR Agencies and the offer containing the best marketing plan will be selected by the committee members through vote. -AiB will maintain the relation with the PR Agency and will report to the committee on the status of deliverables. - -**Scope of Campaigns:** - -The campaigns will be $ATOM related and should be aligned with the ATOM2021 initiative, increase awareness about the Cosmos Hub, the value proposition of $ATOM, the dynamics of IBC in relation to $ATOM without neglecting to point on the truly decentralised, sovereign, scalable, sustainable properties inherent in the project’s architecture and ethos as well as its non-competitive character to other chains within the ecosystem. -Since we are aware of the superiority of the project over any similar efforts on interoperability, honest and informed comparisons by thought leaders in the space are anticipated and will be coordinated during the course of this undertaking. - -**Release of funds:** - -Funds will be released to a multi-sig committee which in turn may - depending on each initiative and based on a majority multisignature approval - release the funds to: 1) Tendermint (AiB) that will act as a liaison between Cosmos Hub community and third parties and distribute the payments according with the marketing proposal or where appropriate, 2) directly to the entities or individuals ( e.g. contest winners or various contributors) - - -**Funds’ Distribution:** - -The distribution of funds will be administered by 5 community members that have been selected via the governance working group. At least 3 will have to approve each spend for it to be released to AiB or any third party, according with the marketing proposal. - -@johnniecosmos, @JoeDirtay, @jackzampolin (Jack Zampolin, Pylon Validator), @immasssi (SG-1 Validator), @zakimanian (Zaki Manian, Iqlusion Validator). - -Every spend action related to this proposal has to be approved via multi-sig. At least 3/5 signatures are required to confirm a spend of the allocated marketing funds. - -For administrative efforts, drafting the proposal and executing the marketing efforts, the 5 administrators will receive 100 ATOMs each for their time & efforts over the coming 3 months in helping to properly execute the above mentioned strategy. - -**MultiSig Address: cosmos16plylpsgxechajltx9yeseqexzdzut9g8vla4k** - -**Refund of Unspent Funds to the Pool:** - -It is expected that amounts requested and allocated for each campaign will be depleted and spent. In the event this does not happen within 3 months of the passing of the proposal, this amount will have to be refunded by either AiB or the mutli-sig committee (whomever is in custody of the funds) back to the community pool. - -**Expectations from the rest of entities involved in the Hub:** - -We expect that our initiative will stand as a beacon for the rest of the teams/entities/individuals involved in the development of the Cosmos Hub in respect to pushing the project forward. - -Educational material, articles on mainstream media, podcasts, interviews, social media campaigns, active promotion to e.g. the end of a Paypal listing, only form part of what we deem as an optimal and thorough and long-term strategy for establishing the Cosmos Hub ($ATOM) as the true game changer in people’s minds within this space. Since our resources are limited and the purpose here is not to deplete the Community pool, we expect the rest of the main teams involved in the development of the Hub or even teams earning value from their operations on the Cosmos hub and $ATOM to undertake efforts similar (at least in passion) to ours and support or supplement our efforts. Thus, we aim to motivate others by this limited in resources initiative. - -**AiB’s General Obligations to the Community:** - -Specific work tasks like the banner campaign & the thought leader campaign are expected to be covered by AIB. This can be done right away even before the proposal is passed to enable a faster execution of the proposal. Any tasks which are agreed upon and that are signed off by the administrators will then be commissioned to AIB upon delivery. Administrators expect a fully transparent report every 2 weeks showing the state of the tasks and additional information that verifies the proper execution of the community tasks (Receipts & documentation). - -**Closing Remarks:** - -Ultimately for us, the Community, Cosmos Hub ($ATOM) signals the second era of the so-called Blockchain Revolution. We can all be the messengers, but we need the message to be delivered sooner than later. Empower us with the necessary funding tools so that we disseminate and deliver the message across all corners of the space. For, beyond awesome code, we see an equally awesome community ready to undertake and support this ambitious initiative. We do not see this as a phoney attempt to shill an empty promise. We see this as an opportunity to inform, educate and create a larger follower base around the most important project in this space to date. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-atom2021_marketing/proposal.json b/docs/docs/governance/proposals/2021-01-atom2021_marketing/proposal.json deleted file mode 100644 index 09a17886f68..00000000000 --- a/docs/docs/governance/proposals/2021-01-atom2021_marketing/proposal.json +++ /dev/null @@ -1,17 +0,0 @@ -{ - "title": "Luna Mission - Funding $ATOM", - "description": "The Cosmos Hub (ATOM) community is requesting a community pool spend amount of 129,208 ATOM in order to implement a comprehensive ATOM marketing plan that will be executed in collaboration with AiB (Tendermint). The marketing efforts will be initiated immediately upon passing of proposal #34.\n\n The distribution of funds will be administered by 5 community members, that have been carefully selected by the community via the Cosmos governance working group to administer the marketing plan and release funds to either AiB that will act as a liaison between Cosmos Hub community and third parties or directly to parties that will be in charge of executing the marketing plan based on a majority multisignature approval. At least 3 members will have to approve each milestone-spend for it to be released to AiB based on the expected proposal scope &completion. \n\n More details can be found in the long form proposal here: https://cloudflare-ipfs.com/ipfs/QmWAxtxf7fUprPVWx1jWyxSKjBNqkcbA3FG6hRps7QTu3k and https://github.com/cosmos/governance/pull/10 and https://forum.cosmos.network/t/draft-governance-proposal-for-a-community-pool-spend-proposal-33-luna-mission-funding-atom/4244/15 \n\n The multisig administration includes: \n @johnniecosmos, @JoeDirtay, @jackzampolin (Jack Zampolin, Pylon Validator), @immasssi (SG-1 Validator), @zakimanian (Zaki Manian, Iqlusion Validator).", - "recipient": "cosmos16plylpsgxechajltx9yeseqexzdzut9g8vla4k", - "amount": [ - { - "denom": "uatom", - "amount": "129208000000" - } - ], - "deposit": [ - { - "denom": "uatom", - "amount": "12000000" - } - ] -} diff --git a/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/README.md b/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/README.md deleted file mode 100644 index bc110a1229b..00000000000 --- a/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/README.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Delay of Hub Stargate Upgrade ---- - - -The Stargate team is recommending that the Cosmos Hub reschedule the next upgrade to a new commit hash. The new commit hash is expected to be available on Tuesday Jan 26th with a new upgrade proposal immediately after. - -This governance proposal will signal that [proposal 35](https://www.mintscan.io/cosmos/proposals/35) will not be executed. The Hub governance will vote on the forthcoming proposal aiming for a final upgrade. The earliest target date would be February 11th. Given that Lunar New Year is on Feb 12th. The next best date is Feb 18th 06:00UTC. - -We are recommending the delay for the following reasons. - -* Bugs have been identified in the Proposal 29 implementation. They are resolved in this pull request[Additional review of prop 29 and migration testing by zmanian · Pull Request #559 · cosmos/gaia · GitHub](https://github.com/cosmos/gaia/pull/559) -* A balance validation regression was identified during Prop 29 code review. [x/bank: balance and metadata validation by fedekunze · Pull Request #8417 · cosmos/cosmos-sdk · GitHub](https://github.com/cosmos/cosmos-sdk/pull/8417) -* The IBC Go To Market Working Group has [identified Ledger hardware wallet](https://github.com/cosmos/cosmos-sdk/issues/8266) support as a necessary feature for the initial launch of IBC on the Hub. We have an opportunity to provide this support in this upgrade. The SDK believes this can be quickly remediated in the time available with merged PRs on Monday. -* The number of Stargate related support requests from integrators has increased significantly since the governance proposal went live but some teams have already announced a period of reduced $ATOM support while they upgrade like . The additional time should minimize the disruption for $ATOM holders. Thank so much to the $IRIS team who is fielding a similar request volume among our non-English community. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/proposal.json b/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/proposal.json deleted file mode 100644 index afd47d0297d..00000000000 --- a/docs/docs/governance/proposals/2021-01-delay-stargate-upgrade/proposal.json +++ /dev/null @@ -1,8 +0,0 @@ - -{ - "title":"Delay of Hub Stargate Upgrade for approximately 2 weeks", - "description":"The Stargate team is recommending that the Cosmos Hub reschedule the next upgrade to a new commit hash. The new commit hash is expected to be available on Tuesday Jan 26th with a new upgrade proposal immediately after.\n\nThis governance proposal will signal that [proposal 35](https://www.mintscan.io/cosmos/proposals/35) will not be executed. The Hub governance will vote on the forthcoming proposal aiming for a final upgrade. The earliest target date would be February 11th. Given that Lunar New Year is on Feb 12th. The next best date is Feb 18th 06:00UTC.\n\nWe are recommending the delay for the following reasons.\n\n* Bugs have been identified in the Proposal 29 implementation. They are resolved in this pull request[Additional review of prop 29 and migration testing by zmanian · Pull Request #559 · cosmos/gaia · GitHub](https://github.com/cosmos/gaia/pull/559)\n* A balance validation regression was identified during Prop 29 code review. [x/bank: balance and metadata validation by fedekunze · Pull Request #8417 · cosmos/cosmos-sdk · GitHub](https://github.com/cosmos/cosmos-sdk/pull/8417)\n* The IBC Go To Market Working Group has [identified Ledger hardware wallet](https://github.com/cosmos/cosmos-sdk/issues/8266) support as a necessary feature for the initial launch of IBC on the Hub. We have an opportunity to provide this support in this upgrade. The SDK believes this can be quickly remediated in the time available with merged PRs on Monday.\n* The number of Stargate related support requests from integrators has increased significantly since the governance proposal went live but some teams have already announced a period of reduced $ATOM support while they upgrade like . The additional time should minimize the disruption for $ATOM holders. Thank so much to the $IRIS team whom is fielding a similar request volume among our non-English community.", - "deposit":"256000000uatom", - "type":"Text" - -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/README.md b/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/README.md deleted file mode 100644 index 56bf8412246..00000000000 --- a/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/README.md +++ /dev/null @@ -1,155 +0,0 @@ ---- -title: Stargate Upgrade- Second time is a charm ---- - - -![Stargate Upgrade banner graphic](https://siasky.net/bADrO0dW2KJC0ZS1uie389nmV6MTroRqTNaeFPuTtR7qow) - -## by Iqlusion - -Jan 28, 2021 - -## Key Results - ------------- -If passed, this governance proposal would commit the Cosmos Hub to halting the `cosmoshub-3` at 06:00 UTC on Feb 18th exporting the state and starting `cosmoshub-4` based on gaia 4.0.0 - -## Context - ------------- - -In [Proposal 27](https://ipfs.io/ipfs/Qmbo3fF54tX3JdoHZNVLcSBrdkXLie56Vh2u29wLfs4PnW), Iqlusion proposed a comprehensive process to translate the unprecented surface area of this upgrade. We called this process Stargate. - -Iqlusion is pleased to report that the Stargate Process has been successfully executed. We believe the ecosystem is ready and the Hub can safely step through the Stargate. - -After the success of the community approval of the first Stargate Upgrade proposal, we now follow-up with the second Stargate proposal for the Cosmos Hub that will outline the results of the first proposal and the process for upgrading the Hub. - -### Aborting of Proposal 35 - -Bugs were found in prior upgrade release that triggered the abort procedure that was detailed in the standard upgrade. - -* Bugs have been identified in the Proposal 29 implementation. They are resolved in this pull request[Additional review of prop 29 and migration testing by zmanian · Pull Request #559 · cosmos/gaia · GitHub](https://github.com/cosmos/gaia/pull/559) -* A balance validation regression was identified during Prop 29 code review. [x/bank: balance and metadata validation by fedekunze · Pull Request #8417 · cosmos/cosmos-sdk · GitHub](https://github.com/cosmos/cosmos-sdk/pull/8417) - -## The Stargate Plan - ------------- -The purpose of the Stargate effort was to ensure that Cosmos can fulfill the vision of an Internet of Blockchains in 2021 while mitigating the technological and organizational risks outlined in the [original Stargate Upgrade Proposal 27](https://ipfs.io/ipfs/Qmbo3fF54tX3JdoHZNVLcSBrdkXLie56Vh2u29wLfs4PnW). It was also an attempt to create a process for complex future on-chain upgrades on the Cosmos Hub. That included the following steps: - -1. Run the Stargate Testnet and use this as an integration testing target with widest possible ecosystem participation to help confirm the readiness of the release software. - -2. Engage and support critical partners during the integration process so that partners are able to actively participate in the testing process and provide insights into their success with the upgrade. - -3. Dedicate significant resources in terms of full time human resources and documentation efforts to ensure that everyone integrated into the Cosmos Hub can self-certify as Stargate-ready. - -4. Report back to the Hub on the success of the integration process. - - * We expect that the primary responsibility of the Cosmos Hub is to assess whether we have mitigated the above risks sufficiently. - - * Provide a written report of the entire Stargate effort to enable Hub governance to make an informed decision. - -5. At conclusion, we will indicate why we have confidence that an upgrade won't be disruptive to the Hub’s ecosystem. - -## Stargate Plan Results - ------------- - -### 1. Ecoystem Participation - -The results of ecosystem participation and engagement are available in our [Stargate Ecosystem Readiness Report](https://github.com/cosmosdevs/stargate/blob/master/ecosystem_readiness.md). We list on this page ecosystem partners such as Validators that provided their validator public keys as well as infrastructure partners that confirmed their integration testing the Stargate testnet tags. Validators, exchanges, and wallets have made up the most responsive of their results completing integration testing of the stargate releases. We anticpate that all actors in the ecosystem are aware and ready to respond to the new Cosmos Hub features. Integration partners have helped find regression in the legacy amino compatibility layer and those have been resolved. - -The Cosmos SDK, Tendermint Core, Tendermint Inc, and IBC teams worked tirelessly to deliver the most robust software feature set that would make up the Cosmos Stargate release. Their review of their efforts are documented in their post ["How Seven Teams Collaborated To Deliver The Biggest Software Upgrade In The Cosmos Universe"](https://blog.cosmos.network/how-seven-teams-collaborated-to-deliver-the-biggest-software-upgrade-in-the-cosmos-universe-2288f4f9afe8). - -Integration testing continued through the release of the Cosmos SDK v0.40.0-rc2 that makes up the Cosmos-hub Stargate testnet tag for a simulated upgrade of the CosmosHub-3 to CosmosHub-4. Also, the AiB team continues to deliver simulation testing of Cosmos Stargate to ensure that any possible chain bug issues can be detected and documented. - -We are confident that we have and continue to achieve increased ecosystem engagement with the Stargate testnet. - -### 2. Critical Partner Support - -We delivered critical partner support to leading ATOM exchanges. Out of the exchange support efforts, we documented the [IBC Readiness Matrix](https://github.com/cosmosdevs/stargate/blob/master/ibc_readiness_matrix.md) that outlines the levels of readiness that exchanges may select as they upgrade to Cosmos Stargate. - -We also completed and delivered a completed legacy Amino Audit, [AminoRest & You](https://github.com/cosmosdevs/stargate/blob/master/audit.md). The core finding of this audit was that changes to the underlying structs result in an interface that is close to the prior version allowing legacy queries to return valid data. - -All previous Cosmos Hub upgrades reset the block height. Our interactions with ecosystem particpants identified this as introducing significant complexity to handling this upgrade. This will be the first upgrade of the Cosmos Hub that starts the blockchain at the height + 1 of the antecedent chain. - -### 3. Documentation and Self-Certification - -Documentation was a success for the Cosmos Stargate effort. The upgrades with the most breaking changes such as legacy Amino have a complete audit with documentation on exceptions for blockchain API interfaces. - -Most exchanges and wallets have taken self-certification on directly. Our team continues to provide real-time support on multiple partner slack channels and on the Cosmos [#stargate Discord](https://discord.com/invite/cosmosnetwork) channel. - -We have conducted numerous testnets with different partners. A particularly important testnet conducted with a significant fraction of the Hub validator set was a simulated upgrade of the cosmoshub on Nov 25th,2020. This tested the full upgrade flow including the prop29 implementation and height preserving upgrade functionality. - -### Conclusion - -The governance proposal is our report back to the community on the success of the Stargate program. We have compiled detailed information for the community as a reference in the Stargate [repository](https://github.com/cosmosdevs/stargate). - -### Cosmos Stargate Integration Success - -Cosmos Stargate integration success with exchanges and wallet providers reflects the quality of the code developed by the various Cosmos teams. - -## Prop 29 - -This upgrade also implements the fund recovery procedure defined in proposal 29. The code is [here](https://github.com/cosmos/gaia/blob/main/app/prop29.go). As requested during the discussion of the governance proposal, the migration and fund recovery procedure verifies all signatures. This code was tested during the cosmoshub-3 simulated upgrade testnet. - -## Stargate Upgrade Steps - ------------- -The upgrade steps for the simulated upgrade of the current Cosmoshub mainnet to Cosmos Stargate includes the following steps: - -The upgrade instructions will continue to improve as a living [document](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-3.md). The Gaia maintainers will continue to improve the instruction below. - -This section is with the current `gaia 2.0.*` implementation. - - 1. Validators should set their `gaia` with a halt time of `1613628000`ie. 06:00 UTC on Feb 18th in Unix time. - - 2. Validators should then export the current cosmos state with `gaiad export > cosmoshub-3-export.json` - - 3. Validators should determine the height of the last block as `last-cosmoshub-3_block`. This can be easily determined from gaia logs. - - 4. Validators should back up their `.gaiad` directory. - -This section is with the upgraded `gaia 4.0.*` implemenataion. - - 1. Validators should then migrate the exported genesis state. `gaiad migrate cosmoshub-3-export.json --chain-id=cosmoshub-4 --initial-height [last_cosmoshub-3_block+1] > genesis.json` - 2. Validators should (**AFTER ENSURING IT IS BACKED UP**!) delete their `~/.gaiad` directory and create a new one with `gaiad init [name]` and then edit their configuration files or recover the config files from backups. - 3. Validators should then start `cosmoshub-4` with `gaiad start`. Automated audits of the genesis state can take 30-120 min using the crisis module. This can be disabled by `gaiad start --x-crisis-skip-assert-invariants`. - -Validators should expect that at least 16GB of RAM needs to be provisioned to process the first new block on cosmoshub-4. - -## Time of the Upgrade - ------------- -We propose scheduling the Cosmoshub-3 to Cosmoshub-4 upgrade for Thursday Feb 18th, 2021 at 0600 UTC - -* West Coast USA: 10 PM on Feb 17 -* East Coast USA: 1 AM on Feb 18 -* Central Europe: 7 AM on Feb 18 -* Seoul: 5 PM on Feb 18 - -## The git commit of Gaia that we are upgrading to - ------------- -`a279d091c6f66f8a91c87943139ebaecdd84f689` - -## What we're doing while voting is happening - ------------- - -We expect that integration partners will be motivated to finish their preparations for the upgrade during the period when the governance proposal is running. - -We will upgrade the stargate-final testnet to support Gaia v4.0 and continue the integration progress with exchanges, blockexplorers and wallets. - -[Stargate Ecosystem Readiness Report](https://github.com/cosmos/stargate-launch/blob/master/ecosystem_readiness.md) is a living document. We will be updating this document as we get reports of completed end to end testing. We expect a hard deadline to be motivating. - -## What is the upgrade abort process - ------------- - -There are multiple circumstances where the proposal should be abandoned even if it passes: - -1. A critical vulnerability may be found in the software. If the development teams change their recommended version of gaia, the validator set should implicitly abandon this upgrade procedure. A signaling proposal will be made to indicate a vulnerability or defect in the upgrade has been found. A future proposal will be made to the Hub to upgrade to the new target commit. - -2. The migration process fails could fail to produce a valid cosmoshub-4 genesis file. This would manifest as ad-hoc changes to genesis needed to start or a failure to produce blocks from `cosmoshub-4`. In this case, the validator set should restart cosmoshub-3 at `last-cosmoshub-3_block` and a future governance proposal will be done to initiate another upgrade. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/proposal.json b/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/proposal.json deleted file mode 100644 index 2d03ed2c687..00000000000 --- a/docs/docs/governance/proposals/2021-01-stargate-upgrade-b/proposal.json +++ /dev/null @@ -1,7 +0,0 @@ - -{ - "title":"Stargate Upgrade- Second time is a charm!", - "description":"Proposal to complete the Stargate upgrade, halt `cosmoshub-3` at 06:00 UTC on Feb 18th, export the state and start `cosmoshub-4` based on gaia 4.0.\n\n Gaia Commit hash: \n a279d091c6f66f8a91c87943139ebaecdd84f689 Proposal details can be found on \n github: https://github.com/cosmos/governance/pull/13 \n Rendered: https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/QmYn2SxCMYk5SWs5GMcXdbXR8wMCCXRmCyW19SFyzSeZp1 \n ipfs: https://cloudflare-ipfs.com/ipfs/QmYn2SxCMYk5SWs5GMcXdbXR8wMCCXRmCyW19SFyzSeZp1 \n sia: https://siasky.net/EACAsPcUjpTEpQlG9_nRI1OR07gNeRiudfEWAvKnf0tj_Q \n ", - "type":"Text", - "deposit":"256000000uatom" -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-stargate-upgrade/README.md b/docs/docs/governance/proposals/2021-01-stargate-upgrade/README.md deleted file mode 100644 index 0d9518a95d1..00000000000 --- a/docs/docs/governance/proposals/2021-01-stargate-upgrade/README.md +++ /dev/null @@ -1,148 +0,0 @@ ---- -title: Cosmos Stargate Hub Upgrade Proposal 2 - Time to Upgrade ---- - - - -![Stargate Upgrade banner graphic](https://siasky.net/AADU5rg0GvapbrICLUk7SxZeMDrKo5Q8oLrpOwl71wXhnQ) - -## by Iqlusion - -Jan 11, 2021 - -## Key Results - ------------- -If passed, this governance proposal would commit the Cosmos Hub to halting the `cosmoshub-3` at 06:00 UTC on Jan 28th exporting the state and starting `cosmoshub-4` based on gaia 3.0. - -## Context - ------------- - -In [Proposal 27](https://ipfs.io/ipfs/Qmbo3fF54tX3JdoHZNVLcSBrdkXLie56Vh2u29wLfs4PnW), Iqlusion proposed a comprehensive process to translate the unprecented surface area of this upgrade. We called this process Stargate. - -Iqlusion is pleased to report that the Stargate Process has been successfully executed. We believe the ecosystem is ready and the Hub can safely step through the Stargate. - -After the success of the community approval of the first Stargate Upgrade proposal, we now follow-up with the second Stargate proposal for the Cosmos Hub that will outline the results of the first proposal and the process for upgrading the Hub. - -## The Stargate Plan - ------------- -The purpose of the Stargate effort was to ensure that Cosmos can fulfill the vision of an Internet of Blockchains in 2021 while mitigating the technological and organizational risks outlined in the [original Stargate Upgrade Proposal 27](https://ipfs.io/ipfs/Qmbo3fF54tX3JdoHZNVLcSBrdkXLie56Vh2u29wLfs4PnW). It was also an attempt to create a process for complex future on-chain upgrades on the Cosmos Hub. That included the following steps: - -1. Run the Stargate Testnet and use this as an integration testing target with widest possible ecosystem participation to help confirm the readiness of the release software. - -2. Engage and support critical partners during the integration process so that partners are able to actively participate in the testing process and provide insights into their success with the upgrade. - -3. Dedicate significant resources in terms of full time human resources and documentation efforts to ensure that everyone integrated into the Cosmos Hub can self-certify as Stargate-ready. - -4. Report back to the Hub on the success of the integration process. - - - We expect that the primary responsibility of the Cosmos Hub is to assess whether we have mitigated the above risks sufficiently. - - - Provide a written report of the entire Stargate effort to enable Hub governance to make an informed decision. - -5. At conclusion, we will indicate why we have confidence that an upgrade won't be disruptive to the Hub’s ecosystem. - -## Stargate Plan Results - ------------- - -### 1. Ecoystem Participation - -The results of ecosystem participation and engagement are available in our [Stargate Ecosystem Readiness Report](https://github.com/cosmosdevs/stargate/blob/master/ecosystem_readiness.md). We list on this page ecosystem partners such as Validators that provided their validator public keys as well as infrastructure partners that confirmed their integration testing the Stargate testnet tags. Validators, exchanges, and wallets have made up the most responsive of their results completing integration testing of the stargate releases. We anticpate that all actors in the ecosystem are aware and ready to respond to the new Cosmos Hub features. Integration partners have helped find regression in the legacy amino compatibility layer and those have been resolved. - -The Cosmos SDK, Tendermint Core, Tendermint Inc, and IBC teams worked tirelessly to deliver the most robust software feature set that would make up the Cosmos Stargate release. Their review of their efforts are documented in their post ["How Seven Teams Collaborated To Deliver The Biggest Software Upgrade In The Cosmos Universe"](https://blog.cosmos.network/how-seven-teams-collaborated-to-deliver-the-biggest-software-upgrade-in-the-cosmos-universe-2288f4f9afe8). - -Integration testing continued through the release of the Cosmos SDK v0.40.0-rc2 that makes up the Cosmos-hub Stargate testnet tag for a simulated upgrade of the CosmosHub-3 to CosmosHub-4. Also, the AiB team continues to deliver simulation testing of Cosmos Stargate to ensure that any possible chain bug issues can be detected and documented. - -We are confident that we have and continue to achieve increased ecosystem engagement with the Stargate testnet. - -### 2. Critical Partner Support - -We delivered critical partner support to leading ATOM exchanges. Out of the exchange support efforts, we documented the [IBC Readiness Matrix](https://github.com/cosmosdevs/stargate/blob/master/ibc_readiness_matrix.md) that outlines the levels of readiness that exchanges may select as they upgrade to Cosmos Stargate. - -We also completed and delivered a completed legacy Amino Audit, [AminoRest & You](https://github.com/cosmosdevs/stargate/blob/master/audit.md). The core finding of this audit was that changes to the underlying structs result in an interface that is close to the prior version allowing legacy queries to return valid data. - -All previous Cosmos Hub upgrades reset the block height. Our interactions with ecosystem particpants identified this as introducing significant complexity to handling this upgrade. This will be the first upgrade of the Cosmos Hub that starts the blockchain at the height + 1 of the antecedent chain. - -### 3. Documentation and Self-Certification - -Documentation was a success for the Cosmos Stargate effort. The upgrades with the most breaking changes such as legacy Amino have a complete audit with documentation on exceptions for blockchain API interfaces. - -Most exchanges and wallets have taken self-certification on directly. Our team continues to provide real-time support on multiple partner slack channels and on the Cosmos [#stargate Discord](https://discord.com/invite/cosmosnetwork) channel. - -We have conducted numerous testnets with different partners. A particularly important testnet conducted with a significant fraction of the Hub validator set was a simulated upgrade of the cosmoshub on Nov 25th,2020. This tested the full upgrade flow including the prop29 implementation and height preserving upgrade functionality. - - -### Conclusion - -The governance proposal is our report back to the community on the success of the Stargate program. We have compiled detailed information for the community as a reference in the Stargate [repository](https://github.com/cosmosdevs/stargate). - -### Cosmos Stargate Integration Success - -Cosmos Stargate integration success with exchanges and wallet providers reflects the quality of the code developed by the various Cosmos teams. - -## Prop 29 - -This upgrade also implements the fund recovery procedure defined in proposal 29. The code is [here](https://github.com/cosmos/gaia/blob/main/app/prop29.go). As requested during the discussion of the governance proposal, the migration and fund recovery procedure verifies all signatures. This code was tested during the cosmoshub-3 simulated upgrade testnet. - -## Stargate Upgrade Steps - ------------- -The upgrade steps for the simulated upgrade of the current Cosmoshub mainnet to Cosmos Stargate includes the following steps: - -This section is with the current `gaia 2.0.*` implementation. - - 1. Validators should set their `gaia` with a halt time of `1611813600`ie. 06:00 UTC on Jan 28th in Unix time. - - 2. Validators should then export the current cosmos state with `gaiad export > cosmoshub-3-export.json` - - 3. Validators should determine the height of the last block as `last-cosmoshub-3_block`. - - 4. Validators should back up their `.gaiad` directory. - -This section is with the upgraded `gaia 3.0.*` implemenataion. - - 1. Validators should then migrate the exported genesis state. `gaiad migrate cosmoshub-3-export.json --chain-id=cosmoshub-4 --initial-height [last_cosmoshub-3_block+1] > genesis.json` - 2. Validators should (**AFTER ENSURING IT IS BACKED UP**!) delete their `~/.gaiad` directory and create a new one with `gaiad init [name]` and then edit their configuration files or recover the config files from backups. - 3. Validators should then start `cosmoshub-4` with `gaiad start`. Automated audits of the genesis state can take 30-120 min using the crisis module. This can be disabled by `gaiad start --x-crisis-skip-assert-invariants`. - -Validators should expect that at least 16GB of RAM needs to be provisioned to process the first new block on cosmoshub-4. - -## Time of the Upgrade - ------------- -We propose scheduling the Cosmoshub-3 to Cosmoshub-4 upgrade for Thursday Jan 28th, 2021 at 0600 UTC - -- West Coast USA: 10 PM on Jan 27 -- East Coast USA: 1 AM on Jan 28 -- Central Europe: 7 AM on Jan 28 -- Seoul: 5 PM on Jan 28 - -## The git commit of Gaia that we are upgrading to - ------------- -`d974b27a8caf8cad3b06fbe4678871e4b0b69a51` - -## What we're doing while voting is happening - ------------- - -We expect that integration partners will be motivated to finish their preparations for the upgrade during the period when the governance proposal is running. - -A testnet with the final version of Gaia 3.0 will be running to assist with integrations. - -[Stargate Ecosystem Readiness Report](https://github.com/cosmosdevs/stargate/blob/master/ecosystem_readiness.md) is a living document. We will be updating this document as we get reports of completed end to end testing. We expect a hard deadline to be motivating. - -## What is the upgrade abort process - ------------- - -There are multiple circumstances where the proposal should be abandoned even if it passes: - -1. A critical vulnerability may be found in the software. If the development teams change their recommended version of gaia, the validator set should implicitly abandon this upgrade procedure. A future proposal will be made to the Hub to upgrade to the new target commit. - -2. The migration process fails could fail to produce a valid cosmoshub-4 genesis file. This would manifest as ad-hoc changes to genesis needed to start or a failure to produce blocks from `cosmoshub-4`. In this case, the validator set should restart cosmoshub-3 at `last-cosmoshub-3_block` and a future governance proposal will be done to initiate another upgrade. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-01-stargate-upgrade/proposal.json b/docs/docs/governance/proposals/2021-01-stargate-upgrade/proposal.json deleted file mode 100644 index 44ae6c89167..00000000000 --- a/docs/docs/governance/proposals/2021-01-stargate-upgrade/proposal.json +++ /dev/null @@ -1,4 +0,0 @@ -{ - "title":"Cosmos Stargate Hub Upgrade Proposal 2: Time to Upgrade.", - "description":"Proposal to complete the Stargate upgrade, halt `cosmoshub-3` at 06:00 UTC on Jan 28th, export the state and start `cosmoshub-4` based on gaia 3.0.\n\n Gaia Commit hash: \n d974b27a8caf8cad3b06fbe4678871e4b0b69a51 Proposal details can be found on \n github: https://github.com/cosmos/governance/pull/5 \n ipfs: https://cloudflare-ipfs.com/ipfs/QmPww2PSmkmuLLu12GGwRdu5ur1Etf9u3Nt3Z6NqB7BQP1 \n sia: https://siasky.net/EAALGMzFCafvbKkQjnAieo2cA1mpxk-JLpKsiC4XxuM6eQ \n " -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/README.md b/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/README.md deleted file mode 100644 index 089879e4e18..00000000000 --- a/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/README.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Enable IBC Transfers ---- - - - -The Proposal enables transferring and receiving assets using the ICS20 standard on the Cosmos Hub. If this proposal passes, there will be IBC assets available in the Bank module of the Hub and ATOM will be available on Zones connected over IBC. -Iqlusion believes that the IBC software is sufficiently stable for small amounts of value transfer. We expect there to be issues with stuck funds and UX confusion but overcoming these issues will only happen once IBC is live. - -## Security Model - -Tendermint full nodes produce agreement under the assumption that at most ⅓ of the voting power held by validators is Byzantine. - -## IBC - -IBC is a protocol for authenticated message passing between heterogeneous sovereign blockchains. IBC requires trusting that chains on both sides of the connections operate within their security model. - -## Incentive Security Extensions - -IBC has a facility to support freezing connections once a violation of the security model has occurred. The set of criteria for detecting such attacks continues to evolve and is a constant focus of research. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/proposal.json b/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/proposal.json deleted file mode 100644 index 569ced09dad..00000000000 --- a/docs/docs/governance/proposals/2021-03-enable-ibc-transfers/proposal.json +++ /dev/null @@ -1,17 +0,0 @@ -{ - "title": "Enable IBC transfers", - "description": "The Proposal enables transferring and receiving assets using the ICS20 standard on the Cosmos Hub. If this proposal passes, there will be IBC assets available in the Bank module of the Hub and ATOM will be available on Zones connected over IBC.\n Iqlusion believes that the IBC software is sufficiently stable for small amounts of value transfer. We expect there to be issues with stuck funds and UX confusion but overcoming these issues will only happen once IBC is live.\n Security Model\n Tendermint full nodes produce agreement under the assumption that at most ⅓ of the voting power held by validators is Byzantine.\n IBC\nIBC is a protocol for authenticated message passing between heterogeneous sovereign blockchains. IBC requires trusting that chains on both sides of the connections operate within their security model.\n Incentive Security Extensions\n IBC has a facility to support freezing connections once a violation of the security model has occurred. The set of criteria for detecting such attacks continues to evolve and is a constant focus of research.", - "changes": [ - { - "subspace": "transfer", - "key":"SendEnabled", - "value": true - }, - { - "subspace": "transfer", - "key":"ReceiveEnabled", - "value": true - } - ], - "deposit": "1000000uatom" -} diff --git a/docs/docs/governance/proposals/2021-04-advancing-ethermint/README.md b/docs/docs/governance/proposals/2021-04-advancing-ethermint/README.md deleted file mode 100644 index 499c7d3dee1..00000000000 --- a/docs/docs/governance/proposals/2021-04-advancing-ethermint/README.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: Advancing Ethermint - Governance Proposal - GTM and Engineering Plan for the Ethermint Chain ---- - - - -> **NOTE**: this is a short version of the full proposal. To read the full document click [here](https://forum.cosmos.network/t/advancing-ethermint-governance-proposal-gtm-and-engineering-plan-for-the-ethermint-chain/4554). - -### Author - -Federico Kunze Küllmer: [@fedekunze](https://github.com/fedekunze) - -## Summary - -Tharsis is requesting 100,000 ATOMs from the Cosmos Hub community pool to fund, develop and advance the Ethermint project and launch an Ethermint Chain. The team will use these resources to grow our dedicated Cosmos-EVM team, so we can take on the commitments and responsibilities necessary to maintain and support the Cosmos-EVM chain and codebase. - -An Ethermint environment has enormous potential to unlock new use cases within the Cosmos ecosystem that are not possible on Ethereum today. Use cases that require scalability and composability are some of the endless possibilities for Ethermint. - -Ethermint is a way of vertically and horizontally scaling the projects that deploy on Ethereum, by allowing: - -- Access to greater liquidity through IBC -- Faster transaction times through Tendermint BFT's instant finality -- Less strain on the Ethereum chain to process transactions (i.e. through gravity bridge) -- Seamless portability and composability with Ethereum Virtual Machine support - -The commitments stated in this proposal will ensure a successful launch for the Ethermint chain together with its existing contributors (ChainSafe, OKEx, Iris, Injective, etc). Launching collaboratively with Ethermint stakeholders will result in a robust and independent community within Cosmos that will enable greater developer adoption of Cosmos technology. - -The Ethermint stakeholders are partnering to execute on the long-awaited Ethermint Chain by joining forces to develop and deploy a new Cosmos EVM chain that will be used by thousands of crypto users at launch. - -## Governance Votes - -The following items summarize the voting options and what it means for this proposal. All addresses that vote on the proposal might be eligible for a future airdrop. - -- **YES**: You approve the proposal statements and distribute the amount of 100,000 ATOMs to the multisig address. The treasury will allocate the funds to the Tharsis team, leading Ethermint's core development efforts and supporting the chain's go-to-market strategy. It will also lead to core technology maintenance and continuous discussion to ensure the project's longevity. -- **NO**: The NO vote is a request for improvements or adjustments. You agree that this proposal's motivation is valuable and that the team should create a follow-up proposal once the amendments are included. -- **NO (VETO)**: You veto the entire motivation for the proposal and expect the ICF and current maintainers to make the determination and continue the stewardship of the project. The proposers will not create a follow-up proposal. -- **ABSTAIN**: You are impartial to the outcome of the proposal. - -## Multisig and release of funds - -Upon the approval of the proposal, the treasury will distribute the funds to a ⅔ multi-signature account managed by the following individuals/partners: - -- Federico Kunze Küllmer - Tharsis (proposer) -- Zaki Manian - Iqlusion -- Marko Baricevic - Interchain GmbH - -The account address is: `cosmos124ezy53svellxqs075g69n4f5c0yzcy5slw7xz` - -If the proposal passes, the team will immediately receive 40% of the funds to expand its engineering team and other business development efforts to support GTM for the chain. The remaining 60% will be released in an equal proportion to the number of milestones upon the completion of each milestone. For any reason, if the proposer has not completed the next milestone within a year of the last payment, the remaining funds held in the multisig account will be returned to the community pool. - -## Product commitment - -The current proposal aims to develop all the necessary components for a successful Ethermint chain. Our team will lead the core development efforts to execute the points below. - -### Hard Commitments - -These are the items that are mandatory for the release of funds. The items will be split into four milestones. - -> NOTE: Some of the items below are currently stated under ChainSafe's service agreement with the ICF for Ethermint. Our team will collaborate with them on these items so that they are included by the time the EVM chain is launched. These items are marked below as [CS] - -#### Milestone 1: Developer Usability and Testing - -This milestone aims to reach a stage where developers can begin deployments of Ethermint with the latest Cosmos SDK version and test their smart contracts in what will feel like a seamless experience. - -- **Starport support**: Collaborate to ensure compatibility with Starport for developers that wish to use the EVM module with the latest SDK version on their sovereign chains. -- **Rosetta API support**: Support Ethermint transactions and queries on Coinbase’s Rosetta API that has been integrated into the SDK. -- **EVM Consistency**: Ensure that Ethermint can operate the same state as Ethereum and deterministically runs smart contract executions, exactly how Geth does (for example, checking the gas used between Ethermint and Geth) -- **Replay attack protection**: Register Ethermint permanent testnet and mainnet chain-ids to [ChainID Registry](https://chainid.network/) according to [EIP 155](https://eips.ethereum.org/EIPS/eip-155). -- **Documentation**: Ensure the documentation for both Ethermint and the EVM module are up to date with the implementation. JSON-RPC and OpenAPI (Swagger) docs for gRPC gateway and Rosetta will also be available for client developers. The team will create relevant sections to compare and distinguish key components of Ethermint and their corresponding ones on Ethereum. [CS] -- **Metrics**: We plan to list relevant metrics available through the SDK telemetry system for user engagement information such as the number of contracts deployed, amount transacted, gas usage per block, number of accounts created, number and amount IBC transfers to and from Ethermint, etc. These metrics will be displayed in a Dashboard UI in the form of charts. [CS] -- **Ensure compatibility with Ethereum tooling**: Test and coordinate with dev teams to test compatibility with (Truffle, Ganache, Metamask, web3.js, ethers.js, etc) and ensure the same dev UX as with Ethereum. The compatibility will then be ensured through end-to-end and integration tests. [CS] -- **User Guides**: Relevant guides will be added to connect Ethermint with the tools mentioned above. -- **Cosmjs Library support**: Make Ethermint keys, signing, queries, and txs compatible with the [cosmjs](https://github.com/cosmos/cosmjs) library. -- [**EIP 3085**](https://eips.ethereum.org/EIPS/eip-3085) **support**: add `wallet_addEthereumChain` JSON-RPC endpoint for Ethermint. - -#### Milestone 2: Maximizing Performance and Compatibility - -This milestone aims to enhance and benchmark the Ethermint chain's performance so developers can experience its superior benefits over existing solutions in the market. - -- **EVM module readiness**: The current x/evm module from Ethermint suffers from technical debt regarding its architecture. The current proposal will do a bottleneck analysis of the EVM state transitions to redesign the EVM module to boost performance. -- **Benchmarks**: As a final step, we will be performing benchmarks for Ethereum transactions before and after the EVM refactor has been completed. [CS] -- **Maintain a permanent testnet**: Ethermint will have a permanent testnet to ease the development process for Ethereum developers and clients that wish to connect to Ethermint. The team will create a dedicated website, infrastructure, and faucet UI for users to request funds. -- **Faucet support**: The team will ensure an Ethermint-compatible faucet implementation is supported to ensure the sustainability of the permanent testnet. This will be also integrated into the existing faucet library of cosmjs. [CS] -- **Ethereum Bridge**: Integrate a combination of the following bridges in order to make Ethermint interoperable with Ethereum ERC20s: Cosmos Gravity bridge, IBC solo machine bridge, Chainbridge [CS]. - -#### Milestone 3: Mainnet readiness - -This milestone's objective is to enhance security and users' accessibility to Ethermint, and stress-test the network before the mainnet launch. - -- **Relayer Integration**: While the Ethermint migration to the SDK Stargate version supports IBC fungible token transfers on the app level, additional setup and integration is required to the IBC relayers to enable compatibility with Ethermint fully. The team will integrate the Ethermint keys and the remaining pieces to the relayer for full IBC support. -- **Ledger Support**: The team will perform an assessment of the current Cosmos and Ethereum ledger device applications to test their compatibility with Ethermint. If the keys or signing is not supported, the team will coordinate with ZondaX, the Ledger team, and other key partners to integrate the patches to the corresponding apps. -- **Simulations**: fuzz transaction testing for Ethermint and the EVM module. This will be done through the implementation of simulations and the [manticore](https://github.com/trailofbits/manticore) smart contract execution analysis tool. - -#### Milestone 4: Mainnet launch - -This milestone aims to provide support and coordination across the Cosmos community to ensure a safe and successful launch of the Ethermint mainnet. - -- **Incentivized Testnet:** Planification, coordination and launch of the upcoming Ethermint’s incentivized testnet: Game of Ethermint. -- **Support Mainnet launch**: The team will support Ethermint’s mainnet launch by coordinating with key stakeholders, ecosystem partners, validators, community, etc. [CS] - -#### Ongoing tasks - -Below are hard commitment items that are required for a successful launch but don’t fit into any particular milestone as they are recurring over the whole development period. - -- **Core Ethermint repository maintenance**: The team will commit to review community contributions and engage with issues and discussions regarding bugs and feature requests in the core codebase. -- **Coordination with Cosmos SDK core team**: Since the Ethermint codebase uses a lot of custom functionality (keys, `AnteHandler`, modular servers, etc) some changes/patches will need to be upstreamed to the Cosmos SDK to ensure modularity and non-breakingness. -- **Client support**: Develop partnerships with exchanges and wallets to support Ethermint through the Ethereum-compatible JSON-RPC or the gRPC services from the SDK since day one. -- **Community support**: Respond and support the community inquiries on Discord and other relevant channels. -- **Security Audit**: perform an internal and a third-party security audit prior to launch. -- **Bug bounty**: Coordinate a bug bounty program for the EVM module and the JSON-RPC server prior to launch. - -## Soft Commitments - -See the [full version](https://forum.cosmos.network/t/advancing-ethermint-governance-proposal-gtm-and-engineering-plan-for-the-ethermint-chain/4554) of this document. - -## Conclusion - -With this proposal, Tharsis plans to expedite the Ethermint chain's development and launch the network by Q4 2021. Ethermint will be the first EVM-compatible chain on Cosmos that will be fully interoperable with other BFT and EVM chains via IBC and the Gravity bridge. - -By creating and envisioning this long-term roadmap, we believe Ethermint can act as the vital component of the Interchain and serve as the gateway between the Ethereum and Cosmos ecosystems: The Ethermint launch will combine the Cosmos and Ethereum communities and provide new economic opportunities for millions of users. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-04-advancing-ethermint/proposal.json b/docs/docs/governance/proposals/2021-04-advancing-ethermint/proposal.json deleted file mode 100644 index e34fb598d09..00000000000 --- a/docs/docs/governance/proposals/2021-04-advancing-ethermint/proposal.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "title": "Advancing Ethermint: GTM and Engineering Plan for the Ethermint Chain", - "description": "Tharsis is requesting 100,000 ATOMs from the Cosmos Hub community pool to fund, develop and advance the Ethermint project and launch an Ethermint Chain. n\n More details can be found in the long form proposal here: https://gateway.pinata.cloud/ipfs/QmWwJ63V4TuZkDfWoH66vxd6NK82g6rgPVnypESXBFRbws and https://github.com/cosmos/governance/pull/18 and https://forum.cosmos.network/t/advancing-ethermint-governance-proposal-gtm-and-engineering-plan-for-the-ethermint-chain/4554. \n\n The multisig administration includes:\n\t - @fedekunze (Federico Kunze Küllmer, Tharsis)\n\t - @zmanian (Zaki Manian, Iqlusion)\n\t - @marbar3778 (Marko Baricevic, Interchain GmbH)", - "recipient": "cosmos124ezy53svellxqs075g69n4f5c0yzcy5slw7xz", - "amount": "100000000000uatom", - "deposit": "256000000uatom" -} diff --git a/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/README.md b/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/README.md deleted file mode 100644 index 10d92d389b0..00000000000 --- a/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/README.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: Parameter change - lower minimum proposal deposit amount ---- - - -## Summary - -The current deposit amount of 512 ATOMs prohibits valuable governance activity from small holders or those with most of their ATOM staked. We propose lowering the requirement to 64 ATOMS. - -## Objectives - -1. Enable community members with good ideas but little capital to participate in governance and request resources from the community pool treasury. -2. Improve the governance UX for holders who keep most of their ATOM staked. -3. Increase utilisation of treasury (currently 666,457 ATOM, approximately $14 MM USD, at time of writing). -4. Accelerate Cosmos Hub development and growth. - -## Background - -Current deposit is 512 ATOMs (approximately $10k USD today). The ATOM price when the community treasury was activated (2019-05-03) was $4.99 (source: CoinMarketCap), meaning the total required deposit to submit a proposal was $2,555. Today, most proposers must coordinate with large ATOM holders to request additional funds in order to meet the minimum deposit requirements. This also applies to large ATOM holders who want to be active in governance but do not have enough liquid ATOM to meet the deposit requirements, as staked ATOM cannot be used to post deposits. - -## Proposers - -Federico Kunze Küllmer (Tharsis) and Sam Hart (Interchain). - -Credit to Gavin Birch (Figment Networks) and the Cosmos Governance Working Group (GWG) for initiating a recent conversation that motivated this proposal. - -## Proposed Parameter Change - -Change the minimum proposal deposit requirement from 512 ATOMs (aprox. $10,000 USD) to 64 ATOMs (aprox. $1,300 USD). - -Note: Parameters are denominated in micro-ATOMs, as described in the [governance parameter list](https://github.com/cosmos/governance/blob/master/params-change/Governance.md). - -## Risks - -__This change makes it easier to submit spam proposals.__ - -While this is true, in order to fully mitigate spam the Cosmos Hub must increase the minimum deposit required for proposal [submission](https://cosmoscan.net/proposal/28). - -__By increasing the number of submissions, voter participation or the level of consideration given to each proposal may decrease.__ - -We believe this is a justifiable trade-off for promoting more community-driven initiatives and enthusiasm for advancing Cosmos. As we lower the barrier to entry for governance participation, we invite community members to take this opportunity to enact more effective and efficient governance practices. The upcoming Groups, Authz, and Interchain Accounts modules will provide powerful abstractions to this end. - -## Alternatives - -__Wait for the Cosmos Hub to adopt proposed changes to the Governance module for variable deposit amounts, quorom thresholds, and voting periods.__ - -These initiatives should not be mutually exclusive. While research and development of these features is ongoing, the Cosmos Hub will benefit from this parameter change today, as well as the precedent it sets for self-improving governance. - -__Since the ATOM price fluctuates with respect to USD, make proposal thresholds reference a stable price oracle__ - -This is an interesting design space, however it becomes more plausible if and when the Cosmos Hub adds a decentralized exchange that can be used to produce a reference rate. Lowering the proposal threshold is a temporary solution that will help in the short-term. - -## Governance Votes - -The following items summarise the voting options and what it means for this proposal. - -- **YES**: You approve the parameter change proposal to decrease the governance proposal deposit requirements from 512 to 64 ATOMs. -- **NO**: You disapprove of the parameter change in its current form (please indicate in the Cosmos Forum why this is the case). -- **NO WITH VETO**: You are strongly opposed to this change and will exit the network if passed. -- **ABSTAIN**: You are impartial to the outcome of the proposal. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/proposal.json b/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/proposal.json deleted file mode 100644 index 438f5100a6d..00000000000 --- a/docs/docs/governance/proposals/2021-04-lower-deposit-requirement/proposal.json +++ /dev/null @@ -1,24 +0,0 @@ -{ - "title": "Parameter change: lower minimum proposal deposit amount", - "description": "The current deposit amount of 512 ATOMs prohibits valuable governance activity from small holders or those with most of their ATOM staked. We propose lowering the requirment to 64 ATOMS.", - "changes": [ - { - "subspace": "gov", - "key":"depositparams", - "value": { - "min_deposit": [ - { - "denom": "uatom", - "amount": "64000000" - } - ] - } - } - ], - "deposit": [ - { - "denom": "uatom", - "amount": "1000000" - } - ] -} diff --git a/docs/docs/governance/proposals/2021-04-prop34-continuation/README.md b/docs/docs/governance/proposals/2021-04-prop34-continuation/README.md deleted file mode 100644 index 6bf4dc35541..00000000000 --- a/docs/docs/governance/proposals/2021-04-prop34-continuation/README.md +++ /dev/null @@ -1,163 +0,0 @@ ---- -title: Proposal 46 - Extend Luna Mission to Fund ATOM Marketing ---- - - -The Cosmos community approved Proposal 34 on 2021-01-20 allocating 129,208 ATOM to implement a comprehensive ATOM marketing plan executed in collaboration with key community stakeholders. Proposal 46 is requesting an extension of the time allowed to spend the approved budget and allocate existing funds for additional ATOM-focused priorities. Below are details of this request and an outline of the successful results of Proposal 34 marketing spend as of 2021-03-31. - -## PROPOSAL 46 REQUEST - -1. _*Prop 34 Time Extension:*_ The Prop 34 Implementation team seeks a three-month extension (until 2021-07-20) to fully spend the existing budget allocation under the terms approved in Proposal 34. The multisig team and AiB (Tendermint) invested significant time and energy properly researching, vetting and managing vendors, contractors, and opportunities requiring additional time to complete the Prop 34 expenditure of funds. With the approval of Proposal 46, any unspent funds remaining from Proposal 34 efforts will be returned to the community pool on 2021-07-20. -1. _*Additional Budget Priority - Project Execution Fund Pool:*_ Execution, oversight, and accountability for this significant marketing spend requires substantive operational support. In addition to the 5 multisig administrators, Zaki Manian, Jack Zampolin, Immasssi, Jhonnie and Joe Dirtay, extensive support is being provided by Adriana Mihai (Kalpatech), Garrette Furo (Regen Network), David Fortson (Regen Network/LOACOM), and others. We request an allocation of 3000 ATOM (from the existing budget) to compensate the aforementioned contributors for previous and ongoing support of this expansive marketing campaign. Funds will be distributed through the multisig administration. -1. _*Additional Budget Priority - Gravity DEX:*_ This proposal seeks to allocate 10,000 - 20,000 ATOM (from approved Prop 34 budget) to identify and support robust marketing of the Gravity DEX testnet and DEX mainnet launch- an AMM exchange that will have a significant impact on ATOM valuation if successful. Gravity DEX is initially planned as an automated market maker (AMM) exchange that will allow users to trade IBC token pairs and provide liquidity for traders. These tokens would arrive on the Hub through IBC-enabled chains, IBC-wrapped ETH and ERC20 tokens, IBC-wrapped BTC tokens, and as well as future blockchain ecosystems that implement the IBC protocol. -1. _*Community Created YouTube Videos:*_ After evaluating the existing meme campaign, the project management team is recommending ceasing the community meme campaign and reallocating remaining funds for community-created YouTube videos. This campaign would reward community members for creating select videos for prospective or new token holders focused on ‘How to’ and explainer videos on topics such as “How to set up your wallet,” “How to stake your $ATOM,” “How to delegate, redelegate and participate in governance,” and more. - -## SECTION I OVERVIEW - -A summary report of current marketing activities and related analytics can be found here. Highlights include (Date Range 2021-01-20 to 2021-03-31): - -* ATOM Valuation: ATOM valuation has increased from $8.92 to $19.10 - a 214% increase. -* Twitter: New 2020 and 2021 record on new followers and engagement: - - *New followers:* Q1 Twitter: 45,380 new followers ( 2,236 in Q1 2020, 1940% increase) - - *Engagement:* 10.3M impressions ( 2,16M in Q1 2020, 476% increase) -* Youtube - - *New subscribers:* 1,3k new subscribers (195 in Q1 2020, 667% increase) - - *Impressions and views:* 447k impressions ( 126k in Q1 2020, 355% increase) , 47,4k views ( 10,1k views Q1 2020, 469% increase) -* Cosmos website - - +396% new users, +355% sessions - - +380% unique page views, +64% pages per session, -28% bounce rate - - 1,079,000 visitors, 244,000 new users from which 28,804 acquired new users from the marketing campaign. -* Cosmos Hub - * 31,408 new delegators (increase from 41,885 to 73,293 - a 74% increase.) - * 92,561 new ATOM accounts (increase from 136,219 accounts to 228,780 accounts - a 68% increase.) -* Blockfolio Signal - * 270,000 new followers, increase from 220,000 to 490,000 as of March 31st. ( As of April 21st, total number of followers reached 1,3 Million followers) - -### Spend Overview - -As of 2021-03-31, a total of 41,912 ATOM have been spent in the following ways: -- Meme Contest: 0 ATOM -- Banner ads - 8,750 ATOM -- Influencers: twitter posts and youtube shows - 25,462 ATOM -- Podcasts, newsletters- 6,200 ATOM -- Media/TV: 1,000 ATOM -- Signers fee: 500 ATOM - -Additionally as of 2021-04-21, a total of 22,610 ATOM have been spent for: -- Meme contest: 240 ATOM -- PR company: 990 ATOM -- Twitter influencers: 9,550 ATOM -- Community management: 150 ATOM -- Banner ads: 11,680 ATOM - -#### Total ATOM spent as of 2021-04-21 is of 64,522 ATOM, remaining budget is of 64,655 ATOM. - -## SECTION II - HISTORY - -The Cosmos Hub (ATOM) community approved the passage of Proposal 34 - Luna Mission - Funding $ATOM on 2021-01-20 at 74% yes, 18.9% abstain and 7.1% no. - -Proposal 34 authorized a spending pool of 129,208 ATOM to implement a comprehensive ATOM marketing plan executed in collaboration with AiB (Tendermint). The funds deriving from Prop 34 have been approved by @johnniecosmos, @JoeDirtay, @jackzampolin (Jack Zampolin, Pylon Validator), @immasssi (SG-1 Validator), @zakimanian (Zaki Manian, Iqlusion Validator), as the designated multisig committee. Current funding allocation is due to expire and be returned to the community pool if Proposal 46 does not pass. - -## SECTION III - DELIVERABLES - -Proposal 34 - Results Summary - 2021-01-20 to 2021-03-31 - -1. Banner Ads - - Locations: - * Wallets: Blockfolio, Coinstats - * Platforms: Coingecko, Stacking Rewards - - Sample Banner: https://drive.google.com/drive/folders/1JFpJewRGsQfrK57BxEdE0Pk3ae37ldpL - - Duration of the campaign ads: 1-3 months - - Total performance on all 4 venues: (#37,000,000 impressions, #28,804 new acquired visitors, over #100,000 new wallets downloads with ATOM as preset currency) - - Total Spent: *8,750 ATOMs* -1. Marketing contracts - * Podcasts: - - Charlie Shrem - * Twitter account: https://twitter.com/CharlieShrem - * Followers: 199k - * https://twitter.com/CharlieShrem/status/1376550892321730563?s=20 - * Performance: 268K Twitter Impressions, 6265 Podcast Downloads, & 7600 youtube views. - - Scott Melker - * Twitter Account: https://twitter.com/scottmelker - * Followers: 290K - * https://www.youtube.com/watch?v=MdIb6xImS5Q - * Newsletters/Articles: - - Scott Melker: https://thewolfofallstreets.link/cosmos​ - - The Daily Chain - * https://thedailychain.com/the-stargate-upgrade-launch-is-coming-on-cosmos-hub/ - * https://thedailychain.com/cosmos-hub-governance-passes-new-proposals-to-improve-the-project/ - * https://thedailychain.com/solving-blockchain-interoperability-with-the-cosmos-hub/ - - Blockworks - * Tweet https://twitter.com/Blockworks_/status/1381969023584272395?s=20 - * Article https://blockworks.co/cosmos-why-we-need-interoperability-in-blockchain/ - * 250,255 Dedicated Twitter Impressions, 10,653 Newsletter Impressions, 1,147 pageviews - - Total Spent: *6,200 ATOM* -1. Influencers - * Twitter - - Over 30 Twitter influencers engaged including Crypto Dog, Michaël van de Poppe and the Wolf of all Streets. - - Sample Posts: - * [Crypto Dog](https://twitter.com/thecryptodog/status/1376640286428864514?s=21 ) - * [Michaël van de Poppe](https://twitter.com/CryptoMichNL/status/1381264254033133569?s=20) - * [Scott Melker ](https://twitter.com/scottmelker/status/1383155303525576706?s=20) - * [StackingUSD](https://twitter.com/stackingusd/status/1362133942435012608?s=28) - * [MacroCRG](https://twitter.com/macrocrg/status/1364606751878881288?s=28) - * [Trader_XO](https://twitter.com/trader_xo/status/1369038610415161347?s=28 ) - * [Crypto_Chasr](https://twitter.com/crypto_chase/status/1381696722557136899?s=28 ) - - Results: from the 1st-month Twitter only (second-month data was not complete in time) - * 245 tweets, 20,000 Likes, 4,000 Retweets, 1700 Comments - * YouTube Shows & Podcasts - - Programs: Crypto Daily, Data Dash, Tech Con Catalina,Crypto Busy, Hashoshi, Crypto Michael. - - Featured Shows: - * [Crypto Daily](https://www.youtube.com/watch?v=g55JAdwVs2Q&t=254s&ab_channel=CryptoDaily) - * Subscribers: 193K - * Video views: 52,834 - * Publish date: March 1st - * [Data Dash](https://www.youtube.com/watch?v=vaZLBgi5o-w) - * Subscribers: 423K - * Video views: 40,150 - * Publish date: Feb 17th - * [Tech Con Catalina](https://www.youtube.com/watch?v=H5kHoFXjMyM) - * YouTube Followers - 115K Subscribers - * Video views: 42,415 - * Publish date: April 12th - * [Crypto Busy](https://www.youtube.com/watch?v=G2zHiIw_DZM) - * YouTube Followers - 152K Subscribers - * Video views: 24,468 - * Publish date: March 3rd - * [Hashoshi](https://www.youtube.com/watch?v=jVjcCjfGOxU) - * YouTube Followers - 116K Subscribers - * Video views: 6,218 views - * Publish date: April 20th - * [Crypto Michael](https://www.youtube.com/watch?v=xTUCsRs89no) - * YouTube Followers - 67K Subscribers - * Video views: 4,499 views - * Publish date: April 14th - * Delphi Digital podcasts & Brand Sponsor - * Podcast ads are just starting, clubhouse (later aired as podcast) w/ key cosmonauts soon - * Total Spent on Influencers (Twitter &YouTube): *25,462 ATOMS* - -And many more videos to be dropping soon Cosmonauts! - - -## SECTION IV - Public Relations - -Hired GFCA - work begins 2021-04-07, placements were done in April 2021: -* [Peng Zhong featured in Business Insider](https://www.businessinsider.com/crypto-investing-experts-bitcoin-price-drop-explainer-charts-data-watch-2021-4) - - Notes: world's favorite business brand — by a wide margin. With over 70 million unique visitors a month. -* [Garrette Furo featured in Finance Magnates](https://www.financemagnates.com/cryptocurrency/news/are-nfts-a-good-long-term-investment-on-ownership-long-term-viability/) - - Notes: global business news outlet that focuses on alternatives and trading industries with 553,507 unique monthly visitors. -Spend: *990 ATOM* - - -## SECTION V - MEME Competition 2021 - -Start 22nd of March (3 Total stages) -Spend total: *3915 ATOM* (Split up for each stage) -Stage 1 accepted entries for prizes (so far): 170+ - - Total valid entries: 2000+ - - Cosmonaut Telegram channel growth: 700+ new people in 2 weeks (organic) - - Cosmonaut Twitter channel growth: 400+ new people in 2 weeks (organic) -[MEME Live tracker](https://docs.google.com/spreadsheets/d/1w8ry3-SxIRuEjMT1PoES8H19CsRT1aSjiKvVJEjFp_k/edit#gid=0) -[Competition outline](https://twitter.com/ATOMCosmonauts/status/1373952259013349376?s=20) - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-04-prop34-continuation/proposal.json b/docs/docs/governance/proposals/2021-04-prop34-continuation/proposal.json deleted file mode 100644 index dd3d5de98f7..00000000000 --- a/docs/docs/governance/proposals/2021-04-prop34-continuation/proposal.json +++ /dev/null @@ -1,4 +0,0 @@ -{ - "title": "Cosmos Stargate Hub Upgrade Proposal 2: Time to Upgrade.", - "description": "The Cosmos community approved Proposal 34 on 2021-01-20 allocating 129,208 ATOM to implement a comprehensive ATOM marketing plan executed in collaboration with key community stakeholders. Proposal 46 is requesting an extension of the time allowed to spend the approved budget and allocate existing funds for additional ATOM-focused priorities.\n Proposal details can be found on github: https://github.com/cosmos/governance/pull/22" -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/README.md b/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/README.md deleted file mode 100644 index a2726592585..00000000000 --- a/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/README.md +++ /dev/null @@ -1,192 +0,0 @@ ---- -title: Signaling Proposal - Deployment of Gravity Bridge on the Cosmos Hub ---- - - - -![Gravity Bridge](https://raw.githubusercontent.com/althea-net/cosmos-gravity-bridge/main/gravity-bridge.svg) - -## Summary - -This proposal is a Request For Comment from the ATOM community regarding the activation of the Gravity Bridge module onto the Cosmos Hub. - -By voting YES to this proposal, you will signal that you approve of having the Gravity Ethereum <-> Cosmos bridge deployed onto the Cosmos Hub. - -## Vision - -Gravity as an Ethereum-Cosmos bridge is designed for the Cosmos Hub to pull as much value as possible into the orbits of Cosmos via a direct and decentralized bridge. Gravity will be able to bring ERC20 assets from Ethereum into Cosmos, as well as Cosmos assets to Ethereum ERC20 representations. ATOM, and any other asset in the Cosmos ecosystem, will be able to trade on Uniswap and other Ethereum AMMs, and interact with Ethereum DeFi like any ERC20 token. As well, Cosmos Hub users can use the Gravity DEX to trade between ERC20 assets and tokens that are transferred using IBC. This will bring a tremendous amount of liquidity and utility to these multi-chain assets. - -## Cosmos, Ethereum, and Gravity - -Gravity is a secure and highly efficient bridge between EVM and Cosmos SDK-based blockchains. At a high-level, Gravity enables token transfers from Ethereum to the Cosmos Hub and back again by locking tokens on the Ethereum side and minting equivalent tokens on the Cosmos side. - -Gravity is completely non-custodial. Control of the bridge mirrors the active validator set on the Cosmos SDK-based chain, and validator stake on Cosmos can be slashed for misbehavior involving the Gravity bridge. - -The Gravity Ethereum contract is highly optimized, utilizing batches to dramatically reduce the cost of Cosmos -> Ethereum transfers. Sending funds from Cosmos back to Ethereum can be up to 50% less costly than a normal ERC20 send. - -## How do validators support the Gravity Bridge? - -Cosmos Hub validators will run three key software components of the Gravity bridge: - -- The Gravity bridge module, integrated into gaiad (the binary that runs the Cosmos Hub) -- The Gravity bridge Orchestrator -- A Geth light client or any Ethereum full node implementing the JSON-rpc standard - -### Cosmos to Ethereum: - -To send transactions from Cosmos to Ethereum, the Gravity Bridge module of a validator's Gaia instance first packages the transaction data, and makes it available on an endpoint. The Orchestrator then signs this data with the validator’s Ethereum key, and submits it as a message to the Ethereum network. The Ethereum signature of each Cosmos validator needs to be assembled and submitted to the Ethereum chain by relayers. - -Validators may be slashed if they fail to submit Ethereum signatures within 10,000 blocks (about twelve to fourteen hours) of their creation. - -The current liveness rules require a validator to sign at least 500 of the last 10,000 blocks (about twelve to fourteen hours) - -Validators may also be slashed if they sign a message with their Ethereum key that was not created by the Gravity bridge module. - -Gravity bridge has no other slashing conditions. - -### Ethereum to Cosmos: - -The Orchestrator also monitors the Ethereum chain, submitting events that occur on Ethereum to Cosmos as messages. When more than 2/3 of the active voting power has sent a message observing the same Ethereum event, the Gravity module will take action. - -This oracle action will not be incentivized, nor will it be enforced with slashing. If validators making up more than 33% of the staked tokens do not participate in the oracle, new deposits and withdrawals will not be processed until those validators resume their oracle obligations. - -The oracle was designed to adhere to the Cosmos Hub validator security model without slashing conditions to ensure that a consensus failure on Ethereum does not affect operation of the Cosmos chain. - -### Slashing Conditions Spec - -https://github.com/cosmos/gravity-bridge/blob/main/spec/slashing-spec.md - -## How does it work? - -Gravity consists of 4 parts: - -- An Ethereum contract called Gravity.sol -- The Gravity Cosmos module of Gaia -- The orchestrator program which is run by Cosmos validators alongside the Gravity module -- A market of relayers, who compete to submit transactions to Ethereum - -### Gravity.sol - -The Gravity Ethereum contract is a highly compact and efficient representation of weighted powers voting on Ethereum. It contains an Etheruem key from each Cosmos validator, as well as their voting power. This signer set is continuously updated as validation power changes on Cosmos, ensuring that it matches the current Cosmos validator set. - -Sending tokens, or updating the validator set, contained in Gravity.sol requires more than 66% of the total voting power to approve the action. In this way Gravity.sol mirrors Tendermint consensus on the Cosmos chain as closely as possible on Ethereum. - -### Gravity Cosmos Module - -The Gravity module governs and coordinates the bridge. Generating messages for the validators to sign with their Ethereum keys and providing these signatures to relayers who assemble and submit them to the Ethereum chain. - -### Orchestrator - -The Gravity bridge orchestrator performs all the external tasks the Gravity bridge requires for validators, which includes submission of signatures and submission of Ethereum events. - -While the Gravity module concerns itself with the correctness and consensus state of the bridge, the Orchestrator is responsible for locating and creating the correct inputs. - -### Market of Relayers - -Relayers are an unpermissioned role that observes the Cosmos chain for messages ready to be submitted to Ethereum. - -The relayer then packages the validators signatures into an Ethereum transaction and submits that transaction to the Ethereum blockchain. All rewards in the Gravity bridge design are paid to msg.sender on Ethereum. This means that relayers do not require any balance on the Cosmos side and can immediately liquidate their earnings into ETH while continuing to relay newer messages. - -## Security assumptions - -The Gravity bridge is designed with the assumption that the total amount of funds in Gravity.sol is less than the value of the validator set’s total staked tokens. - -If this assumption does not hold true, it would be more profitable for validators to steal the funds in the bridge and simply lose their stake to slashing. - -There is no automated enforcement of this assumption. It is up to the $ATOM holders to take action if the amount deposited in the bridge exceeds the total value of all stake on the hub. - -It should be noted that this condition is not unique to the Gravity bridge. The same dynamic exists for any IBC connection, and even exists in scenarios other than cross-chain communication. For example, in a hypothetical blockchain keeping domain name records, this same vulnerability would exist if the potential profit from exploiting the domain name system was greater than the value of the validator set’s total staked tokens. - -## Ongoing work - -The Gravity Bridge has been continuously tested throughout Q1/Q2 2021 by multiple ongoing test nets with a diverse group of validators. - -### Testing - -The Althea team is committed to playing a long-term role in upgrading, documenting, and supporting Gravity over the coming years. -The Gravity bridge is currently live and running in a testnet, which validators can join by following the instructions [here](https://github.com/althea-net/althea-chain/blob/main/docs/althea/testnet-2.md) - -### Audit: - -The Gravity bridge module is currently undergoing an audit with Informal Systems estimated to be completed by the end of July, 2021. - -Phase one of the audit has been completed, which resulted in the addition of evidence based slashing and several other minor design fixes. - -The phase two design audit will be completed by the end of June. To be followed by phrase three, an implementation audit to be completed by the end of July. - -### Conclusion: - -With this proposal, the Althea team, together with Cosmos ecosystem partners, will expedite the development of the Gravity Bridge with an incentivized testnet and launch in Q3 2021. Althea will be closely shepherding the Gravity Bridge throughout all phases related to the testing, audit, and implementation process on the Cosmos Hub. - -## Proposers - -_The Althea Gravity bridge team._ - -Deborah Simpiler, Justin Kilpatrick and, Jehan Tremback - -We’d like to share praise and thank you for contributions from the following teams! - -Interchain Foundation - -All in Bits/Tendermint - -Sommelier, Informal, Injective, Confio - -_Gravity Readiness Committee:_ - -Justin Kilpatrick and Jehan Tremback, Althea - -Zarko Milosevic, Informal Systems - -Zaki Manian, Sommelier/Iqlusion - -## Governance Votes - -The following items summarize the voting options and what it means for this proposal. - -- **YES**: You agree that Gravity Bridge should be deployed to the Cosmos Hub. -- **NO**: You disapprove of deploying Gravity bridge on the Cosmos Hub in its current form (please indicate in the [Cosmos Forum](https://forum.cosmos.network/) why this is the case). -- **NO WITH VETO**: You are strongly opposed to the deployment of Gravity bridge on the Cosmos Hub and will exit the network if this occurred. -- **ABSTAIN**: You are impartial to the outcome of the proposal. - -## Appendix - -### FAQ - -### Is running the Gravity Module difficult for Cosmos Validators? - -Soliciting feedback from dozens of Cosmos hub validators and over 100 test net participants, we found that running the Gravity module is not a difficult task or undue burden on Cosmos validators. - -### Is the Gravity bridge secure? - -The Gravity bridge is undergoing an audit by Informal Systems. It will then be up to ATOM holders to interpret the results of the code audit and weigh implementation risks in another governance proposal before deployment. Fundamentally, the design of the Gravity Bridge means that its security is directly represented by the security of the validator set on Cosmos Hub. On the Cosmos side, the Gravity Bridge security design adheres to the Cosmos network's ideal of safety over liveness assured by 2/3+ validator voting power, but without sacrificing safety or liveness due to issues that may rarely arise with Ethereum. - -### Are slashing conditions a problem for validators? - -Gravity Bridge slashing conditions closely mirror the slashing conditions which validators are already subject to. - -- Uptime: Validators on Cosmos currently must keep their validator software running at all times, or risk slashing. Gravity adds an additional binary which must be run, which is low in difficulty, resource usage, and operational requirements. - -- Equivocation: Validators on Cosmos are subject to slashing if they sign two blocks at the same height. It is possible for this to happen through accidental misconfiguration. Gravity adds an additional item which must not be signed, which are the fraudulent bridge transactions that never existed on Cosmos. It is not possible for this to happen by accident, so this slashing condition is much less of a risk than the Hub’s existing slashing conditions. - -### What about peg zones? - -The concept of a "peg zone" has been around in Cosmos for a while. This is a separate chain which runs the Gravity Bridge and connects to Ethereum or another blockchain. We believe that running Gravity Bridge on the Cosmos Hub and connecting directly is the superior solution. First, let's look at what different forms peg zones could take. - -1. The most likely type of peg zone is what will result if this proposal does not pass. There are at least 5 Cosmos SDK chains who will be using the Gravity Bridge module to connect to Ethereum. There will be no official way to bridge Ethereum assets into the Cosmos ecosystem. Instead there will be many dueling representations of Ethereum assets. It goes without saying that this will confuse Cosmos users. If one of these peg zones gains the upper hand and becomes dominant, the Cosmos Hub will miss out on all the transaction fees that it generates. - -2. It would also be possible to establish an official peg zone, and airdrop its staking token 1:1 to current Atom holders. This would at least allow the Cosmos Hub stakeholders to keep the economic benefit of activity on the peg zone. However, this is capital inefficient. A dollar staked on this peg zone would not be staked on the hub and vice versa. Splitting stake between these two important chains would make both weaker. Cosmos users will also need to choose whether to put value into Atom or put value into the peg zone token, resulting in less value in Atom. - -3. Shared security has been talked about for a long time in Cosmos, but it is not yet in production. Establishing a peg zone with shared security with the Cosmos Hub would allow the same validator set to validate both chains, and put the same Atoms at stake to secure each of them. This would avoid the issues of scenarios 1 and 2 above. However, we cannot afford to wait. Many other PoS blockchains already have Ethereum bridges and Cosmos needs to continue innovating to stay relevant. - -This is easier to both design and debug, and is ideal for high-value chains like the Hub. - -### Why not use IBC to create a bridge to Ethereum? - -Ethereum as it currently exists (ETH1) fundamentally can not implement IBC. It may be possible in the future to create an IBC bridge with ETH2. - -Implementing IBC for ETH2 require significant development effort and coordination with the Ethereum team as well as the completion and deployment of ETH2, which is on an uncertain timeline. - -Gravity bridge is a design that can be deployed in the forseeable future and will continue to function so long as ETH1 compatibility is maintained. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/proposal.json b/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/proposal.json deleted file mode 100644 index 8d7154bc9e7..00000000000 --- a/docs/docs/governance/proposals/2021-05-gravity-bridge-deployment/proposal.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "title": "Signaling Proposal - Deployment of Gravity Bridge on the Cosmos Hub", - "description": "This proposal is a Request For Comment from the ATOM community regarding the activation of the Gravity Bridge module onto the Cosmos Hub.\n By voting YES to this proposal, you will signal that you approve of having the Gravity Ethereum <> Cosmos bridge deployed onto the Cosmos Hub. \n More details can be found in the long form proposal here: https://github.com/cosmos/governance/pull/27 and discussion here: https://forum.cosmos.network/t/signaling-proposal-deployment-of-gravity-bridge-on-the-cosmos-hub", - "deposit": [ - { - "denom": "uatom", - "amount": "1000000" - } - ] -} diff --git a/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/README.md b/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/README.md deleted file mode 100644 index 8419fa537c8..00000000000 --- a/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/README.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: ATOM 🤝 Osmosis - Allocate Community Pool to ATOM Liquidity Incentives ---- - - - -ATOMs should be the base money of Cosmos, just like ETH is the base money of the entire Ethereum DeFi ecosystem. ATOM is currently well positioned to play this role among Cosmos assets because it has the highest market cap, most liquidity, largest brand, and many integrations with fiat onramps. ATOM is the gateway to Cosmos. - -In the Cosmos Hub Port City vision, ATOMs are pitched as equity in the Cosmos Hub. However, this alone is insufficient to establish ATOM as the base currency of the Cosmos ecosystem as a whole. Instead, the ATOM community must work to actively promote the use of ATOMs throughout the Cosmos ecosystem, rather than passively relying on the Hub's reputation to create ATOM's value. - -In order to cement the role of ATOMs in Cosmos DeFi, the Cosmos Hub should leverage its community pool to help align incentives with other protocols within the Cosmos ecosystem. We propose beginning this initiative by using the community pool ATOMs to incentivize deep ATOM base pair liquidity pools on the Osmosis Network. - -Osmosis is the first IBC-enabled DeFi application. Within its 3 weeks of existence, it has already 100x’d the number of IBC transactions ever created, demonstrating the power of IBC and the ability of the Cosmos SDK to bootstrap DeFi protocols with $100M+ TVL in a short period of time. Since its announcement Osmosis has helped bring renewed attention and interest to Cosmos from the crypto community at large and kickstarted the era of Cosmos DeFi. - -Osmosis has already helped in establishing ATOM as the Schelling Point of the Cosmos ecosystem. The genesis distribution of OSMO was primarily based on an airdrop to ATOM holders specifically, acknowledging the importance of ATOM to all future projects within the Cosmos. Furthermore, the Osmosis LP rewards currently incentivize ATOMs to be one of the main base pairs of the platform. - -Osmosis has the ability to incentivize AMM liquidity, a feature not available on any other IBC-enabled DEX. Osmosis already uses its own native OSMO liquidity rewards to incentivize ATOMs to be one of the main base pairs, leading to ~2.2 million ATOMs already providing liquidity on the platform. - -In addition to these native OSMO LP Rewards, the platform also includes a feature called “external incentives” that allows anyone to permissionlessly add additional incentives in any token to the LPs of any AMM pools they wish. You can read more about this mechanism here: https://medium.com/osmosis/osmosis-liquidity-mining-101-2fa58d0e9d4d#f413 . Pools containing Cosmos assets such as AKT and XPRT are already planned to receive incentives from their respective community pools and/or foundations. - -We propose the Cosmos Hub dedicate 100,000 ATOMs from its Community Pool to be allocated towards liquidity incentives on Osmosis over the next 3 months. This community fund proposal will transfer 100,000 ATOMs to a multisig group who will then allocate the ATOMs to bonded liquidity gauges on Osmosis on a biweekly basis, according to direction given by Cosmos Hub governance. For simplicity, we propose setting the liquidity incentives to initially point to Osmosis Pool #1, the ATOM/OSMO pool, which is the pool with by far the highest TVL and Volume. Cosmos Hub governance can then use Text Proposals to further direct the multisig members to reallocate incentives to new pools. - -The multisig will consist of a 2/3 key holder set consisting of the following individuals whom have all agreed to participate in this process shall this proposal pass: - -- Zaki Manian -- Federico Kunze -- Marko Baricevic - -This is one small step for the Hub, but one giant leap for ATOM-aligned. - - \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/proposal.json b/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/proposal.json deleted file mode 100644 index b89c88d7b42..00000000000 --- a/docs/docs/governance/proposals/2021-07-atom-liquidity-incentives/proposal.json +++ /dev/null @@ -1,7 +0,0 @@ -{ - "title": "ATOM 🤝 Osmosis: Allocate Community Pool to ATOM Liquidity Incentives", - "description": "ATOMs should be the base money of Cosmos, just like ETH is the base money of the entire Ethereum DeFi ecosystem. ATOM is currently well positioned to play this role among Cosmos assets because it has the highest market cap, most liquidity, largest brand, and many integrations with fiat onramps. ATOM is the gateway to Cosmos.\n\nIn the Cosmos Hub Port City vision, ATOMs are pitched as equity in the Cosmos Hub. However, this alone is insufficient to establish ATOM as the base currency of the Cosmos ecosystem as a whole. Instead, the ATOM community must work to actively promote the use of ATOMs throughout the Cosmos ecosystem, rather than passively relying on the Hub's reputation to create ATOM's value.\n\nIn order to cement the role of ATOMs in Cosmos DeFi, the Cosmos Hub should leverage its community pool to help align incentives with other protocols within the Cosmos ecosystem. We propose beginning this initiative by using the community pool ATOMs to incentivize deep ATOM base pair liquidity pools on the Osmosis Network.\n\nOsmosis is the first IBC-enabled DeFi application. Within its 3 weeks of existence, it has already 100x’d the number of IBC transactions ever created, demonstrating the power of IBC and the ability of the Cosmos SDK to bootstrap DeFi protocols with $100M+ TVL in a short period of time. Since its announcement Osmosis has helped bring renewed attention and interest to Cosmos from the crypto community at large and kickstarted the era of Cosmos DeFi.\n\nOsmosis has already helped in establishing ATOM as the Schelling Point of the Cosmos ecosystem. The genesis distribution of OSMO was primarily based on an airdrop to ATOM holders specifically, acknowledging the importance of ATOM to all future projects within the Cosmos. Furthermore, the Osmosis LP rewards currently incentivize ATOMs to be one of the main base pairs of the platform.\n\nOsmosis has the ability to incentivize AMM liquidity, a feature not available on any other IBC-enabled DEX. Osmosis already uses its own native OSMO liquidity rewards to incentivize ATOMs to be one of the main base pairs, leading to ~2.2 million ATOMs already providing liquidity on the platform.\n\nIn addition to these native OSMO LP Rewards, the platform also includes a feature called “external incentives” that allows anyone to permissionlessly add additional incentives in any token to the LPs of any AMM pools they wish. You can read more about this mechanism here: https://medium.com/osmosis/osmosis-liquidity-mining-101-2fa58d0e9d4d#f413 . Pools containing Cosmos assets such as AKT and XPRT are already planned to receive incentives from their respective community pools and/or foundations.\n\nWe propose the Cosmos Hub dedicate 100,000 ATOMs from its Community Pool to be allocated towards liquidity incentives on Osmosis over the next 3 months. This community fund proposal will transfer 100,000 ATOMs to a multisig group who will then allocate the ATOMs to bonded liquidity gauges on Osmosis on a biweekly basis, according to direction given by Cosmos Hub governance. For simplicity, we propose setting the liquidity incentives to initially point to Osmosis Pool #1, the ATOM/OSMO pool, which is the pool with by far the highest TVL and Volume. Cosmos Hub governance can then use Text Proposals to further direct the multisig members to reallocate incentives to new pools.\n\nThe multisig will consist of a 2/3 key holder set consisting of the following individuals whom have all agreed to participate in this process shall this proposal pass:\n\n- Zaki Manian\n- Federico Kunze\n- Marko Baricevic\n\nThis is one small step for the Hub, but one giant leap for ATOM-aligned.\n", - "recipient": "cosmos157n0d38vwn5dvh64rc39q3lyqez0a689g45rkc", - "amount": "100000000000uatom", - "deposit": "64000000uatom" -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/2021-09-hub-ibc-router/README.md b/docs/docs/governance/proposals/2021-09-hub-ibc-router/README.md deleted file mode 100644 index 277f97b3c3f..00000000000 --- a/docs/docs/governance/proposals/2021-09-hub-ibc-router/README.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: Make the Cosmos Hub the IBC Router ---- - - - -The following is a selection from the [Cosmos Whitepaper](https://v1.cosmos.network/resources/whitepaper): - -```sh -The Cosmos Hub connects to many other blockchains (or zones) via a novel inter-blockchain communication protocol. The Cosmos Hub tracks numerous token types and keeps record of the total number of tokens in each connected zone. Tokens can be transferred from one zone to another securely and quickly without the need for a liquid exchange between zones, because all inter-zone coin transfers go through the Cosmos Hub. - -... - -Any of the zones can themselves be hubs to form an acyclic graph, but for the sake of clarity we will only describe the simple configuration where there is only one hub, and many non-hub zones. -``` - -The Hub has long been envisioned as a central point in the IBC architecture. In the battle to build and ship IBC this central vision has remained unchanged, but with so much focus on the need to build out other zones with real economies to support this network (the CosmosSDK is the result of this effort), the idea of the hub as an Interchain Router hasn't been discussed in a serious context for quite a while. - -This is understandable: Cosmos needed so many other pieces to come together before the Hub had a chance to even start performing this function. Those other zones have been created, they each have products and economies. The bootstrapping era of IBC is well underway. - -These new zones joining are noticing a problem: they need to maintain a large amount of infrastructure (archive nodes and relayers for each counterparty chain) to connect with all the chains in the ecosystem, a number that is continuing to increase quickly. - -Luckly this problem has been anticipated and IBC architected to accomodate multi-hop transactions. However, a packet forwarding/routing feature was not in the initial IBC release. This proposal aims to fix this for the Hub. - -This is a proposal to include a new feature to IBC on the Hub that allows for multi-hop packet routing for ICS20 transfers. By appending an intermediate address, and the port/channel identifiers for the final destination, clients will be able to outline more than one transfer at a time. The following example shows routing from Terra to Osmosis through the Hub: - -```json -// Packet sent from Terra to the hub, note the format of the forwaring info -// {intermediate_refund_address}|{foward_port}/{forward_channel}:{final_destination_address} -{ - "denom": "uluna", - "amount": "100000000", - "sender": "terra15gwkyepfc6xgca5t5zefzwy42uts8l2m4g40k6", - "receiver": "cosmos1vzxkv3lxccnttr9rs0002s93sgw72h7ghukuhs|transfer/channel-141:osmo1vzxkv3lxccnttr9rs0002s93sgw72h7gl89vpz", -} - -// When OnRecvPacket on the hub is called, this packet will be modified for fowarding to transfer/channel-141. -// Notice that all fields execept amount are modified as follows: -{ - "denom": "ibc/FEE3FB19682DAAAB02A0328A2B84A80E7DDFE5BA48F7D2C8C30AAC649B8DD519", - "amount": "100000000", - "sender": "cosmos1vzxkv3lxccnttr9rs0002s93sgw72h7ghukuhs", - "receiver": "osmo1vzxkv3lxccnttr9rs0002s93sgw72h7gl89vpz", -} -``` - -Strangelove Ventures has delivered an [IBC Middleware module](https://github.com/cosmos/ibc-go/pull/373) that will allow the hub to play the role of IBC Router that was always envisioned for it. Passing of this propsal will begin the era of the Hub offering interchain services to other chains and profiting from those relationships. - -To pay the hub validators and stakers, this proposal implements a governance configurable fee (which we propose should be initially set to 0.0 to encourage adoption) that will be taken out of each packet and given to the community pool. The community pool will then periodically trade these fees for ATOM and distribute them to staked holders. The exact distribution method of these fees is left TBD in this proposal as it is not initially required and can be implemented in a future governance proposal. One way to do this would be using the [Groups module](https://docs.cosmos.network/main/architecture/adr-042-group-module.html), Community spend proposals and the Gravity DEX. - -A vote YES on this proposal indicates that this feature should be included in the next hub upgrade. We (as the Hub) believe that time is critical right now and we cannot wait to begin providing this service to other chains. A NO vote indicates that this shouldn't be included in the next upgrade. - diff --git a/docs/docs/governance/proposals/2021-09-hub-ibc-router/proposal.json b/docs/docs/governance/proposals/2021-09-hub-ibc-router/proposal.json deleted file mode 100644 index c4826615002..00000000000 --- a/docs/docs/governance/proposals/2021-09-hub-ibc-router/proposal.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "title": "⚛️ IBC Add Router to Hub ⚛️", - "description": "The Hub has long been envisioned as a central point in the IBC architecture. In the battle to build and ship IBC this central vision has remained unchanged, but with so much focus on the need to build out other zones with real economies to support this network (the CosmosSDK is the result of this effort), the idea of the hub as an Interchain Router hasn't been discussed in a serious context for quite a while.\n\nThis is understandable: Cosmos needed so many other pieces to come together before the Hub had a chance to even start performing this function. Those other zones have been created, they each have products and economies. The bootstrapping era of IBC is well underway.\n\nThese new zones joining are noticing a problem: they need to maintain a large amount of infrastructure (archive nodes and relayers for each counterparty chain) to connect with all the chains in the ecosystem, a number that is continuing to increase quickly.\n\nLuckly this problem has been anticipated and IBC architected to accomodate multi-hop transactions. However, a packet forwarding/routing feature was not in the initial IBC release. This proposal aims to fix this for the Hub.\n\nThis is a proposal to include a new feature to IBC on the Hub that allows for multi-hop packet routing for ICS20 transfers. By appending an intermediate address, and the port/channel identifiers for the final destination, clients will be able to outline more than one transfer at a time.\n\nStrangelove Ventures has delivered an [IBC Middleware module](https: //github.com/cosmos/ibc-go/pull/373) that will allow the hub to play the role of IBC Router that was always envisioned for it. Passing of this propsal will begin the era of the Hub offering interchain services to other chains and profiting from those relationships.\n\nTo pay the hub validators and stakers, this proposal implements a governance configurable fee (which we propose should be initially set to 0.0 to encourage adoption) that will be taken out of each packet and given to the community pool. The community pool will then periodically trade these fees for ATOM and distribute them to staked holders. The exact distribution method of these fees is left TBD in this proposal as it is not initially required and can be implemented in a future governance proposal. One way to do this would be using the [Groups module](https: //docs.cosmos.network/v0.45/architecture/adr-042-group-module.html), Community spend proposals and the Gravity DEX.\n\nA vote YES on this proposal indicates that this feature should be included in the next hub upgrade. We (as the Hub) believe that time is critical right now and we cannot wait to begin providing this service to other chains. A NO vote indicates that this shouldn't be included in the next upgrade.\n\n[Full Proposal text and additional links available here](https://github.com/strangelove-ventures/governance/blob/master/proposals/2021-09-hub-ibc-router/README.md", - "deposit": "64000000uatom" -} diff --git a/docs/docs/governance/proposals/README.md b/docs/docs/governance/proposals/README.md deleted file mode 100644 index 2e668f4010b..00000000000 --- a/docs/docs/governance/proposals/README.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Proposals -order: 1 -parent: - order: 8 ---- - -# Proposals - -A historical record of past proposals. diff --git a/docs/docs/governance/proposals/_category_.json b/docs/docs/governance/proposals/_category_.json deleted file mode 100644 index d387ce6e489..00000000000 --- a/docs/docs/governance/proposals/_category_.json +++ /dev/null @@ -1,4 +0,0 @@ -{ - "label": "Proposals", - "position": 6 -} \ No newline at end of file diff --git a/docs/docs/governance/proposals/previous-proposals/README.md b/docs/docs/governance/proposals/previous-proposals/README.md deleted file mode 100644 index 9fb0aacb26f..00000000000 --- a/docs/docs/governance/proposals/previous-proposals/README.md +++ /dev/null @@ -1,209 +0,0 @@ ---- -title: Previous Proposals -order: 1 ---- - -This is a record of past proposals, including ones that weren't drafted in the governance repository. These proposals are present in the cosmoshub-4 genesis file. - -## 1 Adjustment of blocks_per_year to come aligned with actual block time - -* **Submitted:** 2019-03-20 02:41:27 -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -This governance proposal is for adjustment of blocks_per_year parameter to normalize the inflation rate and reward rate.\n ipfs link: https://ipfs.io/ipfs/QmXqEBr56xeUzFpgjsmDKMSit3iqnKaDEL4tabxPXoz9xc - -## 2 ATOM Transfer Enablement - -* **Submitted:** 2019-03-25T21:42:19.240550245Z -* **Status:** PROPOSAL_STATUS_REJECTED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -A plan is proposed to set up a testnet using the Cosmos SDK v0.34.0 release, along with mainnet conditions, plus transfer enablement and increased block size, as a testing ground. Furthermore, a path for upgrading the cosmoshub-1 chain to use the Cosmos SDK release v0.34.0, along with the necessary updates to the genesis file, at block 425000, is outlined. IPFS: https://ipfs.io/ipfs/QmaUaMjXPE6i4gJR1NakQc15TZpSqjSrXNmrS1vA5veF9W - -## 3 ATOM Transfer Enablement v2 - -* **Submitted:** 2019-04-03T10:15:22.291176064Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -A plan for enabling ATOM transfers is being proposed, which involves the release and test of Cosmos SDK v0.34.0 and a strategy for the network to accept the release and upgrade the mainnet once testing has been deemed to be successful. Read the full proposal at https://ipfs.io/ipfs/Qmam1PU39qmLBzKv3eYA3kMmSJdgR6nursGwWVjnmovpSy or formatted at https://ipfs.ink/e/Qmam1PU39qmLBzKv3eYA3kMmSJdgR6nursGwWVjnmovpSy - -## 4 Proposal for issuance of fungible tokens directly on the Cosmos Hub - -* **Submitted:** 2019-04-15T08:45:39.072577509Z -* **Status:** PROPOSAL_STATUS_REJECTED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -This proposal is a first step towards enabling fungible token issuance on the Cosmos Hub, with listing of new tokens requiring governance approval. Read the full proposal at https://github.com/validator-network/cosmoshub-proposals/blob/0d306f1fcc841a0ac6ed1171af96e6869d6754b6/issuance-proposal.md - -## 5 Expedited Cosmos Upgrade Proposal - -* **Submitted:** 2019-04-19T00:49:55.251313656Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Proposal to upgrade the Cosmos Hub at block 500,000 on April 22nd 5pm GMT. Details:https://ipfs.io/ipfs/QmS13GPNs1cRKSojete5y9RgW7wyf1sZ1BGqX3zjTGs7sX - -## 6 Don't Burn Deposits for Rejected Governance Proposals Unless Vetoed - -* **Submitted:** 2019-05-03T18:14:33.209053883Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Read here, or on https://ipfs.ink/e/QmRtR7qkeaZCpCzHDwHgJeJAZdTrbmHLxFDYXhw7RoF1ppnnThe Cosmos Hub's state machine handles spam prevention of governance proposals by means of a deposit system. A governance proposal is only considered eligible for voting by the whole validator set if a certain amount of staking token is deposited on the proposal. The intention is that the deposit will be burned if a proposal is spam or has caused a negative externality to the Cosmos community (such as wasting stakeholders’ time having to review the proposal).nnIn the current implementation of the governance module used in the Cosmos Hub, the deposit is burned if a proposal does not pass, regardless of how close the final tally result may have been. For example, if 49% of stake votes in favor of a proposal while 51% votes against it, the deposit will still be burned. This seems to be an undesirable behavior as it disincentivizes anyone from creating or depositing on a proposal that might be slightly contentious but not spam, due to fear of losing the deposit minimum (currently 512 atoms). This will especially be the case as TextProposals will be used for signaling purposes, to gauge the sentiment of staked Atom holders. Disincentivizing proposals for which the outcome is uncertain would undermine that effort.nnWe instead propose that the deposit be returned on failed votes, and that the deposit only be burned on vetoed votes. If a proposal seems to be spam or is deemed to have caused a negative externality to Cosmos communninty, voters should vote NoWithVeto on the proposal. If >33% of the stake chooses to Veto a proposal, the deposits will then be burned. However, if a proposal gets rejected without being vetoed, the deposits should be returned to the depositors. This proposal does not make any change to the current behavior for proposals that fail to meet quorum; if a proposal fails to meet quorum its deposit will be burned. - -## 7 Activate the Community Pool - -* **Submitted:** 2019-05-03T21:08:25.443199036Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Enable governance to spend funds from the community pool. Full proposal: https://ipfs.io/ipfs/QmNsVCsyRmEiep8rTQLxVNdMHm2uiZkmaSHCR6S72Y1sL1 - -## 8 Notification for Security Critical Hard Fork at Block 482100 - -* **Submitted:** 2019-05-30T19:43:02.870666885Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -As described by user @Jessysaurusrex on Cosmos Forum in https://forum.cosmos.network/t/critical-cosmossdk-security-advisory/2211, All in Bits has learned of a critical security vulnerability in the codebase for the Cosmos Hub. We deem the issue to be of high severity, as if exploited it can potentially degrade the security model of the chain's Proof of Stake system. This vulnerability CANNOT lead to the theft of Atoms or creation of Atoms out of thin air. nn All in Bits has released a source code patch, Gaia v0.34.6, that closes the exploitable code path starting at block 482100. nn The proposed upgrade code Git hash is: 80234baf91a15dd9a7df8dca38677b66b8d148c1 nn As a proof of stake, we are putting some collateral behind this legitimacy of this bug and patch and encourage others familiar with the report to do so as well. If the disclosed bug turns out to be fabricated or malicious in some way, we urge the Cosmos Hub governance to slash these Atoms by voting NoWithVeto on this proposal. nn We encourage validators and all users to upgrade their nodes to Gaia v0.34.6 before block 482100. In the absence of another public bulletin board, we request validators to please vote Yes on this proposal AFTER they have upgraded their nodes to v0.34.6, as a method of signalling the readiness of the network for the upgrade. - -## 10 Increase Max Validator Set Size to 125 - -* **Submitted:** 2019-07-01T14:09:25.508939113Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Read here, or on https://ipfs.ink/e/QmRhQycV19QiTQGLuPzPHfJwCioj1wDeHHtZvxiHegTFDd nnThis proposal supercedes proposal number 9, which contains conflicting numbers in the title and body. nnIn the Cosmos Hub, the total number of active validators is currently capped at 100, ordered by total delegated Atoms. This number was originally proposed in the Cosmos whitepaper section titled [Limitations on the Number of Validators](https://github.com/cosmos/cosmos/blob/master/WHITEPAPER.md#limitations-on-the-number-of-validators 4). This number was chosen as a relatively conservative estimate, as at the time of writing, it was unclear how many widely distributed nodes Tendermint consensus could scale to over the public internet. nnHowever, since then, we have seen empirically through the running of the Game of Stakes incentivized testnet that Tendermint Core with Gaia state machine can operate with over 180 validators at reasonable average block times of <7 seconds. The Game of Stakes results empirically show that adding validators should not delay consensus at small block sizes. At large block sizes, the time it takes for the block to gossip to all validators may increase depending on the newfound network topology. However we view this as unlikely, and if it did become a problem, it could later be solved by known improvements at the p2p layer. The other tradeoff to increasing the number of validators is that the size of commits becomes ~25% larger due to more precommits being included, increasing the network and storage costs for nodes. This can also be resolved in the future with the integration of aggregate signatures. At the time of submission of this proposal, the minimum delegation to become a top 100 validator is 30,600 Atoms, a fairly high barrier to entry for new validators looking to enter the active validator set. nnIn the Cosmos whitepaper, it states that the number of validators on the Hub will increase at a rate of 13% a year until it hits a cap of 300 validators. We propose scrapping this mechanism and instead increasing the max validators to 125 validators in the next chain upgrade with no further planned increases. Future increases to the validator set size will be originated through governance. - -## 12 Are Validators Charging 0% Commission Harmful to the Success of the Cosmos Hub? - -* **Submitted:** 2019-07-23T00:28:15.881319915Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -This governance proposal is intended to act purely as a signalling proposal. Throughout this history of the Cosmos Hub, there has been much debate about the impact that validators charging 0% commission has on the Cosmos Hub, particularly with respect to the decentralization of the Cosmos Hub and the sustainability for validator operations. nn Discussion around this topic has taken place in many places including numerous threads on the Cosmos Forum, public Telegram channels, and in-person meetups. Because this has been one of the primary discussion points in off-chain Cosmos governance discussions, we believe it is important to get a signal on the matter from the on-chain governance process of the Cosmos Hub. nn There have been past discussions on the Cosmos Forum about placing an in-protocol restriction on validators from charging 0% commission. https://forum.cosmos.network/t/governance-limit-validators-from-0-commission-fee/2182 nn This proposal is NOT proposing a protocol-enforced minimum. It is merely a signalling proposal to query the viewpoint of the bonded Atom holders as a whole. nn We encourage people to discuss the question behind this governance proposal in the associated Cosmos Hub forum post here: https://forum.cosmos.network/t/proposal-are-validators-charging-0-commission-harmful-to-the-success-of-the-cosmos-hub/2505 nn Also, for voters who believe that 0% commission rates are harmful to the network, we encourage optionally sharing your belief on what a healthy minimum commission rate for the network using the memo field of their vote transaction on this governance proposal or linking to a longer written explanation such as a Forum or blog post. nn The question on this proposal is “Are validators charging 0% commission harmful to the success of the Cosmos Hub?”. A Yes vote is stating that they ARE harmful to the network's success, and a No vote is a statement that they are NOT harmful. - -## 13 Cosmos Hub 3 Upgrade Proposal A - -* **Submitted:** 2019-07-26T18:04:10.416760069Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -This is a proposal to approve these high-level changes for a final vote for what will become Cosmos Hub 3. Please read them carefully: nhttps://github.com/cosmos/cosmos-sdk/blob/rc1/v0.36.0/CHANGELOG.mdnn-=-=-nnIf approved, and assuming that testing is successful, there will be a second proposal called Cosmos Hub 3 Upgrade Proposal B. Cosmos Hub 3 Upgrade Proposal B should specify 1) the software hash; 2) the block height state export from cosmoshub-2; 3) the genesis time; 4) instructions for generating the new genesis file.nn-=-=-nnFull proposal: nhttps://ipfs.io/ipfs/QmbXnLfx9iSDH1rVSkW5zYC8ErRZHUK4qUPfaGs4ZdHdc7n - -## 14 Cosmos Hub 3 Upgrade Proposal B - -* **Submitted:** 2019-08-23T16:16:19.814900321Z -* **Status:** PROPOSAL_STATUS_REJECTED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the Cosmos Hub 3 upgrade. A high level overview of these changes was successfully approved by the voters signalling via Cosmos Hub 3 Upgrade Proposal A (https://www.mintscan.io/cosmos/proposals/13). We are proposing to use this code https://github.com/cosmos/gaia/releases/tag/v2.0.0 to upgrade the Cosmos Hub. We are proposing to export the ledger's state at Block Height 1823000, which we expect to occur on Sunday, September 15, 2019 at or around 2:00 pm UTC. We are proposing to launch Cosmos Hub 3 at 3:57 pm UTC on Sunday, September 15, 2019. nnInstructions for migration: https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-UpgradennFull proposal: https://ipfs.io/ipfs/Qmf54mwb8cSRf316jS4by96dL91fPCabvB9V5i2Sa1hxdznn - -## 16 Cosmos Hub 3 Upgrade Proposal D - -* **Submitted:** 2019-09-05T21:32:32.253341577Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Figment Networks (https://figment.io)nn-=-=-nnThis proposal is intended to supersede flawed Cosmos Hub 3 Upgrade Proposal B (https://www.mintscan.io/cosmos/proposals/14) and Cosmos Hub 3 Upgrade Proposal C (https://www.mintscan.io/cosmos/proposals/15), regardless of their outcomes. This proposal will make both Proposal 14 and 15 void.nnThis proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the Cosmos Hub 3 upgrade. A high overview of these changes was successfully approved by the voters signalling via Cosmos Hub 3 Upgrade Proposal A (https://www.mintscan.io/cosmos/proposals/13). We are proposing to use this code https://github.com/cosmos/gaia/releases/tag/v2.0.0 to upgrade the Cosmos Hub. We are proposing to export the ledger’s state at Block Height 1,933,000, which we expect to occur on September 24, 2019 at or around 1:53 pm UTC. Please note that there will likely be a variance from this target time, due to changes in block time (https://forum.cosmos.network/t/cosmos-hub-3-upgrade-proposal-d/2675/18?u=gavin). We are proposing to launch Cosmos Hub 3 at 60 minutes after Block Height 1,933,000.nn-=-=-nnInstructions for migration: https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-UpgradenPlease note the recovery scenario in the case that the chain fails to start.nn-=-=-nnFull proposal:nhttps://ipfs.io/ipfs/QmPbSLvAgY8m7zAgSLHzKHfDtV4wx5XaGt1S1cDzqvXqJg - -## 19 Cosmos Hub 3 Upgrade Proposal E - -* **Submitted:** 2019-11-14T17:13:31.985706216Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Figment Networks (https://figment.io)nn-=-=-nnFull proposal:nhttps://ipfs.io/ipfs/QmfJyd64srJSX824WoNnF6BbvF4wvPGqVBynZeN98C7ygqnn-=-=-nn_Decision_nnWe are signalling that:nn1. The Gaia 2.0.3 implementation is aligned with the list of high-level changes approved in Cosmos Hub 3 Upgrade Proposal A.nn2. We are prepared to upgrade the Cosmos Hub to cosmoshub-3 based uponnta. Commit hash: 2f6783e298f25ff4e12cb84549777053ab88749a;ntb. The state export from cosmoshub-2 at Block Height 2902000;ntc. Genesis time: 60 minutes after the timestamp at Block Height 2902000.nn3. We are prepared to relaunch cosmoshub-2nta. In the event of:ntti. A non-trivial error in the migration procedure and/ornttii. A need for ad-hoc genesis file changesnttiii. The failure of cosmoshub-3 to produce two (2) blocks by 180 minutes after the timestamp of Block Height 2902000;ntb. Using:ntti. The starting block height: 2902000nttii. Software version: Cosmos SDK v0.34.6+ https://github.com/cosmos/cosmos-sdk/releases/tag/v0.34.10nttiii. The full data snapshot at export Block Height 2902000;ntc. And will consider the relaunch complete after cosmoshub-2 has reached consensus on Block 2902001.nn4. The upgrade will be considered complete after cosmoshub-3 has reached consensus on Block Height 2 within 120 minutes of genesis time.nn5. This proposal is void if the voting period has not concluded by Block Height 2852202.nn-=-=-nn_Context_nThis proposal follows Cosmos Hub 3 Upgrade Proposal D (https://www.mintscan.io/cosmos/proposals/16) aka Prop 16, which passed in vote, but failed in execution (https://forum.cosmos.network/t/cosmos-hub-3-upgrade-post-mortem/2772). This proposal is intended to succeed where Prop 16 failed.nnThis proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the Cosmos Hub 3 upgrade. A high level overview of these changes was successfully approved by the voters signalling via Cosmos Hub 3 Upgrade Proposal A (https://www.mintscan.io/cosmos/proposals/14). We are proposing to use this code https://github.com/cosmos/gaia/releases/tag/v2.0.3 to upgrade the Cosmos Hub.nWe are proposing to export the ledger’s state at Block Height 2,902,000, which we expect to occur on December 11, 2019 at or around 14:27 UTC assuming an average of 6.94 seconds per block. Please note that there will likely be a variance from this target time, due to deviations in block time.nnWe are proposing that the Cosmos Hub 3 genesis time be set to 60 minutes after Block Height 2,902,000.nn-=-=-nnCo-ordination in case of failure will happen in this channel: https://riot.im/app/#/room/#cosmos_validators_technical_updates:matrix.org - -## 23 Cosmos Governance Working Group - Q1 2020 - -* **Submitted:** 2020-01-15T06:51:48.001168602Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.distribution.v1beta1.CommunityPoolSpendProposal - -Cosmos Governance Working Group - Q1 2020 fundingnnCommunity-spend proposal submitted by Gavin Birch (https://twitter.com/Ether_Gavin) of Figment Networks (https://figment.io)nn-=-=-nnFull proposal: https://ipfs.io/ipfs/QmSMGEoY2dfxADPfgoAsJxjjC6hwpSNx1dXAqePiCEMCbYnn-=-=-nnAmount to spend from the community pool: 5250 ATOMsnnTimeline: Q1 2020nnDeliverables:n1. A governance working group community & chartern2. A template for community spend proposalsn3. A best-practices document for community spend proposalsn4. An educational wiki for the Cosmos Hub parametersn5. A best-practices document for parameter changesn6. Monthly governance working group community calls (three)n7. Monthly GWG articles (three)n8. One Q2 2020 GWG recommendations articlennMilestones:nBy end of Month 1, the Cosmos Governance Working Group (GWG) should have been initiated and led by Gavin Birch of Figment Networks.nBy end of Month 2, Gavin Birch is to have initiated and led GWG’s education, best practices, and Q2 recommendations.nBy end of Month 3, Gavin Birch is to have led and published initial governance education, best practices, and Q2 recommendations.nnDetailed milestones and funding:nhttps://docs.google.com/spreadsheets/d/1mFEvMSLbiHoVAYqBq8lo3qQw3KtPMEqDFz47ESf6HEg/edit?usp=sharingnnBeyond the milestones, Gavin will lead the GWG to engage in and answer governance-related questions on the Cosmos Discourse forum, Twitter, the private Cosmos VIP Telegram channel, and the Cosmos subreddit. The GWG will engage with stake-holders to lower the barriers to governance participation with the aim of empowering the Cosmos Hub’s stakeholders. The GWG will use this engagement to guide recommendations for future GWG planning.nnRead more about the our efforts to launch the Cosmos GWG here: https://figment.io/resources/introducing-the-cosmos-governance-working-group/nn-=-=-nn_Problem_nPerhaps the most difficult barrier to effective governance is that it demands one of our most valuable and scarce resources: our attention. Stakeholders may be disadvantaged by informational or resource-based asymmetries, while other entities may exploit these same asymmetries to capture value controlled by the Cosmos Hub’s governance mechanisms.nnWe’re concerned that without establishing community standards, processes, and driving decentralized delegator-based participation, the Cosmos Hub governance mechanism could be co-opted by a centralized power. As governance functionality develops, potential participants will need to understand how to assess proposals by knowing what to pay attention to.nn_Solution_nWe’re forming a focused, diverse group that’s capable of assessing and synthesizing the key parts of a proposal so that the voting community can get a fair summary of what they need to know before voting.nnOur solution is to initiate a Cosmos governance working group that develops decentralized community governance efforts alongside the Hub’s development. We will develop and document governance features and practices, and then communicate these to the broader Cosmos community.nn_Future_nAt the end of Q1, we’ll publish recommendations for the future of the Cosmos GWG, and ideally we’ll be prepared to submit a proposal based upon those recommendations for Q2 2020. We plan to continue our work in blockchain governance, regardless of whether the Hub passes our proposals.nn-=-=-nnCosmos forum: https://forum.cosmos.network/c/governancenCosmos GWG Telegram channel: https://t.me/hubgovnTwitter: https://twitter.com/CosmosGov - -## 25 CosmWasm Integration 1 - Permissions and Upgrades - -* **Submitted:** 2020-05-12T17:10:00.465282299Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.distribution.v1beta1.CommunityPoolSpendProposal - -CosmWasm Integration 1 - Permissions and UpgradesnnCommunity-spend proposal submitted by Ethan Frey (https://github.com/ethanfrey) of Confio UO (http://confio.tech/) and CosmWasm (https://www.cosmwasm.com)nn-=-=-nnFull proposal: https://ipfs.io/ipfs/QmbD3bMajQCFmtDmkuRVWhmMWVdN2sK8QP2FoFCz9cjPiCnForum Post: https://forum.cosmos.network/t/proposal-cosmwasm-on-cosmos-hub/3629nn-=-=-nnAmount to spend from the community pool: 25000 ATOMsnnTimeline: 2-4 months from approvalnnDeliverables:n1. Adding governance control to all aspects of the CosmWasm contract lifecycle to make it compatible with the hub. Allowing governance to control code upload, contract instantiation, upgrades, and destruction (if needed).n2. Adding ability to upgrade contracts along with migrations (also allowing orderly shutdowns). This controlled by a governance vote.n3. Launch a testnet with working version of this code (Cosmos SDK 0.38 or 0.39) to enable all interested parties to trial the process and provide feedback.n4. Provide sample contracts to demo on the testnet, along with some migration scenariosnnWithin 2 months, the working code and binaries should be delivered and open for public review. Within 4 months, these binaries will be used on a testnet, with sufficient staking tokens given to all active voters on the Cosmos Hub, and we will go through a few governance voting cycles to trial contract deployment and migrations (with a shorter voting cycles, eg. 3 days)nnDetailed milestones in the full proposal:nhttps://ipfs.io/ipfs/QmbD3bMajQCFmtDmkuRVWhmMWVdN2sK8QP2FoFCz9cjPiCnnBeyond the milestones, CosmWasm will enhance documentation of the platform and offer technical support on our Telegram channel.nn-=-=-nn_Problem_nWith the upcoming launch of IBC, the hub will need to adapt more rapidly to the needs of the ecosystem, while also limiting chain restarts, which may be detrimental to IBC connections. In particular support for relaying Dynamic IBC Protocols and Rented Security, using ATOMs as collateral for smaller zones, would greatly benefit from CosmWasm's flexibility.nn_Solution_nWe’re adding some key features to CosmWasm to convert it from a permissionless, immutable smart contract platform to a permissioned platform with governance control for upgrading or shutting down contracts. This is a key requirement to be able to integrate CosmWasm to the Cosmos Hub with minimal disruption.nn_Future_nWe will continue development of CosmWasm, especially adding IBC integration as well as working towards a stable 1.0 release that can be audited and safely deployed (Q3/Q4 2020).nn-=-=-nnTwitter: https://twitter.com/CosmWasmnMedium: https://medium.com/confionTelegram: https://t.me/joinchat/AkZriEhk9qcRw5A5U2MapAnWebsite: https://www.cosmwasm.comnGithub: https://github.com/CosmWasm - -## 26 Takeoff Proposal from Cyber to Cosmos - -* **Submitted:** 2020-05-21T18:00:11.292428073Z -* **Status:** PROPOSAL_STATUS_REJECTED -* **Type:** /cosmos.distribution.v1beta1.CommunityPoolSpendProposal - -cyber Congress (https://cybercongress.ai) developed Cyber (https://github.com/cybercongress/go-cyber): a software for replacing existing internet behemoth monopolies, such as Google, which exploited outdated internet protocols using the common patterns of our semantic interaction. These corps lock the information, produced by the users, from search, social and commercial knowledge graphs in private databases, and then sell this knowledge back as advertisement. They stand as an insurmountable wall between content creators and consumers extracting an overwhelming majority of the created value.nnWe propose ATOM holders to invest 10,000 ATOM from the community pool into the Takeoff of Cyber. In exchange, at the end of its donation round (https://cyber.page/gol/takeoff), and when an IBC connection will become possible, cyber Congress will transfer CYB tokens back to the community pool. Passing this proposal will transfer 10,000 ATOMs from the community pool to cyber Congress multisig (https://www.mintscan.io/account/cosmos1latzme6xf6s8tsrymuu6laf2ks2humqv2tkd9a).nnFull Proposal-Manifest text: https://ipfs.io/ipfs/QmUYDQt9tqLQJwxnUck7dQY3XmZA3tDtpFh3Hchkg7oH46nnor at https://cyber.page/gol/takeoffnnThe software we offer resembles a decentralized google (https://github.com/cybercongress):n- A protocol spec and the rationale behind itn- go-cyber: our implementation using cosmos-sdkn- cyber.page: PoC reference web interfacen- launch-kit: useful tools for launching cosmos-sdk based chainsn- cyberindex: GraphQL middleware for cybern- euler Foundation: mainnet predecessor of cyber Foundation: the DAO, which will handle all the donated ETHn- documentation and various side toolsnnCyber solves the problem of opening up the centralised semantics core of the Internet. It does so by opening up access to evergrowing semantics core taught to it by the users.nnEconomics of the protocol are built around the idea that feedback loops between the number of links and the value of the knowledge graph exist. The more usage => the bigger the knowledge graph => the more value => the better the quality of the knowledge => the more usage. Transaction fees for basic operations are replaced by lifetime bandwidth, which means usability for both, end-users and developers. You can think of Cyber as a shared ASIC for search.nnYou already see that the idea of Cyber evolves around content identifiers and its ranks. From here, welcome to Decentralized Marketing, or DeMa. You've certainly heard of DeFi. DeFi is built around a simple idea that you can use a collateral for something that will be settled based on a provided price feed. Here comes the systematic problem of DeFi: price oracles. DeMa is based on the same idea of using collateral, but the input for settlement can be information regarding the content identifier itself.nnWith the help of DeMa and IBC chains will be able to prove relevance using content identifiers and their ranks one to another. This will help to grow the IBC ecosystem, where each chain has multiple possibilities to exchange data, which is provably valued.nnCosmos was created to become the internet of blockchains. A protocol that propagates the spirit of decentralization and governed by the community. For such technology to succeed, a lot is required. One thing is a solid foundation it can build on. One virtue of such foundation is monetary flow of income that has to feed this machine for as long as it exists.nnA good question that arises is how to turn the community pool into a pool that isn’t (a) a pot of money which goes solely to network security, (b) a pool that isn’t solely a build-up of inflationary rewards and (с) has long term prosperity value (its value rises).nnThe solution to the above problem is to establish a fund, that is managed and processed collectively and consists of a diversified number of assets that can bring long term value to its stakeholders.nnThis means using the funds to support exceptional projects that are building with Tendermint and Cosmos-SDK. After all, is we want to glorify the ecosystem, we need for it to grow. How will it grow? It will have projects with a clear utility, amazing a product and provable distribution. This will attract users, developers and large stakeholders to the ecosystem. Together we already did one very successful investment decision. We all participated in cosmos fundraizer. So let us move the idea forward.nnIf this proposal is successful and stands for more demand from the public, we will open another proposal using the community pool. However, anyone can participate in Game of Links (https://cyber.page/gol/) or Takeoff https://cyber.page/gol/takeoff independently. If you have question you can ask them either on Cyber topic on Cosmos forum (https://forum.cosmos.network/t/cyber-a-decentralized-google-for-provable-and-relevant-answers) or Cyber forum (https://ai.cybercongress.ai).nnProposal results: https://www.mintscan.io/proposals/26 - -## 27 Stargate Upgrade Proposal 1 - -* **Submitted:** 2020-07-12T06:23:02.440964897Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Stargate is our name for the process of ensuring that the widely integrated public network known as the Cosmos Hub is able to execute the cosmoshub-3 -> cosmoshub-4 upgrade with the minimum disruption to its existing ecosystem. This upgrade will also realize the Internet of Blockchains vision from the Cosmos whitepaper.nIntegrations from ecosystem partners are at risk of breaking changes due to the Stargate changes. These changes drive the need for substantial resource and time requirements to ensure successful migration. Stargate represents a unique set of circumstances and is not intended to set precedent for future upgrades which are expected to be less dramatic.nThere is a widespread consensus from many Cosmos stakeholders that these changes to core software components will enhance the performance and composability of the software and the value of the Cosmos Hub in a world of many blockchains.nA Yes result on this proposal provides a clear signal that the Cosmos Hub accepts and understands the Stargate process and is prepared to approve an upgrade with proposed changes if the plan below is executed successfully.nA No result would force a reconsideration of the tradeoffs in the Alternatives section and the forming a new plan to deliver IBC.nSee the full proposal here: https://ipfs.io/ipfs/Qmbo3fF54tX3JdoHZNVLcSBrdkXLie56Vh2u29wLfs4PnW - -## 29 Genesis fund recovery proposal on behalf of fundraiser participants unable to access their ATOMs - -* **Submitted:** 2020-09-09T06:47:46.521375251Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -The purpose of this proposal is to restore access to geneis ATOMs for a subset of donors who have been active participants in our community through the last year.n The view of iqlusion is that this is an important moment for the Cosmos Hub. Stargate brings the fundraiser period to the end with delivery of IBC. This proposal resolves the open business of active members of our community who cannot access their ATOM. This is an opportunity is opporunity to bring this business to a close and setup the agenda for IBC powered innovation comming in 2021.We strongly encourage the Cosmos Community to verify the cryptographic evidence and bring these community members to full ATOM holder status.nnnFull Proposal:https://ipfs.io/ipfs/QmV6pBgDppN7X3BdVW197EUe7dpcmcdLMivPa6xxtPj3aW nThe original authors of the proposal will be available to answer questions on the Cosmos forum.nhttps://forum.cosmos.network/t/updated-genesis-atoms-recovery-request-proposal/3905 - - -## 31 Governance Split Votes - -* **Submitted:** 2020-11-23T00:53:38.508414880Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -In the Cosmos Hub governance system, each address can only cast a vote for one option (Yes/No/Abstain/NoWithVeto) which uses their full voting power behind that choice.nnThis proposal proposes an upgrade to the Cosmos Hub governance module that would allow a staker to optionally split their votes into several voting options. For example, a single address could use 70% of its voting power to vote Yes and 30% of its voting power to vote No. Clients may opt into supporting this feature, as the existing UX of voting for a single option is preserved.nnThis is beneficial because oftentimes the entity owning that address might not be a single individual. For example, a company or organization that owns an address might have different stakeholders who want to vote differently, and so it makes sense to allow them to split their voting power.nnAnother example use case is exchanges and custodians. Many custodians and exchanges custody multiple customers’ ATOMs in the same address and use this address to stake on behalf of them. However, because of this, it makes it infeasible to do 'passthrough voting' and give their customers voting rights over their tokens, if different customers have different voting preferences. With this new proposal, custodians can use split votes to accurately reflect the preferences of their customers in on-chain governance.nnThe technical architecture for this feature can be seen in ADR 037 to the Cosmos SDK: https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-037-gov-split-vote.md nnAcceptance of this governance proposal is signalling approval to adopt this feature in a future upgrade of the Cosmos Hub. - -## 32 Funding for Development of Governance Split Votes - -* **Submitted:** 2020-11-24T17:22:36.584208993Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.distribution.v1beta1.CommunityPoolSpendProposal - -Sikka is requesting 1776 ATOMs from the community pool to architect and implement the Governance Split Votes feature proposed in Cosmos Hub Proposal #31. This community fund proposal is dependent on the passing of Proposal #31 and thus should only be approved if Proposal #31 is approved. We request 1776 ATOMs, valuing each atom at $5.1 nnSikka has already begun the design of this feature and submitted it as ADR 037 to the Cosmos Hub: https://github.com/cosmos/cosmos-sdk/blob/master/docs/architecture/adr-037-gov-split-vote.md nn As past contributors to the codebase that runs the Cosmos Hub, we are familiar with the security and code quality requirements to be included in the Cosmos Hub. Sikka will implement & test this feature and will work with the maintainers of the github.com/cosmos/cosmos-sdk repo to get it merged into the x/gov module. - -## 34 Luna Mission - Funding $ATOM - -* **Submitted:** 2021-01-05T23:09:26.477112871Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.distribution.v1beta1.CommunityPoolSpendProposal - -The Cosmos Hub (ATOM) community is requesting a community pool spend amount of 129,208 ATOM in order to implement a comprehensive ATOM marketing plan that will be executed in collaboration with AiB (Tendermint). The marketing efforts will be initiated immediately upon passing of proposal #34.nn The distribution of funds will be administered by 5 community members, that have been carefully selected by the community via the Cosmos governance working group to administer the marketing plan and release funds to either AiB that will act as a liaison between Cosmos Hub community and third parties or directly to parties that will be in charge of executing the marketing plan based on a majority multisignature approval. At least 3 members will have to approve each milestone-spend for it to be released to AiB based on the expected proposal scope &completion. nn More details can be found in the long form proposal here: https://cloudflare-ipfs.com/ipfs/QmWAxtxf7fUprPVWx1jWyxSKjBNqkcbA3FG6hRps7QTu3k and https://github.com/cosmos/governance/pull/10 and https://forum.cosmos.network/t/draft-governance-proposal-for-a-community-pool-spend-proposal-33-luna-mission-funding-atom/4244/15 nn The multisig administration includes: n @johnniecosmos, @JoeDirtay, @jackzampolin (Jack Zampolin, Pylon Validator), @immasssi (SG-1 Validator), @zakimanian (Zaki Manian, Iqlusion Validator). - -## 35 Cosmos Stargate Hub Upgrade Proposal 2: Time to Upgrade. - -* **Submitted:** 2021-01-12T01:37:07.471992293Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Proposal to complete the Stargate upgrade, halt `cosmoshub-3` at 06:00 UTC on Jan 28th, export the state and start `cosmoshub-4` based on gaia 3.0.nn Gaia Commit hash: n d974b27a8caf8cad3b06fbe4678871e4b0b69a51 Proposal details can be found on n github: https://github.com/cosmos/governance/pull/5 n ipfs: https://cloudflare-ipfs.com/ipfs/QmPww2PSmkmuLLu12GGwRdu5ur1Etf9u3Nt3Z6NqB7BQP1 n sia: https://siasky.net/EAALGMzFCafvbKkQjnAieo2cA1mpxk-JLpKsiC4XxuM6eQ - -## 36 Delay of Hub Stargate Upgrade for approximately 2 weeks - -* **Submitted:** 2021-01-24T15:51:52.051468824Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -The Stargate team is recommending that the Cosmos Hub reschedule the next upgrade to a new commit hash. The new commit hash is expected to be available on Tuesday Jan 26th with a new upgrade proposal immediately after.nnThis governance proposal will signal that [proposal 35](https://www.mintscan.io/cosmos/proposals/35) will not be executed. The Hub governance will vote on the forthcoming proposal aiming for a final upgrade. The earliest target date would be February 11th. Given that Lunar New Year is on Feb 12th. The next best date is Feb 18th 06:00UTC.nnWe are recommending the delay for the following reasons.nn* Bugs have been identified in the Proposal 29 implementation. They are resolved in this pull request[Additional review of prop 29 and migration testing by zmanian · Pull Request #559 · cosmos/gaia · GitHub](https://github.com/cosmos/gaia/pull/559)n* A balance validation regression was identified during Prop 29 code review. [x/bank: balance and metadata validation by fedekunze · Pull Request #8417 · cosmos/cosmos-sdk · GitHub](https://github.com/cosmos/cosmos-sdk/pull/8417)n* The IBC Go To Market Working Group has [identified Ledger hardware wallet](https://github.com/cosmos/cosmos-sdk/issues/8266) support as a necessary feature for the initial launch of IBC on the Hub. We have an opportunity to provide this support in this upgrade. The SDK believes this can be quickly remediated in the time available with merged PRs on Monday.n* The number of Stargate related support requests from integrators has increased significantly since the governance proposal went live but some teams have already announced a period of reduced $ATOM support while they upgrade like . The additional time should minimize the disruption for $ATOM holders. Thank so much to the $IRIS team whom is fielding a similar request volume among our non-English community. - -## 37 Stargate Upgrade- Second time is a charm! - -* **Submitted:** 2021-01-28T21:07:30.044676129Z -* **Status:** PROPOSAL_STATUS_PASSED -* **Type:** /cosmos.gov.v1beta1.TextProposal - -Proposal to complete the Stargate upgrade, halt `cosmoshub-3` at 06:00 UTC on Feb 18th, export the state and start `cosmoshub-4` based on gaia 4.0.nn Gaia Commit hash: n a279d091c6f66f8a91c87943139ebaecdd84f689 Proposal details can be found on n github: https://github.com/cosmos/governance/pull/13 n Rendered: https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/QmYn2SxCMYk5SWs5GMcXdbXR8wMCCXRmCyW19SFyzSeZp1 n ipfs: https://cloudflare-ipfs.com/ipfs/QmYn2SxCMYk5SWs5GMcXdbXR8wMCCXRmCyW19SFyzSeZp1 n sia: https://siasky.net/EACAsPcUjpTEpQlG9_nRI1OR07gNeRiudfEWAvKnf0tj_Q n - - diff --git a/docs/docs/governance/proposals/proposal-template.json b/docs/docs/governance/proposals/proposal-template.json deleted file mode 100644 index ea1cc88d094..00000000000 --- a/docs/docs/governance/proposals/proposal-template.json +++ /dev/null @@ -1,10 +0,0 @@ -{ - "title": "", - "description": "", - "deposit": [ - { - "denom": "uatom", - "amount": "" - } - ] -} diff --git a/docs/docs/governance/proposals/proposal-template.md b/docs/docs/governance/proposals/proposal-template.md deleted file mode 100644 index 765067dabe5..00000000000 --- a/docs/docs/governance/proposals/proposal-template.md +++ /dev/null @@ -1,42 +0,0 @@ -# [Proposal][Draft] Proposal Title - -## Changelog - -- {date}: {changelog} - -## Authors and Credit - -{Name}: {link e.g., github, discord, twitter} - -## Status - -{DRAFT | PROPOSED} - -> Use DRAFT if the Governance Proposal is in a draft stage or PROPOSED if it's in review. You can read more about governance proposal stages [here](../best-practices.md). - -## Proposal - -> A short (~200 word) description of the governance proposal being considered. - -## Context - -> A complete, yet brief account of the current situation the proposal aims to address. It should clearly explain the motivation, goals, and expected outcomes of the proposal as well as how the proposal addresses the situation better than other options. - -## Governance Votes - -The following items summarize the voting options and what it means for this proposal. - -- **YES**: You approve the {type} proposal to...{one sentence summary}. -- **NO**: You disapprove of the proposal in its current form. The NO vote can be a request for improvements or adjustments, please indicate them in the relevant topic in the [Cosmos forum](https://forum.cosmos.network/). You agree that this proposal's motivation is valuable and that the team should create a follow-up proposal once the amendments are included. -- **NO (VETO)**: You veto the entire motivation for the proposal, are strongly opposed to its implementation, and will exit the network if passed. You are signalling the proposers should not create a follow-up proposal. -- **ABSTAIN**: You are impartial to the outcome of the proposal. - -> State what voting for each option means in terms of this proposal. - -## Conclusion - - - -## References - -- {reference link} diff --git a/docs/docs/governance/state-of-cosmos-governance-2021.md b/docs/docs/governance/state-of-cosmos-governance-2021.md deleted file mode 100644 index 8441b5f72f8..00000000000 --- a/docs/docs/governance/state-of-cosmos-governance-2021.md +++ /dev/null @@ -1,360 +0,0 @@ ---- -title: State of Cosmos Governance 2021 -order: 9 ---- - - - -> Governance and decision-making processes within the Cosmos ecosystem as of August 2021. This particular document serves as a snapshot of the process at this moment in time and parts of it may be out of date or deprecated in the future. - -## Cosmos View of Governance - -The Cosmos ecosystem emphasizes governance mechanisms in order to achieve the vision of an ecosystem of interoperable blockchains supported by interchain infrastructure and services on the Cosmos Hub and beyond. The intent is that Cosmos Hub is operated by the community of code development teams supported by the Interchain Foundation, validators and ATOM token holders as a form of distributed organization. - -Cosmos Hub has a [Governance (x/gov) module](https://docs.cosmos.network/main/modules/gov/) for coordinating various changes to the blockchain through parameters, upgrades and proposals (the [white paper](https://v1.cosmos.network/resources/whitepaper) refers to text amendments to the "human-readable constitution" setting out Cosmos Hub policies). However, the ecosystem also has additional on- and off- chain processes that exist to set technical direction and inculcate social norms. - -Reviewing existing governance documentation and discussion, a few key themes surfaced: - -### Emphasis on Self-governance and Sovereignty - -On-chain governance standardizes forms of coordination but leaves many governance decisions to each application-specific blockchain or zone. Sunny Aggarwal [uses the analogy](https://blog.cosmos.network/deep-dive-how-will-ibc-create-value-for-the-cosmos-hub-eedefb83c7a0) that IBC as a form of standardization allows for "economic integration without political integration." Sunny also [talks about](https://www.youtube.com/watch?v=LApEkXJR_0M) how governance controlled by a community that shares culture and trust can "achieve greater security than economic incentives alone." For example, the Regen Network has a [governance model](https://medium.com/regen-network/community-stake-governance-model-b949bcb1eca3) that identifies multiple constituencies that require representation in governance. This allows diverse chains to exchange value while retaining the ability to self-govern. - -### Flexibility through On-chain Parameters - -Each blockchain in the Cosmos ecosystem can be tailored to a specific application or use case, as opposed to building everything on top of a general purpose chain (and as a result without a Turing complete virtual machine like Ethereum's, for example). This approach provides flexibility through allowing stakeholders to vote on live parameter changes. In addition, Cosmos ecosystem teams are working on smart contract functionality. For example, the CosmWasm team have explored [permissioned smart contracts](https://medium.com/cosmwasm/cosmwasm-launches-its-permissioned-testnet-gaiaflex-e32635232026), where on-chain governance is required to approve instantiation of smart contracts. - -### Development of Governance Processes Over Time - -The existing [governance module](https://docs.cosmos.network/main/modules/gov/) is described as a minimum viable product for the governance module, with [ideas for future improvement](https://docs.cosmos.network/main/modules/gov/05_future_improvements.html) . For example an active product team is currently aligning [groups and governance functionality](https://docs.google.com/document/d/1w-fwa8i8kkgirbn9DOFklHwcu9xO_IdbMN910ASr2oQ/edit#) will change current governance practices and open up new avenues to explore and support through on- and off- chain processes - - -## On- and off-chain Governance Structure - -### Communication - -Governance practices and decisions are communicated through different types of documents and design artefacts: - -- On-chain governance [proposals](https://cosmoscan.net/governance-stats) -- Decision records - - Cosmos Improvement Proposals ([CIPs](https://cips.cosmos.network/)) - - Cosmos SDK's [ADRs](https://docs.cosmos.network/main/architecture/) - - Tendermint's [ADRs](https://github.com/tendermint/tendermint/tree/master/docs/architecture) -- Technical standards / specifications - - Interchain Standard ([ICS](https://github.com/cosmos/ibc)) - - [RFCs](https://github.com/tendermint/spec/blob/master/rfc/README.md) -- [Opinion pieces](https://blog.cosmos.network/the-cosmos-hub-is-a-port-city-5b7f2d28debf) -- [Light papers](https://github.com/cosmos/gaia/issues/659) - -### Decision-making and Discussion Venues - -Venues involve community members to different degrees and individuals often perform multiple roles in the Cosmos ecosystem (e.g., Validator and member of Core Development Team). Because technical direction setting and development is almost always happening in the open, involvement from members in the extended community occurs organically. - -[Working group](https://github.com/cosmos/cosmos-sdk/wiki/Architecture-Design-Process#working-groups) meetings and coordinating Cosmos stakeholders occurs in semi-/open online spaces: - -- **[All in Bits Cosmos Forum](http://forum.cosmos.network/)** - - For long form discussion. Cosmos core developers have an active presence (e.g., Ethan, Zaki, Sunny) - - Cosmos Hub governance topics and proposals have a governance tag and usually get the most activity and substantive feedback, especially from validators (e.g., [direct conversations](https://forum.cosmos.network/t/proposal-are-validators-charging-0-commission-harmful-to-the-success-of-the-cosmos-hub/2505/8), ones that [spin out](https://forum.cosmos.network/t/on-the-interrelationship-between-the-security-budget-and-the-business-prospects-of-the-cosmos-network/2547) of proposals, and [meta discussions on process](https://forum.cosmos.network/t/streamline-the-gov-process/3997)) - - Developing and sharing of opinion pieces, light papers, hot takes etc., also happens on the forum (e.g., [Where I see the Cosmos at Present](https://forum.cosmos.network/t/where-i-see-cosmos-at-present/5022)) - - [Chinese language discussion](https://forum.cosmos.network/c/chinese/9) is one of the largest categories with 269 posts - - There are still some old links to [Matrix chat](https://riot.im/app/#/room/#cosmos_validators:matrix.org), which has been deprecated -- **[/r/cosmonetwork Subreddit](http://reddit.com/r/cosmosnetwork)** - - Venue primarily for ATOM holders to discuss ATOM and other ecosystem coins - - Discussion topics mostly about investing in the ecosystem and include: [investment theses](https://www.reddit.com/r/cosmosnetwork/comments/o38psh/i_think_atom_is_undervalued/), where to buy tokens, wallets to use, how to stake, and more recently, how to get involved with DeFi in the ecosystem (e.g., with Osmosis) - - Community managers use it for announcements (e.g., catdotfish) -- **[Cosmos Community Discord](https://discord.com/invite/cosmosnetwork)** - - For ecosystem cross-pollination with an active developer presence. Older Riot chats have moved here. - - `#validator-verified` channel for example discussing proposals, upgrades etc. - - Major ecosystem chains all have a presence here, cross-validator convo, artefacts like: [Citadel.one Validator Constitution](https://drive.google.com/file/d/1wDTqro208y_1q3zF6rt39QjwYkcvVd7P/view) -- **Cosmos Hub Discord (semi-private)** - - For [core development teams](https://cosmos.network/learn/faq/who-is-building-cosmos/) to have multi-team discussions that are mature - - Internal org channels (e.g., Interchain Slack) and slack-connect (private) - - For internal team coordinating, 1-1s between specific core development teams, multi-team discussions that are early stage, have private or strategic team info too early to share out -- **[Telegram (Governance Working Group)](https://t.me/hubgov)** - - For coordinating a working group that: "develops decentralized community governance efforts alongside the Hub's governance development." - - Working Group came out of [a community pool proposal](https://www.figment.io/resources/introducing-the-cosmos-governance-working-group). - - Some interest in deprecating but remains actives -- **GitHub repositories** for governance processes ([Cosmos governance](https://github.com/cosmos/governance), [Cosmos cips](https://github.com/cosmos/cips), [Cosmos ibc](https://github.com/cosmos/ibc)) - - For discussing meta aspects of governance processes, discussion and development of specific off-chain design records and technical specs, and repository for on-chain proposals - - The Cosmos governance repo is officially deprecated as of October 2021. -- **Bi-weekly Cosmos Gaia / ATOM sync call** - - For cross-team discussion on the [Gaia roadmap](https://github.com/cosmos/gaia/projects/9) -- (Informal) **Google Docs for early feedback** - - For individuals and collaborators to develop and iterative on governance ideas before proposing them formally -- **[Matrix chat](https://riot.im/app/#/room/#cosmos_validators:matrix.org)** (deprecated) - -### Roles and Stakeholders - -As mentioned above, stakeholders often perform multiple roles in the Cosmos ecosystem (e.g., both a Validator and member of the Core Development Team). As a result, visualizing the roles each stakeholder can take up in current governance can fail to reflex the overlapping roles. Within the ecosystem, decision-making power and process "ownership" has been decentralized to an extent, reflecting system goals. - -What roles can each stakeholder take up in current governance? - -**Viewer (V)** - Able to easily review previous governance decisions, see current state of governance -**Active Participant (P)** - Regularly providing input or helping to move governance decisions forward, but does not drive them or necessarily initiate -**Governance Proposer (I)** - Initiates a proposal for updating Cosmos Hub governance -**Decision Maker (DM)** - Can vote or be part of the final governance decision -**Process Owner (PO)** - Owns the creation, refinement, and execution of the governance mechanism - -| **Role** | **Cosmos Hub
On-chain** | **CIPs** | **Cosmos SDK
ADRs** | **Tendermint
RFCs** | **ICSs** | -|---|:-:|:-:|:-:|:-:|:-:| -| ATOM holders (retail and
professional) | V | | | | | | -| Hub Delegators | DM | | | | | | -| Hub Validators | DM | | | | | | -| Interchain Foundation team | DM | | | | | | -| Cosmos Core Development
teams | PO | PO | DM | P | PO | -| Cosmos SDK Core Team | DM | DM | PO | P | DM | -| Tendermint Developers | DM | DM | DM | PO | DM | -| Cosmos Integrators (wallets,
exchanges, services) | DM | P | ? | ? | ? | -| Other zones and hubs members | DM | P? | P? | P? | P? | - - -#### Role Ability to Govern - -What aspects of the Cosmos ecosystem does each role have the ability to govern? - -| **Role** | **Cosmos Hub
Blockchain
(through on-chain proposals)** | **Cosmos Hub
Community Pool (treasury)** | **Cosmos Hub On-chain
governance processes** | **Cosmos
Ecosystem Tech Decision Records, Specs, Standards Development** | **Cosmos Ecosystem
Off-chain governance processes** | -|---|:-:|:-:|:-:|:-:|:-:| -| ATOM holders (retail and
professional) | Must delegate ATOMs | Must delegate ATOMs | Must delegate ATOMs | | | -| Hub Delegators | ✔ | ✔ | ✔ | | | -| Hub Validators | ✔ | ✔ | ✔ | | | -| Interchain Foundation team | | ✔ | ✔ | | ✔ | -| Cosmos Core Development
teams | | | ✔ | ✔ | ✔ | -| Cosmos SDK Core Team | | | | ✔ | ✔ | -| Tendermint Developers | | | | ✔ | ✔ | -| Cosmos Integrators (wallets,
exchanges, services) | | | | ✔ | | -| Other zones and hubs members | | | ✔ | ✔ | ✔ | - ---- - -## Review of Governance processes - -### Cosmos Hub on-chain governance - -The Cosmos Hub has an on-chain governance mechanism, which allow ATOM token holders to: - -#### Change module parameters - -The Cosmos Hub is implemented modularly using the Cosmos SDK, where each module brings a different set of functions. Some modules have "governable" parameters, i.e., parameters that are alterable through on-chain "parameter change" governance proposals. Parameter change proposals allows token-holders to adjust the Cosmos Hub's functionality live on the blockchain, without the need for a new software release. It's interesting to note that parameters related to the governance module, i.e., x/gov module in the Cosmos SDK which implements the technical functionality of on-chain governance, is itself governable through parameter change proposals. - -Example: [Proposal 47](https://www.mintscan.io/cosmos/proposals/47) asked to lower the minimum proposal deposit amount from 512 ATOMs to 64 ATOMs. - -#### Pass text proposals - -Text proposals are used by delegators to agree to a certain strategy, plan, commitment, future upgrade, or any other statement in the form of text. Aside from having a record of the proposal outcome on the Cosmos Hub chain, a text proposal has no direct effect on the change Cosmos Hub. - -Example: [Proposal 12](https://www.mintscan.io/cosmos/proposals/12) asked if the Cosmos Hub community of validators charging 0% commission was harmful to the success of the Cosmos Hub? - -#### Spend funds from the community pool - -Cosmos Hub has a pool of ATOMs that can be spent through governance proposals. As of July 2nd, 2021 there are 645,961.01 ATOM in the community pool [according to cosmoscan](https://cosmoscan.net/). - -Example: [Proposal 45](https://www.mintscan.io/cosmos/proposals/45) asked to allow the spending of 5,000 ATOMS for the Gravity DEX Incentivized Testnet (Trading Competition) from the community pool. - -#### Pass software upgrade proposals - -A software upgrade proposal, when passed, will halt the chain until the node operator upgrades their software. If passed, the expectation is validators will update their software in accordance wi - -Example: [Proposal 51](https://www.mintscan.io/cosmos/proposals/51) asked to adopt the Gravity DEX protocol on Cosmos Hub. - -### User Story: Chain-Wide Governance - -_Reproduced from [Gov Use Cases](https://docs.google.com/document/d/1GJTTVlRU1qDzIbiwhRo-RVFq7pQ-BOjABgVpDdrpAAM/edit#heading=h.84b4lthf6mm)_ - -A community member, Alice, wants to submit an on-chain proposal to change a parameter, the average number of blocks per year, which is used to calculate the inflation rate for the chain. To do this Alice first asks in a chat forum discord for instance whether this is a good idea and something the community would like to see happen. There is some initial discussion to confirm that this is in fact something the community wants. Another community member, Bob, also offers to collaborate on the proposal. - -Alice and Bob have a zoom call and start working in a google doc to draft the proposal synchronously, after which Alice finishes the draft and Bob reviews her work. Alice then opens a pull request on the governance repo that includes the text document as well as the json message required to make the parameter proposal on chain. - -Alice solicits community feedback on the PR, sharing it to the Discord and among validators, and is asked to make some minor changes, which are completed before the PR is finalized and merged by the governance repo owner. - -Once the proposal has been finalized an IPFS hash of the README.md is added to the json. - -The proposal is then submitted on chain through the CLI and a Cosmos forum post is made to notify the community that the proposal has been submitted. Links to the forum post are then shared in various community channels and on twitter. The merits of the proposal are discussed in these respective channels and validators / ATOM holders vote. - -| **Venues** | **1
Problem Identification** | **2
Problem validation and proposal development** | **3
Review, debating pros and cons** | **4
Incorporating feedback** | **5
Initiate process** | **6
Decision finalization and adoption** | -|---|:-:|:-:|:-:|:-:|:-:|:-:| -| Cosmos Hub Discord | | ✔ | | | ✔ | | -| Gaia call | | | | | | | -| Cosmos Gov GitHub Repo | | | ✔ | ✔ | | | -| Cosmos Hub Gov WG Telegram | | | | | | | -| Discourse forum | | | ✔ | | ✔ | | -| On chain vote | | | | | | ✔ | -| Community Discord | | | | | ✔ | | -| Twitter | | | | | ✔ | | -| Other unofficial chat channels | | | | | ✔ | | -| Subreddit | | | | | ✔ | | - -### Process overview - -![Diagram of process for on-chain governance proposals](https://lh6.googleusercontent.com/FPQ176gx_-0jR5zbpImJtWx3iTnL-JJPc41hT4NUsNIYj5FziO6bsFWFn_CWV2ARr4vxm-HJi_3Fn4zowN1d2JuXB_CW2mTzJwn8L45mIPY0W_8sfjz3w3jeFr2q1NCcFVeRu7j_) - -On-chain governance on the hub is implemented in Gaia using the x/gov module in the Cosmos SDK. Every bonded token is allowed a single vote. - -Participants in the process include: - -- The proposal creator: develops the proposal, solicits feedback, submits and socializes the on-chain proposal -- Validators: vote on behalf of delegators. Voting power of validators is equivalent to total ATOMS delegated to them. There are currently 125 active validators in the validator set, updated from 100 validators through governance [proposal #10](https://cosmoscan.net/proposal/10). -- Delegators: can cast their own vote, otherwise they inherit the vote of their delegates - -### Process owners - -- Former process owners are listed in the now-deprecated [governance repo](https://github.com/cosmos/governance). - -### Process maturity - -- 37 proposals that have been voted on so far. The latest proposal as of July 2nd, 2021 is proposal ID #51 (proposals that don't meet minimum deposit don't count towards the 37) -- [Cosmoscan's governance charts](https://cosmoscan.net/governance-charts) provide insight on turnout and voter activity. [Mintscan](https://www.mintscan.io/cosmos/proposals) can be used to fill in any gaps. - - -## Cosmos Improvement Proposals (CIPs) - -CIPs serve as the process for describing major changes or providing info about the protocol and APIs or processes of the Cosmos ecosystem. - -"The CIP process draws heavily from Ethereum's EIP process and Rust's RFC process. It pertains primarily to the protocol and APIs of the Cosmos Hub blockchain (Cosmos, for short), including Tendermint, Cosmos-SDK, IBC, and other modules. A CIP is a design document providing information to the Cosmos community, or describing a new feature or major change for Cosmos or its processes or environment." - -"This CIP process aims to subsume, but not necessarily to replace" the RFC and ADR processes. -🔗 - -### User Story: Governing Technical Direction - -Alice, a member of one core development team, submits a PR to the Cosmos cips repo after a recurring issue is identified in the standing GAIA / ATOM call. There has been a recurring discussion about how to formalize emerging agreement on a distinctive Cosmos interpretation of a technical feature common to blockchains. There are existing prior specifications in the bitcoin ecosystem that were the direct inspiration for Cosmos development, but over time the core development teams have developed a contrasting understanding of how their implementation provides a pathway to future specification development. At the end of last call, Alice decides this was important enough to step forward and take a first pass at drafting the spec based on the current roadmap. - -Alice follows the template from the repo to draft an early CIP and updates the frontmatter of the file to indicate the status is "draft." Once the PR is submitted, Alice pings a few developers who mentioned they would provide feedback in Discord and Slack bridge channels. The developers review the PR and leave inline comments and suggestions. Alice incorporates this feedback and requests the CIP be discussed at the next GAIA / ATOM call. In the meantime, Alice solicits community feedback on the PR, sharing it to the Cosmos Hub Discord and a relevant Slack connect channel. Once again Alice is asked to make minor changes, which are completed before the PR is finalized, the cip status is updated to "living" and it is merged by the cips repo owner. - - -### Process overview - -![Diagram of standarization process for CIPS](https://github.com/cosmos/cips/raw/main/assets/cip-1/CIP-process.png) - -- Ideas are ideally socialized first: "It is thus recommended to open a discussion thread on the Cosmos forum to do this, but you can also use the Cosmos Discord, the Cosmos subreddit or the Issues section of this repository." If the author decides to proceed, CIPs are drafted and submitted using the [cosmos/cips](https://github.com/cosmos/cips/) GitHub repo. -- When a CIP reaches the "Final" state, it represents a completed standard that is ready to be adopted. -- CIPs do not represent the views of the wider Cosmos community. CIP-1 states that "finalization of a CIP does not equate to acceptance into Cosmos. For that, CIP authors must turn to Cosmos Governance." -- Not all CIPS are taken through an on-chain vote -- A situation where CIPs interact with Cosmos Governance is while coordinating a software upgrade among validators. [CIP-5](https://github.com/cosmos/cips/blob/17a9ffc1cc40933ea3cf4460849ae713e6c244e3/CIPS/cip-5.md) [PR not merged], which offers guidelines for new modules to be integrated into Cosmos Hub ensuring safety and robustness, states "motivated by decentralization and the Cosmos community's decisions, a module's code is activated by submitting a parameter change proposal." - - - -### Process owners - -CIP editor: Ethan Buchman ([@ebuchman](https://github.com/ebuchman)) - -### Process maturity - -- There are 12 CIPs proposed to date, none are living, have been finalized, or taken through the on-chain governance process to be widely adopted. - - -## Cosmos SDK Architecture Decision Records (ADR) - -ADRs serve as the main way to propose new feature designs, new processes, and to document design decisions for the Cosmos SDK. - -"An Architectural Decision (AD) is a software design choice that addresses a functional or non-functional requirement that is architecturally significant. An Architecturally Significant Requirement (ASR) is a requirement that has a measurable effect on a software system's architecture and quality. An Architectural Decision Record (ADR) captures a single AD, such as often done when writing personal notes or meeting minutes; the collection of ADRs created and maintained in a project constitute its decision log." - -🔗 - -### Process overview - -- Ideas are socialized on GitHub first: "Every proposal SHOULD start with a new GitHub Issue or be a result of existing Issues. The Issue should contain just a brief proposal summary. Once the motivation is validated, a GitHub Pull Request (PR) is created" -- If the author decides to proceed, ADRs are drafted and submitted using the [cosmos/cosmos-sdk](https://github.com/cosmos/cosmos-sdk/tree/master/docs/architecture) GitHub repo. - 1. Copy the adr-template.md file. Use the following filename pattern: adr-next_number-title.md - 1. Create a draft Pull Request if you want to get an early feedback. - 1. Make sure the context and a solution is clear and well documented. - 1. Add an entry to a list in the [README](https://docs.cosmos.network/main/architecture/) file. - 1. Create a Pull Request to propose a new ADR. - `` -- ADRs go through a lifecycle: -``` -DRAFT -> PROPOSED -> LAST CALL yyyy-mm-dd -> ACCEPTED | REJECTED -> SUPERSEEDED by ADR-xxx - - \ | - - \ | - - v v - - ABANDONED -``` - -### Process owners - -- SDK [codeowners](https://github.com/cosmos/cosmos-sdk/blob/master/.github/CODEOWNERS): Aaron Craelius ([@aaronc](https://github.com/aaronc)) and Aleksandr Bezobchuk ([@alexanderbez](https://github.com/alexanderbez)) - -### Process maturity - -- A bunch have passed, many are proposed: - - -## Tendermint Request for Comments (RFC) - -RFCs are ways to both investigate and develop an idea prior to formalizing for inclusion in the Tendermint Spec, they also describe proposals to change the spec. - -"RFC stands for Request for Comments. It is a social device use to float and polish an idea prior to the inclusion into an existing or new spec/paper/research topic. RFC stands for Request for Comments. It is a social device use to float and polish an idea prior to the inclusion into an existing or new spec/paper/research topic." -🔗 - -"As part of our 1.0 push, we'll determine if gRPC is the right framework for our RPC layer; and if so, we'll implement it. This work will begin with an RFC, and we'll seek further input from community members and users. If this RFC is accepted, we'll write a transition plan for the RPC layer and execute it." -🔗 - -### Process overview - -- Not publicly documented - -### Process owners - -- Specification [general codeowners](https://github.com/tendermint/spec/blob/master/.github/CODEOWNERS): Zarko Milosevic ([@milosevic](https://github.com/milosevic)), Ethan Buchman ([@ebuchman](https://github.com/ebuchman)), Josef Widder ([@josef-widder](https://github.com/josef-widder)), Igor Konnov ([@konnov](https://github.com/konnov)) - -### Process maturity - -- 5 RFCs have been merged to the repo with an active pull request for adding one more - - -## Interchain Standards (ICS) - -ICSs are standards that document a particular protocol, standard, or feature of use to the Cosmos Ecosystem. - -"Interchain Standards (ICS) for the Cosmos network & interchain ecosystem." -🔗 - -"An inter-chain standard (ICS) is a design document describing a particular protocol, standard, or feature expected to be of use to the Cosmos ecosystem. An ICS should list the desired properties of the standard, explain the design rationale, and provide a concise but comprehensive technical specification. The primary ICS author is responsible for pushing the proposal through the standardisation process, soliciting input and support from the community, and communicating with relevant stakeholders to ensure (social) consensus." -🔗 - -### Process overview - -- Unclear where early discussions would happen -- ICSs are drafted and submitted using the [cosmos/ibc](https://github.com/cosmos/ibc) GitHub repo: -- To propose a new standard, [open an issue](https://github.com/cosmos/ics/issues/new). -- To start a new standardisation document, copy the [template](https://github.com/cosmos/ibc/blob/master/spec/ics-template.md) and open a PR. -- Standardization process has 4 phases, laid out in [PROCESS.md](https://github.com/cosmos/ibc/blob/master/meta/PROCESS.md) for a description of the standardisation process. - - Stage 1 - Strawman. Start the specification process - - Stage 2 - Draft. Make the case for the addition of this specification to the IBC ecosystem, describe the shape of a potential solution, and Identify challenges to this proposal. - - Stage 3 - Candidate. Indicate that further refinement will require feedback from implementations and users - - Stage 4 - Finalised. Indicate that the addition is included in the formal ICS standard set - -### Process owners - -- IBC [Standards Committee](https://github.com/cosmos/ibc/blob/master/meta/STANDARDS_COMMITTEE.md): Aditya Sripal ([@adityasripal](https://github.com/adityasripal)), Christopher Goes ([@cwgoes](https://github.com/cwgoes)), Zarko Milosevic ([@milosevic](https://github.com/milosevic)) - -### Process maturity - -- 16 have been merged into the repo with at least one more under active discussion: - - ---- - -## Observations and Discussion - -This report provides a descriptive account of the existing governance documentation and a snapshot of existing processes. Future work can probe specific questions and assumptions (e.g., if the goals to distribute decision-making or ensure a degree of sovereignty for zones are met) and focus on process refinement and [maturity](https://docs.google.com/document/d/1k2dxvd9IQF5WKXn67656bRloBtgdOWJ4mJ29m_qstPo/edit#heading=h.m8lb7fphmit0). - -### On-chain processes - -- UX limits who can create and vote for proposals, currently requiring the use of the CLI. If Cosmos Hub sees [itself as a port city](https://blog.cosmos.network/the-cosmos-hub-is-a-port-city-5b7f2d28debf), offering the best possible services, there is an argument to be made that it should extend that commitment to governance to ensure a diverse range of city dwellers and visitors can participate. -- Some validators feel that active participation in governance is a bottleneck to setting up validator businesses. I.e., that there are already a number of proposals they are asked to vote on. -- Cosmos Hub governance documentation is out of date, challenging to maintain, and difficult to discover. Current governance documentation is in the [`governance` repo as markdown](https://github.com/cosmos/governance), the [`gaia` documentation as vuepress](https://hub.cosmos.network/main/), and [`cosmos-sdk` documentation as vuepress](https://docs.cosmos.network/). -- Assessing this and making improvements is work that Hypha is currently undertaking, but there can be ongoing improvements -- The [upcoming x/gov and x/group alignment](https://docs.google.com/document/d/1w-fwa8i8kkgirbn9DOFklHwcu9xO_IdbMN910ASr2oQ/edit#) will allow for permissions related to governance to be delegated to other groups, opening up possibilities for multi-stakeholder governance approaches and products (see [related links](https://linktr.ee/cosmos_gov)). - -### Off-chain processes - -- More clarity is needed on when the CIPs should be used. It could be seen as the canonical home for high level decisions where alignment is required across the ecosystem but needs to be presented as such and the process needs refinement -- Some CIPS clearly impact all Cosmos ecosystem and blockchains and need ecosystem-wide buy-in, for example [CIP-11: Cosmos Hierarchical Deterministic key derivation](https://github.com/cosmos/cips/pull/11). -- ["RFC Interchain Staking Light Paper"](https://github.com/cosmos/gaia/issues/659) an example of a potential CIP that was PRd to the Gaia repo. The ambiguity makes sense: it fits criteria of informational CIP about the Cosmos environment (Light Paper), but also a shorter and higher level document is needed to function as more of a summary in order to get early user feedback and market ideas that isn't a CIP -- The terms "Cosmos" and "Cosmos Hub" are used interchangeably in the CIPs repository, so the intended audience could be made more clear. The [module readiness process and checklist](https://github.com/cosmos/cips/pull/6/files), which proposes a process for modules to be adopted by the Gaia team, suggests that the process is intended for teams involved in development related to the Cosmos Hub. -- Tendermint has an [ADR process](https://github.com/tendermint/tendermint/tree/master/docs/architecture) as well. Documentation around the relationship between the Tendermint ADR and the RFC processes would be valuable. - - diff --git a/docs/docs/governance/submitting.md b/docs/docs/governance/submitting.md index bafdaa4af69..101c5cb746a 100644 --- a/docs/docs/governance/submitting.md +++ b/docs/docs/governance/submitting.md @@ -6,7 +6,7 @@ order: 5 If you have a final draft of your proposal ready to submit, you may want to push your proposal live on the testnet first. These are the three primary steps to getting your proposal live on-chain. Interacting with the Cosmos Hub via the command line in order to run queries or submit proposals has several prerequisites: -- You will need to compile [`gaiad`](https://hub.cosmos.network/main/getting-started/installation.html) from source into a binary file executable by your operating system eg. MacOS, Windows, Linux +- You will need to compile [`gaiad`](../getting-started/installation) from source into a binary file executable by your operating system eg. MacOS, Windows, Linux - You will need to indicate which chain you are querying, and currently this is `--chain-id cosmoshub-4` - You will need to connect to a full node. You can find a list of available Cosmos Hub endpoints under the [API section](https://github.com/cosmos/chain-registry/blob/master/cosmoshub/chain.json) in the [Chain Registry](https://github.com/cosmos/chain-registry). - More info is in the Walkthrough Example section. @@ -48,7 +48,7 @@ Once on-chain, most people will rely upon block explorers to interpret this info ## Sending the transaction that submits your governance proposal -For information on how to use gaiad (the command line interface) to submit an on-chain proposal through the governance module, please refer to the [gaiad CLI tutorials](../hub-tutorials/gaiad.mdx) for the Cosmos Hub documentation. +For information on how to use gaiad (the command line interface) to submit an on-chain proposal through the governance module, please refer to the [gaiad CLI tutorials](../hub-tutorials/gaiad) for the Cosmos Hub documentation. ### Proposal types @@ -201,7 +201,7 @@ Use `gaiad tx gov --help` to get more info about the CLI options, we will explai 6. `--fees` is a flat-rate incentive for a validator to process your transaction. - Many nodes use a minimum fee to disincentivize transaction spamming. - 7500uatom is equal to 0.0075 ATOM. -8. `--node` is using an established node to send the transaction to the Cosmos Hub 4 network. For available nodes, please look at the [Chain Registry](https://github.com/cosmos/chain-registry/blob/master/cosmoshub/chain.json) (e.g. https://rpc.cosmos.network:443). +8. `--node` is using an established node to send the transaction to the Cosmos Hub 4 network. For available nodes, please look at the [Chain Registry](https://github.com/cosmos/chain-registry/blob/master/cosmoshub/chain.json). **Note**: be careful what you use for `--fees`. A mistake here could result in spending hundreds or thousands of ATOMs accidentally, which cannot be recovered. diff --git a/docs/docs/guidelines/code-guidelines.md b/docs/docs/guidelines/code-guidelines.md index ed174aafed4..ad91137d258 100644 --- a/docs/docs/guidelines/code-guidelines.md +++ b/docs/docs/guidelines/code-guidelines.md @@ -61,7 +61,7 @@ The goal of this guide is to manage this complexity by describing in detail the Try to avoid extensive methods and always test your code. All PRs should have at least 95% of code coverage. -- [Contributing](#contributing) +- Contributing - [Maintainability](#maintainability) - [Run tests](#run-tests) - [Guidelines](#guidelines) diff --git a/docs/docs/hub-tutorials/README.md b/docs/docs/hub-tutorials/README.md index 4d8443d5095..ec7b1745690 100644 --- a/docs/docs/hub-tutorials/README.md +++ b/docs/docs/hub-tutorials/README.md @@ -5,7 +5,7 @@ order: 1 This folder contains tutorials related to the `gaiad` application. -- [Interacting with the `gaiad` binary](/hub-tutorials/gaiad.mdx) +- [Interacting with the `gaiad` binary](./gaiad.md) - [Running a full-node for the Cosmos Hub Mainnet](./join-mainnet.md) - [Running a full-node for a `gaia` testnet](./join-testnet.md) - [Upgrading a node from a previous version](./upgrade-node.md) diff --git a/docs/docs/hub-tutorials/_category_.json b/docs/docs/hub-tutorials/_category_.json index bf6b294277a..073036b9b58 100644 --- a/docs/docs/hub-tutorials/_category_.json +++ b/docs/docs/hub-tutorials/_category_.json @@ -1,5 +1,5 @@ { - "label": "Gaia Tutorials", + "label": "Guides", "position": 3, "link": { "type": "doc", "id": "hub-tutorials/README" } } \ No newline at end of file diff --git a/docs/docs/hub-tutorials/gaiad.mdx b/docs/docs/hub-tutorials/gaiad.md similarity index 99% rename from docs/docs/hub-tutorials/gaiad.mdx rename to docs/docs/hub-tutorials/gaiad.md index 87ea5319f73..09480cbaadf 100644 --- a/docs/docs/hub-tutorials/gaiad.mdx +++ b/docs/docs/hub-tutorials/gaiad.md @@ -5,7 +5,7 @@ order: 5 ## Gaia Daemon -`gaiad` is the tool that enables you to interact with the node that runs on the Cosmos Hub network, whether you run it yourself or not. Let us set it up properly. In order to install it, follow the [installation procedure](../getting-started/installation.md). +`gaiad` is the tool that enables you to interact with the node that runs on the Cosmos Hub network, whether you run it yourself or not. Let us set it up properly. In order to install it, follow the [installation procedure](../getting-started/installation). ### Setting up gaiad @@ -39,7 +39,7 @@ gaiad config chain-id cosmoshub-2 The keyring holds the private/public keypairs used to interact with a node. For instance, a validator key needs to be set up before running the blockchain node, so that blocks can be correctly signed. The private key can be stored in different locations, called "backends", such as a file or the operating system's own key storage. -Headless environments are recommended to use either the `file` or `pass` backends. More information is available at the [SDK documentation page](https://docs.cosmos.network/v0.45/run-node/keyring.html). +Headless environments are recommended to use either the `file` or `pass` backends. More information is available at the [SDK documentation page](https://docs.cosmos.network/v0.47/user/run-node/keyring). #### Key Types diff --git a/docs/docs/hub-tutorials/join-mainnet.md b/docs/docs/hub-tutorials/join-mainnet.md index 59eef3580de..8af9fff3075 100644 --- a/docs/docs/hub-tutorials/join-mainnet.md +++ b/docs/docs/hub-tutorials/join-mainnet.md @@ -5,8 +5,9 @@ order: 2 # Join the Cosmos Hub Mainnet -The current Cosmos Hub mainnet, `cosmoshub-4`, has been performing in place store migration upgrades as of the [Delta Upgrade](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-delta-upgrade.md) July 2021. The most recent upgrade is [Gaia v14.1.x](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-v14-upgrade.md) Dec 2023. -This type of upgrade preserves the same chain-id but state before the upgrade height is only accessible by corresponding versions of the binary: +:::info +The chain-id of Cosmos Hub mainnet is `cosmoshub-4`. +::: ## Release History @@ -20,15 +21,16 @@ This type of upgrade preserves the same chain-id but state before the upgrade he - use `gaia v11.x` between `16,596,000` and `16,985,500` - use `gaia v12.x` between `16,985,500` and `17,380,000` - use `gaia v13.x` between `17,380,000` and `18,262,000` -- use `gaia v14.1.x` from `18,262,000` - -For more details, see the [history of upgrades](https://github.com/cosmos/gaia/tree/main/docs/roadmap) or visit the [migration section](https://github.com/cosmos/gaia/tree/main/docs/migration) of the Hub's docs. +- use `gaia v14.1.x` between `18,262,000` and `19,639,600` +- use `gaia v15.1.x` between `19,639,600` and `19,939,000` +- use `gaia v15.2.x` between `19,939,000` and `20,440,500` +- use `gaia v16.x` from `20,440,500` **This guide includes full instructions for joining the mainnet either as an archive/full node or a pruned node.** -For instructions to bootstrap a node via Quicksync or State Sync, see the [Quickstart Guide](https://hub.cosmos.network/main/getting-started/quickstart.html) +For instructions to bootstrap a node via Quicksync or State Sync, see the [Quickstart Guide](../getting-started/quickstart.mdx) -For instructions to join as a validator, please also see the [Validator Guide](https://hub.cosmos.network/main/validators/overview.html#). +For instructions to join as a validator, please also see the [Validator Guide](../validators/overview.mdx). ### Overview @@ -59,26 +61,22 @@ For instructions to join as a validator, please also see the [Validator Guide](h - [Exporting State](#exporting-state) - [Verify Mainnet](#verify-mainnet) -### Background - -The current Cosmos Hub mainnet `cosmoshub-4`. Visit the [migration section](https://github.com/cosmos/gaia/tree/main/docs/migration) of the Hub's docs for more information on previous chain migrations. ## Explorers There are many explorers for the Cosmos Hub. For reference while setting up a node, here are a few recommendations: - [Mintscan](https://www.mintscan.io/cosmos) -- [Big Dipper](https://cosmos.bigdipper.live/) - -- [Stake ID](https://cosmos.stake.id/) +* [Numia](https://www.datalenses.zone/chain/cosmos) +* [Ping.Pub](https://ping.pub/cosmos) ## Getting Started Make sure the following prerequisites are completed: - Choose the proper hardware/server configuration. See the [hardware guide](#hardware). -- Ensure Gaia is properly installed. See the [installation guide](https://hub.cosmos.network/main/getting-started/installation.html) for a walk-through. -- Follow the [configuration guide](#General-Configuration) to initialize and prepare the node to sync with the network. +- Ensure Gaia is properly installed. See the [installation guide](../getting-started/installation) for a walk-through. +- Follow the [configuration guide](../hub-tutorials/join-mainnet#general-configuration) to initialize and prepare the node to sync with the network. ## Hardware @@ -243,7 +241,7 @@ address = "0.0.0.0:9090" ## Sync Options -There are three main ways to sync a node on the Cosmos Hub; Blocksync, State Sync, and Quicksync. See the matrix below for the Hub's recommended setup configuration. This guide will focus on syncing two types of common nodes; full and pruned. For further information on syncing to run a validator node, see the section on [Validators](https://hub.cosmos.network/main/validators/overview.html). +There are three main ways to sync a node on the Cosmos Hub; Blocksync, State Sync, and Quicksync. See the matrix below for the Hub's recommended setup configuration. This guide will focus on syncing two types of common nodes; full and pruned. For further information on syncing to run a validator node, see the section on [Validators](../validators/overview.mdx). There are two types of concerns when deciding which sync option is right. _Data integrity_ refers to how reliable the data provided by a subset of network participants is. _Historical data_ refers to how robust and inclusive the chain’s history is. @@ -261,11 +259,11 @@ Make sure to consult the [hardware](#hardware) section for guidance on the best ### Blocksync -Blocksync is faster than traditional consensus and syncs the chain from genesis by downloading blocks and verifying against the merkle tree of validators. For more information see [CometBFT's Fastsync Docs](https://docs.cometbft.com/v0.34/core/fast-sync) +Blocksync is faster than traditional consensus and syncs the chain from genesis by downloading blocks and verifying against the merkle tree of validators. For more information see [CometBFT's Blocksync Docs](https://docs.cometbft.com/v0.37/core/block-sync) -When syncing via Blocksync, node operators will either need to manually upgrade the chain or set up [Cosmovisor](#Cosmovisor) to upgrade automatically. +When syncing via Blocksync, node operators will either need to manually upgrade the chain or set up [Cosmovisor](#cosmovisor) to upgrade automatically. -For more information on performing the manual upgrades, see [Releases & Upgrades](#Releases-amp=-Upgrades). +For more information on performing the manual upgrades, see [Releases & Upgrades](#releases--upgrades). It is possible to sync from previous versions of the Cosmos Hub. See the matrix below for the correct `gaia` version. See the [mainnet archive](https://github.com/cosmos/mainnet) for historical genesis files. @@ -278,7 +276,7 @@ It is possible to sync from previous versions of the Cosmos Hub. See the matrix ##### Getting Started -Start Gaia to begin syncing with the `skip-invariants` flag. For more information on this see [Verify Mainnet](#Verify-Mainnet). +Start Gaia to begin syncing with the `skip-invariants` flag. For more information on this see [Verify Mainnet](#verify-mainnet). ```bash gaiad start --x-crisis-skip-assert-invariants @@ -289,7 +287,7 @@ The node will begin rebuilding state until it hits the first upgrade height at b ### State Sync -State Sync is an efficient and fast way to bootstrap a new node, and it works by replaying larger chunks of application state directly rather than replaying individual blocks or consensus rounds. For more information, see [CometBFT's State Sync docs](https://docs.cometbft.com/v0.34/core/state-sync). +State Sync is an efficient and fast way to bootstrap a new node, and it works by replaying larger chunks of application state directly rather than replaying individual blocks or consensus rounds. For more information, see [CometBFT's State Sync docs](https://docs.cometbft.com/v0.37/core/state-sync). To enable state sync, visit an explorer to get a recent block height and corresponding hash. A node operator can choose any height/hash in the current bonding period, but as the recommended snapshot period is `1000` blocks, it is advised to choose something close to `current height - 1000`. @@ -315,7 +313,7 @@ enable = true # # For Cosmos SDK-based chains, trust_period should usually be about 2/3 of the unbonding time (~2 # weeks) during which they can be financially punished (slashed) for misbehavior. -rpc_servers = "https://cosmos-rpc.polkachu.com:443,https://rpc-cosmoshub-ia.cosmosia.notional.ventures:443,https://rpc.cosmos.network:443" +rpc_servers = "https://cosmos-rpc.polkachu.com:443,https://rpc-cosmoshub-ia.cosmosia.notional.ventures:443" trust_height = 8959784 trust_hash = "3D8F12EA302AEDA66E80939F7FC785206692F8B6EE6F727F1655F1AFB6A873A5" trust_period = "168h0m0s" @@ -371,78 +369,6 @@ snapshot-interval = 1000 snapshot-keep-recent = 10 ``` -## Releases & Upgrades - -**See all [Gaia Releases](https://github.com/cosmos/gaia/releases)** - -The most up to date release of Gaia is above. For those that want to use state sync or quicksync to get their node up to speed, starting with the most recent version of Gaia is sufficient. - -To sync an archive or full node from scratch, it is important to note that you must start with [`V4.2.1`](https://github.com/cosmos/gaia/releases/tag/v4.2.1) and proceed through two different upgrades Delta at block height `6,910,000`, Vega at block height `8,695,000`, Theta at block height `10,085,397`, Rho at block height `14099412` and Lambda at block height `14,470,501` and so on. - -The process is summarized below but make sure to follow the manual upgrade instructions for each release: - -**[Delta Instructions](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-delta-upgrade.md#Upgrade-will-take-place-July-12,-2021)** - -Once `V4` reaches the upgrade block height, expect the chain to halt and to see the following message: - -```bash -ERR UPGRADE "Gravity-DEX" NEEDED at height: 6910000: v5.0.0-4760cf1f1266accec7a107f440d46d9724c6fd08 -``` - -Make sure to save a backup of `~/.gaia` in case rolling back is necessary. - -Install Gaia [`V5.0.0`](https://github.com/cosmos/gaia/releases/tag/v5.0.0) and restart the daemon. - -**[Vega Instructions](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-vega-upgrade.md)** - -Once `V5` reaches the upgrade block height, the chain will halt and display the following message: - -```bash -ERR UPGRADE "Vega" NEEDED at height: 8695000 -``` - -Again, make sure to backup `~/.gaia` - -Install Gaia [`V6.0.0`](https://github.com/cosmos/gaia/releases/tag/v6.0.0) and restart the daemon. - -**[Theta Instructions](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-v7-Theta-upgrade.md)** - -Once `V6` reaches the upgrade block height, the chain will halt and display the following message: - -```bash -ERR UPGRADE "Theta" NEEDED at height: 10085397 -``` - -Again, make sure to backup `~/.gaia` - -Install Gaia [`V7.0.0`](https://github.com/cosmos/gaia/releases/tag/v7.0.0) and restart the daemon. - -**[Rho Instructions](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-v8-Rho-upgrade.md)** - -Once `V7` reaches the upgrade block height, the chain will halt and display the following message: - -```bash -ERR UPGRADE "Rho" NEEDED at height: 14099412 -``` - -Again, make sure to backup `~/.gaia` - -Install Gaia [`V8.0.0`](https://github.com/cosmos/gaia/releases/tag/v8.0.0) and restart the daemon. - -**[Lambda Instructions](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-v9-Lambda-upgrade.md)** - -Once `V8` reaches the upgrade block height, the chain will halt and display the following message: - -```bash -ERR UPGRADE "Lambda" NEEDED at height: 14470501 -``` - -Again, make sure to backup `~/.gaia` - -Install Gaia [`V9.0.0`](https://github.com/cosmos/gaia/releases/tag/v9.0.0) and restart the daemon. - -Repeat the process for newer versions of the Gaia application at the [stated block heights above](#release-history). - ## Cosmovisor Cosmovisor is a process manager developed to relieve node operators of having to manually intervene every time there is an upgrade. Cosmovisor monitors the governance module for upgrade proposals; it will take care of downloading the new binary, stopping the old one, switching to the new one, and restarting. diff --git a/docs/docs/hub-tutorials/join-testnet.md b/docs/docs/hub-tutorials/join-testnet.md index c414d676c84..d7202847ab7 100644 --- a/docs/docs/hub-tutorials/join-testnet.md +++ b/docs/docs/hub-tutorials/join-testnet.md @@ -5,7 +5,7 @@ order: 3 This tutorial will provide all necessary instructions for joining the current public testnet. If you're interested in more advanced configuration and synchronization options, see [Join Mainnet](./join-mainnet.md) for a detailed walkthrough. -* Current Version: v15 +* Current Version: v17 * Chain ID: `theta-testnet-001` ## Background @@ -53,8 +53,8 @@ We recommend running public testnet nodes on machines with at least 8 cores, 32G There are two ways to sync a testnet node, Fastsync and State Sync. -* [Fast Sync](https://docs.cometbft.com/v0.34/core/fast-sync) syncs the chain from genesis by downloading blocks in parallel and then verifying them. -* [State Sync](https://docs.cometbft.com/v0.34/core/state-sync) will look for snapshots from peers at a trusted height and then verifying a minimal set of snapshot chunks against the network. +* [Fast Sync](https://docs.cometbft.com/v0.37/core/block-sync) syncs the chain from genesis by downloading blocks in parallel and then verifying them. +* [State Sync](https://docs.cometbft.com/v0.37/core/state-sync) will look for snapshots from peers at a trusted height and then verifying a minimal set of snapshot chunks against the network. State Sync is far faster and more efficient than Fast Sync, but Fast Sync offers higher data integrity and more robust history. For those who are concerned about storage and costs, State Sync can be the better option as it minimizes storage usage when rebuilding initial state. @@ -79,7 +79,7 @@ export PATH=$PATH:/usr/local/go/bin ### Installation & Configuration -You will need to install and configure the Gaia binary using the script below. The Cosmos Hub Public Testnet is running Gaia [`v15.0.0-rc0`](https://github.com/cosmos/gaia/releases/tag/v15.0.0-rc0). +You will need to install and configure the Gaia binary using the script below. The Cosmos Hub Public Testnet is running Gaia [`v17.0.0-rc0`](https://github.com/cosmos/gaia/releases/tag/v17.0.0-rc0). * For up-to-date endpoints like seeds and state sync RPC servers, visit the [testnets repository](https://github.com/cosmos/testnets/tree/master/public). @@ -90,7 +90,7 @@ cd $HOME git clone https://github.com/cosmos/gaia cd gaia # To sync from genesis, comment out the next line. -git checkout v15.0.0-rc0 +git checkout v17.0.0-rc0 # To sync from genesis, uncomment the next line and skip the State Sync Setup section. # git checkout v6.0.4 make install @@ -248,7 +248,7 @@ There are three ways you can update the binary: The instructions below are for option 2. For more information on auto-download with Cosmovisor, see the relevant [documentation](https://github.com/cosmos/cosmos-sdk/tree/main/tools/cosmovisor#auto-download) in the Cosmos SDK repo. -If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, Cosmovisor will look for the new binary in a folder that matches the name of the upgrade specified in the software upgrade proposal. For the `v16` upgrade, the expected folder structure would look as follows: +If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, Cosmovisor will look for the new binary in a folder that matches the name of the upgrade specified in the software upgrade proposal. For the `v17` upgrade, the expected folder structure would look as follows: ```shell .gaia @@ -258,7 +258,7 @@ If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, │ └── bin | └── gaiad └── upgrades - └── v16 + └── v17 └── bin └── gaiad ``` @@ -266,7 +266,7 @@ If the environment variable `DAEMON_ALLOW_DOWNLOAD_BINARIES` is set to `false`, Prepare the upgrade directory ```shell -mkdir -p ~/.gaia/cosmovisor/upgrades/v16/bin +mkdir -p ~/.gaia/cosmovisor/upgrades/v17/bin ``` Download and install the new binary version. @@ -274,11 +274,11 @@ Download and install the new binary version. ```shell cd $HOME/gaia git pull -git checkout v16.0.0-rc0 +git checkout v17.0.0-rc0 make install # Copy the new binary to the v16 upgrade directory -cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v16/bin/gaiad +cp ~/go/bin/gaiad ~/.gaia/cosmovisor/upgrades/v17/bin/gaiad ``` When the upgrade height is reached, Cosmovisor will stop the gaiad binary, copy the new binary to the `current/bin` folder and restart. After a few minutes, the node should start syncing blocks using the new binary. diff --git a/docs/docs/hub-tutorials/upgrade-node.md b/docs/docs/hub-tutorials/upgrade-node.md index 85310944374..80f39730da5 100644 --- a/docs/docs/hub-tutorials/upgrade-node.md +++ b/docs/docs/hub-tutorials/upgrade-node.md @@ -9,7 +9,7 @@ This document describes the upgrade procedure of a `gaiad` full-node to a new ve ## Cosmovisor -The Cosmos SDK provides a convenient process manager that wraps around the `gaiad` binary and can automatically swap in new binaries upon a successful governance upgrade proposal. Cosmovisor is entirely optional but recommended. More information can be found in [cosmos.network docs](https://docs.cosmos.network/v0.45/run-node/cosmovisor.html) and [cosmos-sdk/cosmovisor/readme](https://github.com/cosmos/cosmos-sdk/blob/v0.45.0/cosmovisor/README.md). +The Cosmos SDK provides a convenient process manager that wraps around the `gaiad` binary and can automatically swap in new binaries upon a successful governance upgrade proposal. Cosmovisor is entirely optional but recommended. More information can be found in [cosmos.network docs](https://docs.cosmos.network/v0.45/run-node/cosmovisor.html) and [cosmos-sdk/cosmovisor/readme](https://github.com/cosmos/cosmos-sdk/blob/v0.47.11/tools/cosmovisor/README.md). ### Setup @@ -81,7 +81,7 @@ gaiad start ## Upgrade Genesis File :::warning -If the new version you are upgrading to has breaking changes, you will have to restart your chain. If it is not breaking, you can skip to [Restart](#restart) +If the new version you are upgrading to has breaking changes, you will have to restart your chain. If it is not breaking, you can skip to [Restart](/hub-tutorials/upgrade-node#restart) ::: To upgrade the genesis file, you can either fetch it from a trusted source or export it locally. @@ -141,3 +141,11 @@ gaiad unsafe-reset-all ``` Your node is now in a pristine state while keeping the original `priv_validator.json` and `config.toml`. If you had any sentry nodes or full nodes setup before, your node will still try to connect to them, but may fail if they haven't also been upgraded. + +## Restart + +If there are no breaking changes then you can simply restart the node by running: + +```bash +gaiad start +``` diff --git a/docs/docs/index.mdx b/docs/docs/index.md similarity index 85% rename from docs/docs/index.mdx rename to docs/docs/index.md index 758e26de183..ca62c11d48a 100644 --- a/docs/docs/index.mdx +++ b/docs/docs/index.md @@ -23,31 +23,32 @@ The Cosmos Hub is the first of [thousands of interconnected blockchains](https:/ Do you have ATOM tokens? With ATOM, you have the superpower to contribute to the security and governance of the Cosmos Hub. Delegate your ATOM to one or more of the validators on the Cosmos Hub blockchain to earn more ATOM through Proof-of-Stake. You can also vote with your ATOM to influence the future of the Cosmos Hub through on-chain governance proposals. -Learn more about [being a delegator](/delegators/delegator-faq.md), learn about [the security risks](/delegators/delegator-security.md), and start participating with one of the following wallets. +Learn more about [being a delegator](./delegators/delegator-faq.md), learn about [the security risks](./delegators/delegator-security.md), and start participating with one of the following wallets. ## Cosmos Hub Wallets - +::: These community-maintained web and mobile wallets allow you to store & transfer ATOM, delegate ATOM to validators, and vote on on-chain governance proposals. Note that we do not endorse any of the wallets, they are listed for your convenience. +* [Keplr](https://wallet.keplr.app) - Web +* [Ledger](https://www.ledger.com/cosmos-wallet) - Hardware +* [Cosmostation](https://www.cosmostation.io/) - Android, iOS +* [Leap Wallet](https://www.leapwallet.io/) - Android, iOS, Web * [Atomic Wallet](https://atomicwallet.io/) - Android, Linux, macOS, Windows * [Citadel.One](https://citadel.one/#mobile) - Android, iOS * [Cobo](https://cobo.com/) - Android, iOS -* [Cosmostation](https://www.cosmostation.io/) - Android, iOS * [Crypto.com](https://crypto.com/) - Android, iOS * [Huobi Wallet](https://www.huobiwallet.com/) - Android, iOS * [ShapeShift Wallet](https://app.shapeshift.com/) - Android, iOS * [imToken](https://token.im/) - Android, iOS -* [Keplr](https://wallet.keplr.app) - Web -* [Ledger](https://www.ledger.com/cosmos-wallet) - Hardware * [Math Wallet](https://www.mathwallet.org/en/) - Android, iOS, Web * [Rainbow Wallet](https://www.rainbow.one) - Android, iOS * [Trust Wallet](https://trustwallet.com/) Android, iOS * [Komodo Wallet](https://atomicdex.io/en/) -* [Leap Wallet](https://www.leapwallet.io/) - Android, iOS, Web + ## Metamask Snaps @@ -58,27 +59,26 @@ These community-maintained web and mobile wallets allow you to store & transfer These block explorers allow you to search, view and analyze Cosmos Hub data—like blocks, transactions, validators, etc. +* [Mintscan](https://mintscan.io) +* [Numia](https://www.datalenses.zone/chain/cosmos) * [ATOMScan](https://atomscan.com) -* [Big Dipper](https://cosmos.bigdipper.live) * [IOBScan](https://cosmoshub.iobscan.io/) -* [Mintscan](https://mintscan.io) * [Ping.Pub](https://ping.pub/cosmos) * [BronBro](https://monitor.bronbro.io/d/cosmos-stats/cosmos) -* [Numia](https://www.datalenses.zone/chain/cosmos) * [SmartStake](https://cosmos.smartstake.io/stats) ## Cosmos Hub CLI -`gaiad` is a command-line interface that lets you interact with the Cosmos Hub. `gaiad` is the only tool that supports 100% of the Cosmos Hub features, including accounts, transfers, delegation, and governance. Learn more about `gaiad` with the [delegator's CLI guide](/delegators/delegator-guide-cli.md). +`gaiad` is a command-line interface that lets you interact with the Cosmos Hub. `gaiad` is the only tool that supports 100% of the Cosmos Hub features, including accounts, transfers, delegation, and governance. Learn more about `gaiad` with the [delegator's CLI guide](./delegators/delegator-guide-cli.md). ## Running a full-node on the Cosmos Hub Mainnet -In order to run a full-node for the Cosmos Hub mainnet, you must first [install `gaiad`](/getting-started/installation.md). Then, follow [the guide](/hub-tutorials/join-mainnet.md). -If you are looking to run a validator node, follow the [validator setup guide](/validators/validator-setup.md). +In order to run a full-node for the Cosmos Hub mainnet, you must first [install `gaiad`](./getting-started/installation). Then, follow [the guide](./hub-tutorials/join-mainnet). +If you are looking to run a validator node, follow the [validator setup guide](./validators/validator-setup). ## Join the Community -Have questions, comments, or new ideas? Participate in the Cosmos community through one of the following channels. Also check out the [latest events](https://cosmos.network/community). +Have questions, comments, or new ideas? Participate in the Cosmos community through one of the following channels. * [Cosmos Community Discord](https://discord.gg/cosmosnetwork) * [Cosmos Community Telegram](https://t.me/cosmosproject) diff --git a/docs/docs/interchain-security/README.md b/docs/docs/interchain-security/README.md index b61408f1eb7..df678dc0145 100644 --- a/docs/docs/interchain-security/README.md +++ b/docs/docs/interchain-security/README.md @@ -3,18 +3,40 @@ title: Interchain Security order: 3 --- -The Interchain Security feature, brings to the Cosmos Hub a shared security model, where the Cosmos Hub validators, also validate on consumer chains. This is valuable for consumer chains, as consumer chains can focus on product-market fit, rather than business and operational agreements in bringing together a validator set. As part of this agreement, consumer chains pay for the security by distributing a portion of the consumer chain revenue to Hub token holders. +The [Interchain Security](https://cosmos.github.io/interchain-security/) feature brings to the Cosmos Hub a shared security model, where the Cosmos Hub validators, also validate on consumer chains. This is valuable for consumer chains, as consumer chains can focus on product-market fit, rather than business and operational agreements in bringing together a validator set. As part of this agreement, consumer chains pay for the security by distributing a portion of the consumer chain revenue to Hub token holders. All potential chains are onboarded as consumer chains, via Hub Governance, with the feedback from the Hub community. +## New ICS features + +Novel Interchain Security features such as [Partial Set Security](https://cosmos.github.io/interchain-security/features/partial-set-security) and [Power Shaping](https://cosmos.github.io/interchain-security/features/power-shaping) bring benefits for both the consumer chains and validators: + +### Top-N consumer chains +Validators inside the top-N percent of voting power are required to validate the consumer chain. + +e.g. `top-95` means that the 95% of the validators (by voting power) are required to run the consumer chain binary + +### Opt-in consumer chains +Only validators that opt to running a consumer chains are required to run the chain binary and become eiligible for consumer chain rewards distribution. + +### New consumer chain parameters + +Consumer chains gain the ability to customize the validator set to their needs: +* define allow/denylists +* set maximum number of validators +* set validator power cap + + +## Notable consumer chains + Currently the Cosmos Hub has the following two Consumer Chains. -## Neutron +### Neutron [Neutron](https://neutron.org/), is a smart contracting platform, that was the first consumer chain onboarded. Neutron was onboarded as a consumer chain in May 2023, see Hub [proposal 792](https://www.mintscan.io/cosmos/proposals/792) for more details. -## Stride +### Stride [Stride](https://www.stride.zone/), is a liquid staking provider, which aims to unlock liquidity for Cosmos Hub token holders. Stride was onboarded as a consumer chain in July 2023, see Hub [proposal 799](https://www.mintscan.io/cosmos/proposals/799) for more details. diff --git a/docs/docs/interchain-security/_category_.json b/docs/docs/interchain-security/_category_.json index f18ce8bb027..72a3de1b757 100644 --- a/docs/docs/interchain-security/_category_.json +++ b/docs/docs/interchain-security/_category_.json @@ -1,5 +1,5 @@ { "label": "Interchain Security", - "position": 14, + "position": 6, "link": { "type": "doc", "id": "interchain-security/README" } } \ No newline at end of file diff --git a/docs/docs/migration/_category_.json b/docs/docs/migration/_category_.json index 328b468cbc6..d2312acd858 100644 --- a/docs/docs/migration/_category_.json +++ b/docs/docs/migration/_category_.json @@ -1,5 +1,5 @@ { "label": "Upgrade Instructions", - "position": 9, + "position": 17, "link": { "type": "doc", "id": "migration/README" } } \ No newline at end of file diff --git a/docs/docs/migration/archive/cosmoshub-4/cosmoshub-4-v6-vega-upgrade.md b/docs/docs/migration/archive/cosmoshub-4/cosmoshub-4-v6-vega-upgrade.md index 9c4cfbe7c0c..8ae9c880247 100644 --- a/docs/docs/migration/archive/cosmoshub-4/cosmoshub-4-v6-vega-upgrade.md +++ b/docs/docs/migration/archive/cosmoshub-4/cosmoshub-4-v6-vega-upgrade.md @@ -266,6 +266,6 @@ The riskiest thing a validator can do is discover that they made a mistake and r [cosmos/vega-test](https://github.com/cosmos/vega-test) -[Delta upgrade instruction](https://github.com/cosmos/gaia/blob/main/docs/migration/cosmoshub-4-delta-upgrade.md) +[Delta upgrade instruction](https://github.com/cosmos/gaia/tree/main/docs/docs/migration/cosmoshub-4-delta-upgrade.md) diff --git a/docs/docs/modules/globalfee.md b/docs/docs/modules/globalfee.md index b4b4875dbaa..51f899a9669 100644 --- a/docs/docs/modules/globalfee.md +++ b/docs/docs/modules/globalfee.md @@ -87,13 +87,13 @@ bypass-min-fee-msg-types = ["/ibc.core.channel.v1.MsgRecvPacket", "/ibc.core.cha The `minimum-gas-prices` parameter enables node operators to set its minimum fee requirements, and it can be set in the `config/app.toml` file. Please note: if `minimum-gas-prices` is set to include zero coins, the zero coins are sanitized when [`SetMinGasPrices`](https://github.com/cosmos/gaia/blob/76dea00bd6d11bfef043f6062f41e858225820ab/cmd/gaiad/cmd/root.go#L221). When setting `minimum-gas-prices`, it's important to keep the following rules in mind: -- The denoms in `min-gas-prices` that are not present in the global fees list are ignored. +- The denoms in `min-gas-prices` that are not present in the global fees list are ignored. - The amounts in `min-gas-prices` that are lower than global fees `MinimumGasPricesParam` are ignored. - The amounts in `min-gas-prices` are considered as fee requirement only if they are greater than the amounts for the corresponding denoms in the global fees list. ## Fee AnteHandler Behaviour -The denoms in the global fees list and the `minimum-gas-prices` param are merged and de-duplicated while keeping the higher amounts. Denoms that are only in the `minimum-gas-prices` param are discarded. +The denoms in the global fees list and the `minimum-gas-prices` param are merged and de-duplicated while keeping the higher amounts. Denoms that are only in the `minimum-gas-prices` param are discarded. If the denoms of the transaction fees are a subset of the merged fees and at least one of the amounts of the transaction fees is greater than or equal to the corresponding required fees amount, the transaction can pass the fee check, otherwise an error will occur. @@ -190,7 +190,7 @@ A `proposal.json` example to change the `maxTotalBypassMinFeeMsgGasUsage` in glo Here are a few examples to clarify the relationship between global fees, minimum-gas-prices and transaction fees. **Note:** Transactions can include zero-coin fees. However, these fees are removed from the transaction fees during the fee [parsing](https://github.com/cosmos/cosmos-sdk/blob/e716e4103e934344aa7be6dc9b5c453bdec5f225/client/tx/factory.go#L144) / [sanitizing](https://github.com/cosmos/cosmos-sdk/blob/e716e4103e934344aa7be6dc9b5c453bdec5f225/types/dec_coin.go#L172) before reaching the fee AnteHandler. -This means `paidfee = "1uatom, 0stake"` and `paidfee = "1uatom"` are equivalent, and similarly, `paidfee = "0uatom"` is equivalent to `paidfee = ""`. +This means `paidfee = "1uatom, 0stake"` and `paidfee = "1uatom"` are equivalent, and similarly, `paidfee = "0uatom"` is equivalent to `paidfee = ""`. In the following examples, zero-coin fees are removed from the transaction fees, globalfee refers to `MinimumGasPricesParam` in globalfee params, minimum-gas-prices refers to the local `minimum-gas-prices` setup in `app.toml`. ### Case 1 diff --git a/docs/docs/resources/ledger.md b/docs/docs/resources/ledger.md index 547880f4eb1..449b6651ad9 100644 --- a/docs/docs/resources/ledger.md +++ b/docs/docs/resources/ledger.md @@ -71,7 +71,7 @@ The tool used to generate addresses and transactions on the Cosmos Hub network i ### Before you Begin - [Install Golang](https://golang.org/doc/install) -- [Install Gaia](../getting-started/installation.md) +- [Install Gaia](../getting-started/installation) Verify that gaiad is installed correctly with the following command diff --git a/docs/docs/resources/service-providers.md b/docs/docs/resources/service-providers.md index 9c85b13c009..ad92a51f76e 100644 --- a/docs/docs/resources/service-providers.md +++ b/docs/docs/resources/service-providers.md @@ -9,20 +9,19 @@ Service Providers are expected to act as trusted points of contact to the blockc This document describes: -- [Service Providers](#service-providers) - - [Connection Options](#connection-options) - - [Running a Full Node](#running-a-full-node) - - [What is a Full Node?](#what-is-a-full-node) - - [Installation and Configuration](#installation-and-configuration) - - [Command-Line Interface](#command-line-interface) - - [Available Commands](#available-commands) - - [Remote Access to gaiad](#remote-access-to-gaiad) - - [Create a Key Pair](#create-a-key-pair) - - [Check your Account](#check-your-account) - - [Check your Balance](#check-your-balance) - - [Send Coins Using the CLI](#send-coins-using-the-cli) - - [REST API](#rest-api) - - [Listen for Incoming Transactions](#listen-for-incoming-transactions) +- [Connection Options](#connection-options) +- [Running a Full Node](#running-a-full-node) + - [What is a Full Node?](#what-is-a-full-node) + - [Installation and Configuration](#installation-and-configuration) +- [Command-Line Interface](#command-line-interface) + - [Available Commands](#available-commands) + - [Remote Access to gaiad](#remote-access-to-gaiad) + - [Create a Key Pair](#create-a-key-pair) + - [Check your Account](#check-your-account) + - [Check your Balance](#check-your-balance) + - [Send Coins Using the CLI](#send-coins-using-the-cli) +- [REST API](#rest-api) + - [Listen for Incoming Transactions](#listen-for-incoming-transactions) ## Connection Options @@ -43,9 +42,9 @@ A Full Node is a network node that syncs up with the state of the blockchain. It This section describes the steps to run and interact with a full node for the Cosmos Hub. -First, you need to [install the software](../getting-started/installation.md). +First, you need to [install the software](../getting-started/installation). -Consider running your own [Cosmos Hub Full Node](../hub-tutorials/join-mainnet.md). +Consider running your own [Cosmos Hub Full Node](../hub-tutorials/join-mainnet). ## Command-Line Interface @@ -277,11 +276,11 @@ Flags: ## REST API -The [REST API documents](https://v1.cosmos.network/rpc/v0.44.5) list all the available endpoints that you can use to interact +The REST API documents list all the available endpoints that you can use to interact with your full node. Learn [how to enable the REST API](../hub-tutorials/join-mainnet.md#enable-the-rest-api) on your full node. ### Listen for Incoming Transactions The recommended way to listen for incoming transactions is to periodically query the blockchain by using the following HTTP endpoint: -[`/cosmos/bank/v1beta1/balances/{address}`](https://cosmos.network/rpc/) +`/cosmos/bank/v1beta1/balances/{address}` diff --git a/docs/docs/roadmap/README.md b/docs/docs/roadmap/README.md deleted file mode 100644 index ecb1abb37da..00000000000 --- a/docs/docs/roadmap/README.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Roadmap & Previous Releases -order: 2 ---- - -This folder contains details about the CosmosHub launch, previous releases and the current CosmosHub roadmap. - -- CosmosHub Launch - - [Cosmos Hub to Launch Mainnet](./launch/blog-1-en.md) - - [The 3 Phases of the Cosmos Hub Mainnet](./launch/blog-2-en.md) -- Previous Releases - - [Previous CosmosHub `gaiad` releases](./previous-releases.md) -- Roadmap - - [CosmosHub Roadmap](./cosmos-hub-roadmap-2.0.md) diff --git a/docs/docs/roadmap/_category_.json b/docs/docs/roadmap/_category_.json deleted file mode 100644 index 06ecee1dfdf..00000000000 --- a/docs/docs/roadmap/_category_.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "label": "Roadmap & Releases", - "position": 7, - "link": { "type": "doc", "id": "roadmap/README" } -} \ No newline at end of file diff --git a/docs/docs/roadmap/cosmos-hub-roadmap-2.0.md b/docs/docs/roadmap/cosmos-hub-roadmap-2.0.md deleted file mode 100644 index 5991783ea61..00000000000 --- a/docs/docs/roadmap/cosmos-hub-roadmap-2.0.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: The Cosmos Hub Roadmap -order: 1 ---- - -This Cosmos Hub roadmap serves as a reference for the current planned features of upcoming releases. For past releases, please see the following [document](./README.md). - -The Cosmos Hub is decentralized and other teams contribute to it as well. - -The Informal Systems roadmap can be found [here](https://docs.google.com/document/d/1EsA7WstAVz9kHfLeaBAUYo0cFNKcdkwnfDPP3xKzN4I/edit#heading=h.2hlqd6ar7xmu). Other teams also contribute actively to the Hub, but that information lives in other repos or project boards. diff --git a/docs/docs/roadmap/launch/_category_.json b/docs/docs/roadmap/launch/_category_.json deleted file mode 100644 index 4976a350a6a..00000000000 --- a/docs/docs/roadmap/launch/_category_.json +++ /dev/null @@ -1,5 +0,0 @@ -{ - "label": "Cosmos Hub Launch", - "position": 1, - "link": null -} \ No newline at end of file diff --git a/docs/docs/roadmap/launch/blog-1-en.md b/docs/docs/roadmap/launch/blog-1-en.md deleted file mode 100644 index a4bf3fbbf88..00000000000 --- a/docs/docs/roadmap/launch/blog-1-en.md +++ /dev/null @@ -1,228 +0,0 @@ ---- -title: Cosmos Hub to Launch Mainnet -order: 1 ---- - - - -## Pre-launch Dependencies & How to Safely Claim Your Atoms - -In the summer of 2016, the [Cosmos whitepaper][whitepaper] was released. In the -spring of 2017, the [Cosmos fundraiser][fundraiser] was completed. In the first -months of 2019, the software is [feature complete][releases]. The launch of the -Cosmos Hub draws near. What does this mean for Atom holders? - -If you are an Atom holder, you will be able to delegate Atoms to validators on -the main network and vote on governance proposals. In fact, the future success -of the network depends on you responsibly doing so! However, you will not be -able to transfer Atoms yet. Transfers will be disabled at the protocol level -until a hard-fork is executed to enable them. - -Atom holders should carefully follow the guidelines in order to safely delegate -Atoms. Please read through the entire guide first to familiarize yourself -before you actually do anything: [CLI guide][cli] - -The process outlined in the guide is currently the only verified and secure way -to delegate Atoms at launch. This is because the gaiad tool used in the guide -is the only wallet software undergoing third-party security audits right now. -No other wallet providers have begun security audits yet. - -Remember that delegating Atoms involves significant risk. Once delegated to a -validator, Atoms are bonded for a period of time during which they cannot be -recovered. If the validator misbehaves during this time, some or all of the -delegated Atoms may be burned. It is your responsibility to perform due -diligence on validators before delegating! - -The Cosmos Hub is highly experimental software. In these early days, we can -expect to have issues, updates, and bugs. The existing tools require advanced -technical skills and involve risks which are outside of the control of the -Interchain Foundation and/or the Tendermint team (see also the risk section in -the [Interchain Cosmos Contribution Terms][terms]). Any use of this open source -[Apache 2.0 licensed][apache] software is done at your own risk and on a “AS -IS” basis without warranties or conditions of any kind, and any and all -liability of the Interchain Foundation and/or the Tendermint team for damages -arising in connection to the software is excluded. Please exercise extreme -caution! - -If you are looking for more information about delegation and want to talk to -the folks developing Cosmos, join the virtual meetup on February 14 where you -will be walked through the step-by-step instructions for delegating Atoms at -launch. - -Register here: [gotowebinar.com/register/][webinar] - -## Remaining Milestones for Launch - -To follow mainnet launch progress, please bookmark: -[cosmos.network/launch][cosmos]. - -### 5 Cosmos-SDK Security Audits ✔ - -In early January, the Cosmos-SDK underwent the first in a series of third-party -security assessments scheduled for Q1 2019. This audit took place over a two -and a half week period. To date, two different security auditing firms have -assessed various parts of the Cosmos-SDK and a third audit is under way. - -### 4 Cosmos SDK Feature Freeze - -The final breaking changes to the Cosmos-SDK are included in the [v0.31.0 -launch RC][rc]. Once this RC is completed, the Cosmos-SDK team will engage in a -round of internal bug hunting to further ensure sufficient pre-launch security -due diligence. - -Right after Cosmos-SDK v0.31.0 is released, a Gaia testnet will be released in -an effort to flush out any hard to find bugs. - -### 3 Game of Stakes Completed - -Game of Stakes (GoS), [the first adversarial testnet competition of its -kind][gos], was launched in December 2018 to stress test the economic incentive -and social layers of a blockchain network secured purely by Proof-of-Stake. The -GoS blockchain was successfully hard-forked three times to date. As soon as the -GoS concludes, the [scoring criteria][scoring] will be used to determine -winners. Those will be announced following the completion of the game. - -### 2 Genesis Transactions Collected - -The Interchain Foundation will publish a recommendation for the allocation of -Atoms at genesis. This will include allocations for Cosmos fundraiser -participants, early contributors, and Game of Stakes winners. Any one with a -recommended allocation will have the opportunity to submit a gentx, which is -required to become a validator at genesis. The ultimate result of the -recommended allocation and the collection of gentxs is a final [genesis -file][file]. - -### 1 Cosmos Hub Mainnet Launch - -Once a genesis file is adopted by the community, and +⅔ of the voting power -comes online, the Cosmos mainnet will be live. - -## Official Cosmos Communication Channels - -These are the official accounts that will communicate launch details: - -- [Cosmos Network](https://twitter.com/cosmos) -- [Cosmos GitHub](https://github.com/cosmos) -- [Cosmos Blog](https://blog.cosmos.network) - -Please be aware that the [Cosmos forum][forum], [Riot chat groups][riot], and -[Telegram group][telegram] should not be treated as official news from Cosmos. - -If you have doubt or confusion about what next steps to take and are unsure -about trustworthy sources of information, do nothing for the initial period and -wait for an update via the three communication channels listed above. Do not -ever provide your 12 words to any admin, websites or unofficial software. - -**We will never ask you for your private key or your seed phrase.** - -## Staying Safe (and Secure!) for Mainnet Launch - -The launch of any public blockchain is an incredibly exciting time, and it’s -definitely one that malicious actors may try to take advantage of for their own -personal gain. [Social engineering][social] has existed for about as long as -human beings have been on the planet, and in the technical era, it usually -takes in the form of [phishing] or [spearphishing]. Both of these attacks are -wildly successful forms of trickery that are responsible for over 95% of -account security breaches, and they don’t just happen via email: these days, -opportunistic and targeted phishing attempts take place [anywhere that you have -an inbox][inbox]. It doesn’t matter if you’re using Signal, Telegram, SMS, -Twitter, or just checking your DMs on forums or social networks, attackers have -a [plethora of opportunities][opportunities] to gain foothold in your digital -life in effort to separate you from valuable information and assets that you -most definitely don’t want to lose. - -While the prospect of having to deal with a malicious actor plotting against -you may seem daunting, there are many things that you can do to protect -yourself from all kinds of social engineering schemes. In terms of preparing -for mainnet launch, this should require training your instincts to successfully -detect and avoid security risks, curating resources to serve as a source of -truth for verifying information, and going through a few technical steps to -reduce or eliminate the risk of key or credential theft. - -**Here are few rules of engagement to keep in mind when you’re preparing for -Cosmos mainnet launch:** - -- Download software directly from official sources, and make sure that you’re - always using the latest, most secure version of gaiad when you’re doing - anything that involves your 12 words. The latest versions of Tendermint, the - Cosmos-SDK, and gaiad will always be available from our official GitHub - repositories, and downloading them from there ensures that you will not be - tricked into using a maliciously modified version of software. - -- Do not share your 12 words with anyone. The only person who should ever need - to know them is you. This is especially important if you’re ever approached - by someone attempting to offer custodial services for your Atom: to avoid - losing control of your tokens, you should store them offline to minimize the - risk of theft and have a strong backup strategy in place. And never, ever - share them with anyone else. - -- Be skeptical of unexpected attachments or emails that ask you to visit a - suspicious or unfamiliar website in the context of blockchains or - cryptocurrency. An attacker may attempt to lure you to a [compromised site] - designed to steal sensitive information from your computer. If you’re a Gmail - user, test your resilience against the latest email-based phishing tactics - [here][quiz]. - -- Do your due diligence before purchasing Atoms. Atoms will not be transferable - at launch, so they *cannot* be bought or sold until a hard fork enables them - to be. If and when they become transferable, make sure that you’ve researched - the seller or exchange to confirm that the Atoms are coming from a - trustworthy source. - -- Neither the Tendermint team nor the Interchain Foundation will be selling - Atoms, so if you see social media posts or emails advertising a token sale - from us, they’re not real and should be avoided. Enable 2-factor - authentication, and be mindful of recovery methods used to regain access to - your most important accounts. Unprotected accounts like email, social media, - your GitHub account, the Cosmos Forum and anything in between could give an - attacker opportunities to gain foothold in your online life. If you haven’t - done so yet, start using an authenticator app or a hardware key immediately - wherever you manage your tokens. This is a simple, effective, and proven way - to reduce the risk of account theft. - -- Be skeptical of technical advice, especially advice that comes from people - you do not know in forums and on group chat channels. Familiarize yourself - with important commands, especially those that will help you carry out - high-risk actions, and consult our official documentation to make sure that - you’re not being tricked into doing something that will harm you or your - validator. And remember that the Cosmos forum, Riot channels, and Telegram - are not sources of official information or news about Cosmos. - -- Verify transactions before hitting send. Yes, those address strings are long, - but visually comparing them in blocks of 4 characters at a time may be the - difference between sending them to the right place or sending them into - oblivion. - -*If a deal pops up that [sounds too good to be true][good], or a message shows -up asking for information that should never, ever be shared with someone else, -you can always work to verify it before engaging with it by navigating to a -website or official Cosmos communication channel on your own. No one from -Cosmos, the Tendermint team or the Interchain Foundation will ever send an -email that asks for you to share any kind of account credentials or your 12 -words with us, and we will always use our official blog, Twitter and GitHub -accounts to communicate important news directly to the Cosmos community.* - -[whitepaper]: https://cosmos.network/resources/whitepaper -[fundraiser]: https://github.com/cosmos/fundraiser -[releases]: https://github.com/cosmos/cosmos-sdk/releases -[cosmos]: https://cosmos.network/launch -[social]: https://en.wikipedia.org/wiki/Social_engineering_%28security%29 -[phishing]: https://ssd.eff.org/en/module/how-avoid-phishing-attacks -[spearphishing]: https://en.wikipedia.org/wiki/Phishing#Spear_phishing -[inbox]: https://www.umass.edu/it/security/phishing-fraudulent-emails-text-messages-phone-calls -[opportunities]: https://jia.sipa.columbia.edu/weaponization-social-media-spear-phishing-and-cyberattacks-democracy -[cli]: https://hub.cosmos.network/main/delegators/delegator-guide-cli.html -[webinar]: https://register.gotowebinar.com/register/5028753165739687691 -[terms]: https://github.com/cosmos/cosmos/blob/master/fundraiser/Interchain%20Cosmos%20Contribution%20Terms%20-%20FINAL.pdf -[apache]: https://www.apache.org/licenses/LICENSE-2.0 -[gos]: https://blog.cosmos.network/announcing-incentivized-testnet-game-efe64e0956f6 -[scoring]: https://github.com/cosmos/game-of-stakes/blob/master/README.md#scoring -[file]: https://forum.cosmos.network/t/genesis-files-network-starts-vs-upgrades/1464 -[forum]: https://forum.cosmos.network/ -[riot]: https://riot.im/app/#/group/+cosmos:matrix.org -[telegram]: http://t.me/cosmosproject -[good]: https://www.psychologytoday.com/us/blog/mind-in-the-machine/201712/how-fear-is-being-used-manipulate-cryptocurrency-markets -[rc]: https://github.com/cosmos/cosmos-sdk/projects/27 -[compromised site]: https://blog.malwarebytes.com/cybercrime/2013/02/tools-of-the-trade-exploit-kits/ -[quiz]: https://phishingquiz.withgoogle.com/ - \ No newline at end of file diff --git a/docs/docs/roadmap/launch/blog-2-en.md b/docs/docs/roadmap/launch/blog-2-en.md deleted file mode 100644 index a8ec2ff6224..00000000000 --- a/docs/docs/roadmap/launch/blog-2-en.md +++ /dev/null @@ -1,74 +0,0 @@ ---- -title: The 3 Phases of the Cosmos Hub Mainnet -order: 2 ---- - - - -## Post-Mainnet Development Roadmap & Expectations for Users - -The launch of the Cosmos Hub mainnet is expected to happen in phases. Here we outline what to expect in each phase. - -## 🚨Phase I: Network Gains Stability 🚨 - -In the first phase, the network is likely to be unstable; it may experience halts or other forms of failure requiring intervention and coordination among Cosmos Hub validators and full node operators to deploy a fix. This type of failure is not unexpected while the network gains stability. - -## State Reversions and Mainnet launch - -One of the core ideologies around blockchains is immutability. This is the idea that we don't go -back and edit past state transitions. While this notion of immutability is implemented directly via consensus protocols in the software, it is ultimately upheld by social contract among participants. - -That said, the technology underlying the Cosmos Hub was intentionally developed to enable low-friction forks and rollbacks. We’ve seen the community practice these techniques numerous times on the test networks. It’s likely they will need to be used on a mainnet as well. Ultimately, they are a countervailing force to the risk of cartel takeover. - -Reverting state is often seen as highly grievous, as it compromises the network’s economic finality. Hence it should only be used in extreme conditions, as witnessed in the case of Ethereum with the DAO Hard Fork. That said, in the early days of the Cosmos Hub network, transfers will not be active, and hence the severity of state reversions will be reduced, as state transitions will be much less “economically final”. If necessary in case of bugs, the state can be exported from a past height and the network restarted, as practiced on the testnets. - -Once governance chooses to enable transfers, the importance of economic finality must be respected by the network. - -To summarize, if there are errors or vulnerabilities in the Cosmos Hub in the days before transfers are enabled, users should expect arbitrary state rollbacks even to genesis. - -Once transfers are enabled, state rollbacks will be much more difficult to justify. - -**What this means for developers:** The Cosmos mainnet launch is the first phase in which fundraiser participants will be working together to operate the software. As a decentralized application developer, you are likely a user of either the [Cosmos-SDK framework](https://cosmos.network/docs/) or [Tendermint Core](https://tendermint.com/docs/). The progress of your Cosmos-SDK or Tendermint-based application should be independent of the Cosmos Hub roadmap. However, if your project requires the use of [Inter-Blockchain Communication][blog post], you must wait until Phase III, or participate in the IBC testnets that will begin shortly. - -**What this means for users:** In this phase, we strongly recommend that you do not arrange to trade Atoms (eg. by legal contract as they will not be transferable yet) as there is the risk of state being reverted. - -You can, however, safely delegate Atoms to validators in this phase by following the CLI guideline and video tutorial linked below. Of course, in the event of a state reversion, any earned fees and inflation may be lost. Note that only `gaiad` should be used for making transactions. Voyager, the GUI for interacting with the Cosmos Hub, is currently in alpha and undergoing development. A separate announcement will be made once Voyager is safer for use. - -[CLI Guide](/delegators/delegator-guide-cli.md) 🔗 - -**Watch CLI delegation tutorial:** [Cosmos YouTube](https://www.youtube.com/watch?v=ydZw6o6Mzy0) - -## Phase II: Transfers Enabled - -**Summary:** Once mainnet is deemed sufficiently stable, bonded Atom holders will vote to decide whether or not Atom transfers should be enabled. This procedure will happen through on-chain governance. - -The best way to check on the status of governance proposals is to view them through Cosmos explorers. A list of explorers can be found on the launch page: [cosmos.network/launch](https://cosmos.network/launch). - -**What this means for users:** If the proposal is accepted and transfers are enabled, then it becomes possible to transfer Atoms. - -## Phase III: IBC Enabled - -**Summary:** In Phase III, the [IBC protocol][ibc] is released and Atom holders vote via on-chain governance on whether or not to enable it as part of the core module library within the Cosmos-SDK. - -**What this means for developers:** Application-specific blockchains that are built using the Cosmos-SDK or Tendermint BFT will be able to connect to the Hub and interoperate/compose with all of the other blockchains that are connected to it. - -**What this means for users:** You will be able to transfer various tokens and NFTs directly from one IBC-connected chain to another IBC-connected chain without going through a centralized -third-party platform. - -## Housekeeping for Validators: Submitting a `gentx` for mainnet - -1. You should have generated and secured the validator consensus key you are going to be validating under during mainnet. -2. Be prepared to sign a transaction under an address in the genesis file either from the fundraiser or Game of Stakes depending on where you received your ATOM allocation. -3. We will begin collecting Gentxs for mainnet once the recommended genesis allocations are published. - -## In Closing - -The Cosmos mission is to build bridges to connect all blockchains—to build an Internet of Blockchains. Clearly, we have a long road of development ahead of us. And after mainnet, the real work to a world of deeply integrated token economies is still ahead of us. But as John Fitzgerald Kennedy once said in the face of adversity: - -*“We choose to go to the moon...not because they are easy, but because they are hard….”* - -To the Moon 🚀 - -[blog post]: [https://blog.cosmos.network/developer-deep-dive-cosmos-ibc-5855aaf183fe] -[ibc]: [https://docs.cosmos.network/main/ibc/overview.html] - diff --git a/docs/docs/roadmap/previous-releases.md b/docs/docs/roadmap/previous-releases.md deleted file mode 100644 index 0a10067c98e..00000000000 --- a/docs/docs/roadmap/previous-releases.md +++ /dev/null @@ -1,29 +0,0 @@ - - -# Previous Releases - -The following table below, shows the versions of the main dependencies. - -| Upgrade Name | Date | Height | Chain Identifier | Tm | Cosmos SDK | Gaia | IBC | -|---------------------|---------------|-----------|---------------|------------|------------|--------------------------|--------------------------| -| Mainnet Launch | 13/03/19 | 0 | `cosmoshub-1` | [v0.31.x](https://github.com/tendermint/tendermint/releases/tag/v0.31.11) | [v0.33.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.33.2) | _Included in Cosmos SDK_ | n/a | -| [Security Hard Fork](https://forum.cosmos.network/t/critical-cosmossdk-security-advisory-updated/2211) | 21/04/19 | 482,100 | `cosmoshub-1` | [v0.31.x](https://github.com/tendermint/tendermint/releases/tag/v0.31.11) | [v0.34.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.34.6) | _Included in Cosmos SDK_) | n/a | -| Upgrade #1 | 21/01/20 | 500043 | `cosmoshub-2` | [v0.31.x](https://github.com/tendermint/tendermint/releases/tag/v0.31.11) | [v0.34.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.34.10) | _Included in Cosmos SDK_) | n/a | -| Upgrade #2 | 07/08/20 | 2902000 | `cosmoshub-3` | [v0.32.x](https://github.com/tendermint/tendermint/releases/tag/v0.32.14) | [v0.37.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.37.15) | [v2.0.x](https://github.com/cosmos/gaia/releases/tag/v2.0.14) | n/a | -| [Stargate](https://github.com/cosmos/gaia/releases/tag/v4.0.0) | 18/02/21 | 5200791 | `cosmoshub-4` | [v0.34.x](https://github.com/tendermint/tendermint/releases/tag/v0.34.3) | [v0.40.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.40.1) | [v4.0.x](https://github.com/cosmos/gaia/releases/tag/v4.0.6) | _Included in Cosmos SDK_ | -| Security Hard Fork | ? | ? | `cosmoshub-4` | [v0.34.x](https://github.com/tendermint/tendermint/releases/tag/v0.34.8) | [v0.41.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.41.4) | [v4.2.x](https://github.com/cosmos/gaia/releases/tag/v4.2.1) | _Included in Cosmos SDK_ | -| [Delta (Gravity DEX)](https://github.com/cosmos/gaia/releases/tag/v5.0.0) | 13/07/21 | 6910000 | `cosmoshub-4` | [v0.34.x](https://github.com/tendermint/tendermint/releases/tag/v0.34.13) | [v0.42.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.42.10) | [v5.0.x](https://github.com/cosmos/gaia/releases/tag/v5.0.8) | _Included in Cosmos SDK_ | -| [Vega v6](https://github.com/cosmos/gaia/releases/tag/v6.0.0) | 13/12/21 | 8695000 | `cosmoshub-4` | [v0.34.x](https://github.com/tendermint/tendermint/releases/tag/v0.34.14) | [v0.44.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.5) | [v6.0.x](https://github.com/cosmos/gaia/releases/tag/v6.0.4) | [v2.0.x](https://github.com/cosmos/ibc-go/releases/tag/v2.0.3) | -| [Theta v7](https://github.com/cosmos/gaia/releases/tag/v7.0.0) | 12/04/22 | 10085397 | `cosmoshub-4` | [v0.34.x](https://github.com/tendermint/tendermint/releases/tag/v0.34.14) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.1) | [v7.0.x](https://github.com/cosmos/gaia/releases/tag/v7.0.0) | [v3.0.x](https://github.com/cosmos/ibc-go/releases/tag/v3.0.0) | -| [Rho v8](https://github.com/cosmos/gaia/releases/tag/v8.0.0) | 16/02/23 | 14099412 | `cosmoshub-4` | [v0.34.x](https://github.com/informalsystems/tendermint/releases/tag/v0.34.24) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.12) | [v8.0.x](https://github.com/cosmos/gaia/releases/tag/v8.0.0) | [v3.4.x](https://github.com/cosmos/ibc-go/releases/tag/v3.4.0) | -| [Lambda v9](https://github.com/cosmos/gaia/releases/tag/v9.0.0) | 15/03/23 | 14470501 | `cosmoshub-4` | [v0.34.x](https://github.com/informalsystems/tendermint/releases/tag/v0.34.25) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.13-ics) | [v9.0.x](https://github.com/cosmos/gaia/releases/tag/v9.0.0) | [v4.2.x](https://github.com/cosmos/ibc-go/releases/tag/v4.2.0) | -| [v10](https://github.com/cosmos/gaia/releases/tag/v10.0.0) | 21/06/23 | 15816200 | `cosmoshub-4` | [v0.34.x](https://github.com/cometbft/cometbft/releases/tag/v0.34.28) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.16-ics) | [v10.0.x](https://github.com/cosmos/gaia/releases/tag/v10.0.0) | [v4.4.x](https://github.com/cosmos/ibc-go/releases/tag/v4.4.0) | -| [v11](https://github.com/cosmos/gaia/releases/tag/v11.0.0) | 16/08/23 | 16596000 | `cosmoshub-4` | [v0.34.x](https://github.com/cometbft/cometbft/releases/tag/v0.34.29) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.16-ics) | [v11.x](https://github.com/cosmos/gaia/releases/tag/v11.0.0) | [v4.4.x](https://github.com/cosmos/ibc-go/releases/tag/v4.4.2) | -| [v12](https://github.com/cosmos/gaia/releases/tag/v12.0.0) | 13/09/23 | 16985500 | `cosmoshub-4` | [v0.34.x](https://github.com/cometbft/cometbft/releases/tag/v0.34.29) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.16-ics) | [v12.x](https://github.com/cosmos/gaia/releases/tag/v12.0.0) | [v4.4.x](https://github.com/cosmos/ibc-go/releases/tag/v4.4.2) | -| [v13](https://github.com/cosmos/gaia/releases/tag/v13.0.0) | 11/10/23 | 17380000 | `cosmoshub-4` | [v0.34.x](https://github.com/cometbft/cometbft/releases/tag/v0.34.29) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.16-ics-lsm) | [v13.x](https://github.com/cosmos/gaia/releases/tag/v13.0.0) | [v4.4.x](https://github.com/cosmos/ibc-go/releases/tag/v4.4.2) | -| [v14](https://github.com/cosmos/gaia/releases/tag/v14.1.0) | 11/10/23 | 18262000 | `cosmoshub-4` | [v0.34.x](https://github.com/cometbft/cometbft/releases/tag/v0.34.29) | [v0.45.x](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.45.16-ics-lsm) | [v14.x](https://github.com/cosmos/gaia/releases/tag/v14.0.0) | [v4.4.x](https://github.com/cosmos/ibc-go/releases/tag/v4.4.2) | diff --git a/docs/docs/validators/README.md b/docs/docs/validators/README.md index 5e2f3c98c90..12825f1206f 100644 --- a/docs/docs/validators/README.md +++ b/docs/docs/validators/README.md @@ -5,10 +5,10 @@ order: 1 This folder contains documentation relevant to validators of the Cosmos Hub and other `gaia` blockchains. -- [Validator Overview](/validators/overview.mdx) -- [Setting Up a Validator for Cosmos Hub Mainnet](/validators/validator-setup.md) -- [Validator FAQ](/validators/validator-faq.md) -- [Validator Security Notice](/validators/security.md) +- [Validator Overview](/validators/overview) +- [Setting Up a Validator for Cosmos Hub Mainnet](/validators/validator-setup) +- [Validator FAQ](/validators/validator-faq) +- [Validator Security Notice](/validators/security) - Key Management Systems - - [Intro to KMS](/validators/kms/kms.md) - - [KMS + Ledger](/validators/kms/kms_ledger.md) + - [Intro to KMS](/validators/kms) + - [KMS + Ledger](/validators/kms/kms_ledger) diff --git a/docs/docs/validators/overview.mdx b/docs/docs/validators/overview.mdx index 96c7dd30bbf..1984e601405 100644 --- a/docs/docs/validators/overview.mdx +++ b/docs/docs/validators/overview.mdx @@ -10,11 +10,11 @@ import { currentParams } from '@site/docs/governance/current-parameters.js'; The [Cosmos Hub](/validators/README.md) is based on [CometBFT](https://docs.cometbft.com/v0.34/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. -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 validators, see Proposal , 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 validator candidates with the most voting power are the current Cosmos validators. +Validator candidates can bond their own ATOM and have ATOM ["delegated"](/delegators/delegator-guide-cli), or staked, to them by token holders. The Cosmos Hub has validators, see Proposal , 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 validator candidates with the most voting power are the current Cosmos validators. 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). -If validators double sign or are offline for an [extended period](/validators/validator-faq.md#what-are-the-slashing-conditions), their staked ATOM (including ATOM of users that delegated to them) can be slashed. The penalty depends on the severity of the violation. +If validators double sign or are offline for an [extended period](/validators/validator-faq#what-are-the-slashing-conditions), their staked ATOM (including ATOM of users that delegated to them) can be slashed. The penalty depends on the severity of the violation. ## Hardware @@ -22,7 +22,7 @@ For validator key management, validators must set up a physical operation that i Validators are expected to equip their datacenter location with redundant power, connectivity, and storage backups. Expect to have several redundant networking boxes for fiber, firewall, and switching and then small servers with redundant hard drive and failover. -You can find the minimum hardware requirements on the instructions for [joining the Cosmos Hub mainnet](/hub-tutorials/join-mainnet.md). As the network grows, bandwidth, CPU, and memory requirements rise. Large hard drives are recommended for storing years of blockchain history, as well as significant RAM to process the increasing amount of transactions. +You can find the minimum hardware requirements on the instructions for [joining the Cosmos Hub mainnet](/hub-tutorials/join-mainnet). As the network grows, bandwidth, CPU, and memory requirements rise. Large hard drives are recommended for storing years of blockchain history, as well as significant RAM to process the increasing amount of transactions. ## Create a Validator Website diff --git a/docs/docs/validators/validator-faq.md b/docs/docs/validators/validator-faq.md index dd15d42fa83..3bed91ee124 100644 --- a/docs/docs/validators/validator-faq.md +++ b/docs/docs/validators/validator-faq.md @@ -12,7 +12,7 @@ This is work in progress. Mechanisms and values are susceptible to change. ### What is a Cosmos validator? -The [Cosmos Hub](../getting-started/what-is-gaia.md) is based on [CometBFT](https://docs.cometbft.com/v0.34/introduction/what-is-cometbft) that relies on a set of validators to secure the network. The role of validators is to run a full node and participate in consensus by broadcasting votes that contain cryptographic signatures signed by the validator's private key. Validators commit new blocks in the blockchain and receive revenue in exchange for their work. Validators must also participate in governance by voting on proposals. Validators are weighted according to their total stake. +The [Cosmos Hub](/getting-started/what-is-gaia) is based on [CometBFT](https://docs.cometbft.com/v0.34/introduction/what-is-cometbft) that relies on a set of validators to secure the network. The role of validators is to run a full node and participate in consensus by broadcasting votes that contain cryptographic signatures signed by the validator's private key. Validators commit new blocks in the blockchain and receive revenue in exchange for their work. Validators must also participate in governance by voting on proposals. Validators are weighted according to their total stake. ### What is staking? @@ -32,11 +32,11 @@ You can find more details about the requirements in the [Joining Mainnet Tutoria ### What is a delegator? -Delegators are ATOM holders who cannot, or do not want to, run a validator themselves. ATOM holders can delegate ATOM to a validator and obtain a part of their revenue in exchange. For details on how revenue is distributed, see [What is the incentive to stake?](#what-is-the-incentive-to-stake?) and [What are validators commission?](#what-are-validators-commission?) in this document. +Delegators are ATOM holders who cannot, or do not want to, run a validator themselves. ATOM holders can delegate ATOM to a validator and obtain a part of their revenue in exchange. For details on how revenue is distributed, see [What is the incentive to stake?](/validators/validator-faq#what-is-the-incentive-to-stake) and [What are validators commission?](/validators/validator-faq#what-is-a-validator-commission) in this document. Because delegators share revenue with their validators, they also share risks. If a validator misbehaves, each of their delegators are partially slashed in proportion to their delegated stake. This penalty is one of the reasons why delegators must perform due diligence on validators before delegating. Spreading their stake over multiple validators is another layer of protection. -Delegators play a critical role in the system, as they are responsible for choosing validators. Being a delegator is not a passive role. Delegators must actively monitor the actions of their validators and participate in governance. For details on being a delegator, read the [Delegator FAQ](https://hub.cosmos.network/main/delegators/delegator-faq.html). +Delegators play a critical role in the system, as they are responsible for choosing validators. Being a delegator is not a passive role. Delegators must actively monitor the actions of their validators and participate in governance. For details on being a delegator, read the [Delegator FAQ](https://hub.cosmos.network/delegators/delegator-faq). ## Becoming a Validator diff --git a/docs/docs/validators/validator-setup.md b/docs/docs/validators/validator-setup.md index 56504b966b4..d8d0f3051ad 100644 --- a/docs/docs/validators/validator-setup.md +++ b/docs/docs/validators/validator-setup.md @@ -4,22 +4,22 @@ order: 2 --- :::tip -We suggest you try out joining a public testnet first. Information on how to join the most recent testnet can be found [here](/hub-tutorials/join-testnet.md). +We suggest you try out joining a public testnet first. Information on how to join the most recent testnet can be found [here](/hub-tutorials/join-testnet). ::: -Before setting up a validator node, make sure to have completed the [Joining Mainnet](/hub-tutorials/join-mainnet.md) guide. +Before setting up a validator node, make sure to have completed the [Joining Mainnet](/hub-tutorials/join-mainnet) guide. -If you plan to use a KMS (key management system), you should go through these steps first: [Using a KMS](/validators/kms/kms.md). +If you plan to use a KMS (key management system), you should go through these steps first: [Using a KMS](/validators/kms/kms). ## What is a Validator? -[Validators](/validators/overview.mdx) are responsible for committing new blocks to the blockchain through an automated voting process. A validator's stake is slashed if they become unavailable or sign blocks at the same height. Because there is a chance of slashing, we suggest you read about [Sentry Node Architecture](/validators/validator-faq.md#how-can-validators-protect-themselves-from-denial-of-service-attacks) to protect your node from DDOS attacks and to ensure high-availability. +[Validators](/validators/overview) are responsible for committing new blocks to the blockchain through an automated voting process. A validator's stake is slashed if they become unavailable or sign blocks at the same height. Because there is a chance of slashing, we suggest you read about [Sentry Node Architecture](/validators/validator-faq#how-can-validators-protect-themselves-from-denial-of-service-attacks) to protect your node from DDOS attacks and to ensure high-availability. :::warning -If you want to become a validator for the Hub's `mainnet`, you should learn more about [security](/validators/security.md). +If you want to become a validator for the Hub's `mainnet`, you should learn more about [security](/validators/security). ::: -The following instructions assume you have already [set up a full-node](/hub-tutorials/join-mainnet.md) and are synchronised to the latest blockheight. +The following instructions assume you have already [set up a full-node](/hub-tutorials/join-mainnet) and are synchronised to the latest blockheight. ## Create Your Validator