1559: https://res.cloudinary.com/stargaze/image/upload/w_700/b5ij1wrgjzmzcivljffz.jpg 1980: https://res.cloudinary.com/stargaze/image/upload/w_700/u5swhukgqofrwrqj7vyp.jpg 2979: https://res.cloudinary.com/stargaze/image/upload/w_700/ouw1ndsrjjbhe0btkn6u.jpg 3105: https://res.cloudinary.com/stargaze/image/upload/w_700/ay895kdyocd5ublmlukw.jpg 3797: https://res.cloudinary.com/stargaze/image/upload/w_700/ucjpnj0fh1segz3fuwqf.jpg 3799: https://res.cloudinary.com/stargaze/image/upload/w_700/plbs1zrqrdmizjpo8mnb.jpg 8842: https://res.cloudinary.com/stargaze/image/upload/w_700/badkx397up5ww8epsldm.jpg 8961: https://res.cloudinary.com/stargaze/image/upload/w_700/snav2rleap7jhvzm8pyo.jpg 9045: https://res.cloudinary.com/stargaze/image/upload/w_700/w91bnc1hjm6yfjdvpngz.jpg 8602: https://res.cloudinary.com/stargaze/image/upload/w_700/are9u3qwmgvf78mzwawf.jpg
Last changed by  
 
billy rennekamp
169

Read more

Formatting a proposal

Begin by writing out the proposal description in markdown. Confirm that it's under the charlimit (5k until Theta and 10k after). Then generate the proposal with --offline so that it is not signed but the json is created. Pipe it into a file like unsigned.json. You can leave the description empty or with dummy text here because the CLI will try to escape the chars but likely not the way you want. > gaiad tx gov submit-proposal software-upgrade v7-Theta \ --title v7-Theta \ --deposit 50000uatom \ --upgrade-height 10085397 \ --upgrade-info '{"binaries":{"linux/amd64":"https://github.com/cosmos/gaia/releases/download/v7.0.0/gaiad-v7.0.0-linux-amd64?checksum=sha256:dc0e5b6690a55f0f1c41ad96f068049e25d9e85d53c0587284b7f1a1f9a51545","linux/arm64":"https://github.com/cosmos/gaia/releases/download/v7.0.0/gaiad-v7.0.0-linux-arm64?checksum=sha256:994f67ec8134504ae032a1ae58caf769b5a9a1581a38705efd94ab654a7f6173","darwin/amd64":"https://github.com/cosmos/gaia/releases/download/v7.0.0/gaiad-v7.0.0-darwin-amd64?checksum=sha256:2b7425b27e1c04877f0e9230f1657bee1b3274b73bee8f550a290cc505444dbf","windows/amd64":"https://github.com/cosmos/gaia/releases/download/v7.0.0/gaiad-v7.0.0-windows-amd64.exe?checksum=sha256:1362b026e942cc16ab2b7f35a3ff39fb9075dcde70570635485d4b1866e1d036"}}' \ --description "#test\r\n\r##test" \

5/1/2022
for vega upgrade

for vega-upgrade gaiad tx gov submit-proposal software-upgrade Vega \ --title Vega \ --deposit 500000uatom \ --upgrade-height 8695000 \ --upgrade-info '{"binaries":{"linux/amd64":"https://github.com/cosmos/gaia/releases/download/v6.0.0/gaiad-v6.0.0-linux-amd64?checksum=sha256:d9b4391065a338107ca240f29539d62572fe1e85a6c455576afc5e93dba7f402","linux/arm64":"https://github.com/cosmos/gaia/releases/download/v6.0.0/gaiad-v6.0.0-linux-arm64?checksum=sha256:e348259fb9ca5d516a8754ea1f15255ef32e7656e79d52a87616edb16f0a7343","darwin/amd64":"https://github.com/cosmos/gaia/releases/download/v6.0.0/gaiad-v6.0.0-darwin-amd64?checksum=sha256:e0de182c098ab68d3ef4bab8a3d12aca100b9f1d18d873d66e82ec2c187a1735","windows/amd64":"https://github.com/cosmos/gaia/releases/download/v6.0.0/gaiad-v6.0.0-windows-amd64.exe?checksum=sha256:713cb6c1a7ef555d5ed64f036f65b039b44b76f314855e2f7d2a5330568e6100"}}' \ --description "This on-chain upgrade governance proposal is to adopt gaia v6.0.0 which includes a number of updates, fixes and new modules. By voting YES to this proposal, you approve of adding these updates to the Cosmos Hub.\n\n### Background\n\nSince the last upgrade at height 6910000 there have been a number of updates, fixes and new modules added to the Cosmos SDK, IBC and Tendermint. The following updates are included in gaia v6.0.0:\n * Bump [Cosmos-SDK](https://github.com/cosmos/cosmos-sdk) to [v0.44.3](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.3) which notably includes fixes for the vesting accounts and two new modules outlined below. For a full list of updates in Cosmos-SDK v0.44.3 please see the [CHANGELOG.md](https://github.com/cosmos/cosmos-sdk/blob/release/v0.44.x/CHANGELOG.md#v0443---2021-10-21)\n * Add the [authz](https://github.com/cosmos/cosmos-sdk/tree/v0.44.3/x/authz/spec) module to the Cosmos Hub. `x/authz` is an implementation of a Cosmos SDK module, per [ADR 30](https://github.com/cosmos/cosmos-sdk/blob/v0.44.3/docs/architecture/adr-030-authz-module.md), that allows granting arbitrary privileges from one account (the granter) to another account (the grantee). Authorizations must be granted for a particular Msg service method one by one using an implementation of the `Authorization` interface.\n * Add the [feegrant](https://github.com/cosmos/cosmos-sdk/tree/v0.44.3/x/feegrant/spec) module to the Cosmos Hub. This module allows accounts to grant fee allowances and to use fees from their accounts. Grantees can execute any transaction without the need to maintain sufficient fees.\n * **NOTICE** It's imortant to highlight [PR #10041](https://github.com/cosmos/cosmos-sdk/pull/10041) which impacts **WALLETS AND EXCHANGES**. This update has removed the deprecated the legacy REST endpoints for broadcast & encode. **This means `POST /tx` and `POST /txs/encode` no longer work**. Please see the [REST Endpoints Migration guide](https://docs.cosmos.network/master/migrations/rest.html) to migrate to the new REST endpoints.\n * Add [IBC](https://github.com/cosmos/ibc-go) as a standalone module from the Cosmos SDK using version [v2.0.0](https://github.com/cosmos/ibc-go/releases/tag/v2.0.0). See the [CHANGELOG.md](https://github.com/cosmos/ibc-go/blob/v2.0.0/CHANGELOG.md) for details.\n * Please note that the governance parameter for `MaxExpectedBlockDelay` is set to 30 seconds. This means if a connection is opened with a packet delay of 1 minute, it requires 2 blocks to be committed after the consensus state is submitted before the packet can be processed.\n * Add [packet-forward-middleware](https://github.com/strangelove-ventures/packet-forward-middleware) [v1.0.1](https://github.com/strangelove-ventures/packet-forward-middleware/releases/tag/v1.0.1) as per [Proposal #56](https://www.mintscan.io/cosmos/proposals/56) prepared and tested by [Strangelove Ventures](https://www.strangelove.ventures/). This feature allows multi-hop IBC transfer messages so that a user can send tokens from chain A to chain C via chain B.\n * Bump [Liquidity](https://github.com/gravity-devs/liquidity) module to [v1.4.2](https://github.com/Gravity-Devs/liquidity/releases/tag/v1.4.2) to ensure compatibility with Cosmos-SDK.\n\n### Ready for Production\n\nThese changes have been extensively tested by various Cosmos Core Contributor teams including [Hypha Co-Op](https://hypha.coop/), [Informal Systems Co-Op](https://informal.systems/), [Interchain GmbH](https://interchain.berlin/), [Regen Network](https://regen.network/), [Strangelove Ventures](https://strangelove.ventures/), [Tendermint Inc](https://tendermint.com/) and more. The release candidate for this update was run as a local testnet and a public testnet with a successful upgrade; documentation can be found [here](https://github.com/cosmos/vega-test).\n\n### On-Chain Upgrade Process\n\nWhen the network reaches the halt height, the state machine program of the Cosmos Hub will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. There is also a newer method that relies on [Cosmovisor](https://github.com/cosmos/cosmos-sdk/tree/master/cosmovisor) to swap the binaries automatically. Cosmovisor also includes the ability to download the binaries automatically before swapping them. Instructions specific to the upgrade can be found [here](https://github.com/cosmos/gaia/blob/main/docs/gaia-tutorials/upgrade-node.md). To test a simulated local upgrade please see the [local testnet documentation](https://github.com/cosmos/vega-test/blob/master/local-testnet/README.md). Because it is an onchain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.\n" \ --fees 300uatom \ --gas auto \ --from deploy \

3/16/2022
ICA demo

This is the script that needs to be run on both servers, except the chain id needs to be changed on the second server Introduction Alice is on chain test-1 and has 100 tokens bob is on chain test-2 does not have any token. alice knows an faucet user on chain test-2, so she can sometimes ask faucet user to send her some tokens. now, alice wants to send some native token of chain test-2 to bob.

1/25/2022
Billy's Cosmos Hub Hack Solution

Task 1 # configure gaiad so that there is relevant chain info in two different directories: gaiad config chain-id test-1 gaiad config node http://165.22.23.73:26657 gaiad config keyring-backend test gaiad config chain-id test-2 --home ~/.gaiad2 gaiad config node http://164.90.226.126:26657 --home ~/.gaiad2

12/22/2021
Read more from billy rennekamp
Published on HackMD