6a03586074
## Description ### Issue Some values (like chain ID) were being leaked from the previous block/initialization into PrepareProposal and ProcessProposal, these values are only available if: 1. The node has never been stopped since the genesis block (as these values are set on `InitChain`) 2. The node has already commited a block (as the previous header was being used for the new state of prepare and process proposal). So if a node is restarted, during the first prepare and process proposal these values won't be populated, and that will cause issues if they are being used. ### Solution Remove any previous header information from a previous block in the prepare and process proposal contexts, making things consistent at every height. - Added ChainID to baseapp - Use an empty header in Commit() with only the chain id set - Fix context for prepare and process proposal Closes: #15269 --- ### Author Checklist *All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.* I have... - [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] added `!` to the type prefix if API or client breaking change - [ ] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting)) - [ ] provided a link to the relevant issue or specification - [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/docs/building-modules) - [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing) - [ ] added a changelog entry to `CHANGELOG.md` - [ ] included comments for [documenting Go code](https://blog.golang.org/godoc) - [ ] updated the relevant documentation or specification - [ ] reviewed "Files changed" and left comments if necessary - [ ] confirmed all CI checks have passed ### Reviewers Checklist *All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.* I have... - [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title - [ ] confirmed `!` in the type prefix if API or client breaking change - [ ] confirmed all author checklist items have been addressed - [ ] reviewed state machine logic - [ ] reviewed API design and naming - [ ] reviewed documentation is accurate - [ ] reviewed tests and test coverage - [ ] manually tested (if applicable) |
||
|---|---|---|
| .. | ||
| params | ||
| simd | ||
| app_config.go | ||
| app_test.go | ||
| app_v2.go | ||
| app.go | ||
| export.go | ||
| genesis_account_test.go | ||
| genesis_account.go | ||
| genesis.go | ||
| go.mod | ||
| go.sum | ||
| README.md | ||
| sim_bench_test.go | ||
| sim_test.go | ||
| sonar-project.properties | ||
| test_helpers.go | ||
| testutil_network_test.go | ||
| upgrades.go | ||
| sidebar_position |
|---|
| 1 |
SimApp
SimApp is an application built using the Cosmos SDK for testing and educational purposes.
Running testnets with simd
If you want to spin up a quick testnet with your friends, you can follow these steps. Unless otherwise noted, every step must be done by everyone who wants to participate in this testnet.
-
From the root directory of the Cosmos SDK repository, run
$ make build. This will build thesimdbinary inside a newbuilddirectory. The following instructions are run from inside thebuilddirectory. -
If you've run
simdbefore, you may need to reset your database before starting a new testnet. You can reset your database with the following command:$ ./simd comet unsafe-reset-all. -
$ ./simd init [moniker] --chain-id [chain-id]. This will initialize a new working directory at the default location~/.simapp. You need to provide a "moniker" and a "chain id". These two names can be anything, but you will need to use the same "chain id" in the following steps. -
$ ./simd keys add [key_name]. This will create a new key, with a name of your choosing. Save the output of this command somewhere; you'll need the address generated here later. -
$ ./simd genesis add-genesis-account [key_name] [amount], wherekey_nameis the same key name as before; andamountis something like10000000000000000000000000stake. -
$ ./simd genesis gentx [key_name] [amount] --chain-id [chain-id]. This will create the genesis transaction for your new chain. Hereamountshould be at least1000000000stake. If you provide too much or too little, you will encounter an error when starting your node. -
Now, one person needs to create the genesis file
genesis.jsonusing the genesis transactions from every participant, by gathering all the genesis transactions underconfig/gentxand then calling$ ./simd genesis collect-gentxs. This will create a newgenesis.jsonfile that includes data from all the validators (we sometimes call it the "super genesis file" to distinguish it from single-validator genesis files). -
Once you've received the super genesis file, overwrite your original
genesis.jsonfile with the new supergenesis.json. -
Modify your
config/config.toml(in the simapp working directory) to include the other participants as persistent peers:# Comma separated list of nodes to keep persistent connections to persistent_peers = "[validator_address]@[ip_address]:[port],[validator_address]@[ip_address]:[port]"You can find
validator_addressby running$ ./simd comet show-node-id. The output will be the hex-encodedvalidator_address. The defaultportis 26656. -
Now you can start your nodes:
$ ./simd start.
Now you have a small testnet that you can use to try out changes to the Cosmos SDK or CometBFT!
NOTE: Sometimes creating the network through the collect-gentxs will fail, and validators will start
in a funny state (and then panic). If this happens, you can try to create and start the network first
with a single validator and then add additional validators using a create-validator transaction.