1c6e267964
* add zeroed custom fields check to tm client * remove custom fields function from x/upgrade and fix tests * use []byte in x/upgrade, move abci to 02-client * remove x/ibc from types * whoops, delete testing files * fix upgrade tests * fix tm tests * fix tests * update CHANGELOG * revert proto breakage, use reserved field cc @amaurym * add IBC Upgrade Proposal type * remove IBC from upgrade types * add IBC upgrade logic to 02-client * fix all tests for x/upgrade * Add CLI for IBC Upgrade Proposal * Update x/ibc/core/02-client/types/proposal_test.go Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com> * add gRPC for upgraded client state * test fixes * add HandleUpgradeProposal tests * update docs and remove unnecessary code * self review bug and test fixes * neatness * construct empty rest handler * fix tests * fix stringer tests * Update docs/core/proto-docs.md Co-authored-by: Christopher Goes <cwgoes@pluranimity.org> * add key in ibc store tracking ibc upgrade heights Add a new Key to the IBC client store to track the IBC Upgrade Height. This allows IBC upgrades to correctly remove old IBC upgrade states * update abci and tests * revert key storage after discussion with @AdityaSripal Revert using a key to track IBC upgrades. By clearing any IBC state using an old plan in ScheduleUpgrade, IBC upgrades do not need to be tracked by IBC. This reduces code complexity and reduces potential for bugs. * clear IBC states on cancelled upgrades Co-authored-by: Federico Kunze <31522760+fedekunze@users.noreply.github.com> Co-authored-by: Christopher Goes <cwgoes@pluranimity.org> |
||
---|---|---|
.. | ||
helpers | ||
params | ||
simd | ||
README.md | ||
app.go | ||
app_test.go | ||
config.go | ||
encoding.go | ||
export.go | ||
genesis.go | ||
genesis_account.go | ||
genesis_account_test.go | ||
sim_bench_test.go | ||
sim_test.go | ||
state.go | ||
test_helpers.go | ||
types.go | ||
utils.go | ||
utils_test.go |
README.md
order |
---|
false |
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.
-
$ make build
. This will build thesimd
binary and install it in your Cosmos SDK repo, inside a newbuild
directory. The following instructions are run from inside that directory. -
If you've run
simd
before, you may need to reset your database before starting a new testnet:$ ./simd unsafe-reset-all
-
$ ./simd init [moniker]
. This will initialize a new working directory, by default at~/.simapp
. You need a provide a "moniker," but it doesn't matter what it is. -
$ ./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 add-genesis-account $(simd keys show [key_name] -a) [amount]
, wherekey_name
is the same key name as before; andamount
is something like10000000000000000000000000stake
. -
$ ./simd gentx [key_name] [amount] --chain-id [chain-id]
. This will create the genesis transaction for your new chain. -
Now, one person needs to create the genesis file
genesis.json
using the genesis transactions from every participant, by gathering all the genesis transactions underconfig/gentx
and then calling./simd collect-gentxs
. This will create a newgenesis.json
file 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.json
file 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 address
by running./simd tendermint show-node-id
. (It will be hex-encoded.) By default,port
is 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 Tendermint!
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.