Skip to content

Commit

Permalink
Updates to the message types section along with some other minor upda…
Browse files Browse the repository at this point in the history
…tes (#492)
  • Loading branch information
emperorjm authored Jun 10, 2024
1 parent 18407e8 commit a35a2d6
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions content/3.community/4.governance/1.governance.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,7 @@ You will need **CONST** Testnet tokens to create the proposal on Testnet. There

## Message types

To find the correct message format, you should refer to the proto file of the relevant module. This involves reviewing the required fields and their types, then mirroring this structure in the `messages` JSON array, as demonstrated in the provided example. For instance, the `MsgSend` message from the Cosmos SDK `Bank` module is used in the example. To locate the necessary fields, visit the Cosmos SDK repository, navigate to the release version installed by the Archway protocol, and explore the proto folder for the transaction message details. The `MsgSend` details are available at: [Cosmos SDK GitHub repository](https://github.com/cosmos/cosmos-sdk/blob/v0.47.7/proto/cosmos/bank/v1beta1/tx.proto#L39-L53). For archway custom modules these proto files will be found [here](https://github.com/archway-network/archway/tree/main/proto/archway).
To find the correct message format, you should refer to the proto file of the relevant module. This involves reviewing the required fields and their types, then mirroring this structure in the `messages` JSON array. For instance, the `MsgSend` message from the Cosmos SDK `Bank` module. To locate the necessary fields, visit the Cosmos SDK repository, navigate to the release version installed by the Archway protocol, and explore the proto folder for the transaction message details. For Cosmos SDK `v0.47.7` the `MsgSend` details are available at: [Cosmos SDK GitHub repository](https://github.com/cosmos/cosmos-sdk/blob/v0.47.7/proto/cosmos/bank/v1beta1/tx.proto#L39-L53). For archway custom modules these proto files will be found [here](https://github.com/archway-network/archway/tree/main/proto/archway).

Here is an example of the `MsgSend` structure:

Expand Down Expand Up @@ -156,7 +156,7 @@ The previous solution was quite restrictive, but now a proposal can execute any

### Draft proposal

The protocol has established a process to assist you in drafting the proposal message needed for each module, which will be used by the `submit-proposal` command. This message is stored in a `draft_proposal.json` file. Additionally, a `draft_metadata.json` file is generated, which is intended to be uploaded to `IPFS` and then added to the `metadata` attribute in the `draft_proposal.json` file file.
The protocol has established a process to assist you in drafting the proposal message needed for each module, which will be used by the `submit-proposal` command. This message is stored in a `draft_proposal.json` file. Additionally, a `draft_metadata.json` file is generated, which is intended to be uploaded to `IPFS` and then the `CID` of the `IPFS` resource added to the `metadata` attribute in the `draft_proposal.json` file to allow for capturing the details of the metadata.

You should execute the following command to start the draft proposal process:

Expand Down Expand Up @@ -388,7 +388,7 @@ Mainnet
#desc0
::highlight-card
```shell
$ archwayd tx gov submit-proposal path/to/draft_proposal.json --from mywallet --node https://rpc.mainnet.archway.io:443 --chain-id archway-1 --gas auto --gas-prices $(archwayd q rewards estimate-fees 1 --node 'https://rpc.mainnet.archway.io:443' --output json | jq -r '.gas_unit_price | (.amount + .denom)') --gas-adjustment 1.3
$ archwayd tx gov submit-proposal path/to/draft_proposal.json --from <mywallet> --node https://rpc.mainnet.archway.io:443 --chain-id archway-1 --gas auto --gas-prices $(archwayd q rewards estimate-fees 1 --node 'https://rpc.mainnet.archway.io:443' --output json | jq -r '.gas_unit_price | (.amount + .denom)') --gas-adjustment 1.3
```
::

Expand All @@ -398,17 +398,17 @@ Constantine
#desc1
::highlight-card
```shell
$ archwayd tx gov submit-proposal path/to/draft_proposal.json --from mywallet --node https://rpc.constantine.archway.io:443 --chain-id constantine-3 --gas auto --gas-prices $(archwayd q rewards estimate-fees 1 --node 'https://rpc.constantine.archway.io:443' --output json | jq -r '.gas_unit_price | (.amount + .denom)') --gas-adjustment 1.3
$ archwayd tx gov submit-proposal path/to/draft_proposal.json --from <mywallet> --node https://rpc.constantine.archway.io:443 --chain-id constantine-3 --gas auto --gas-prices $(archwayd q rewards estimate-fees 1 --node 'https://rpc.constantine.archway.io:443' --output json | jq -r '.gas_unit_price | (.amount + .denom)') --gas-adjustment 1.3
```
::
::

## Depositing funds after a proposal has been submitted

If you've submitted a proposal without yet meeting the minimum token deposit, there's no need to worry! You still have time to deposit additional tokens to advance your proposal to the voting stage if the deposit time period has not elapsed. For instance, you can execute the following command:
If you've submitted a proposal without yet meeting the minimum token deposit, there's no need to worry! You still have time to deposit additional tokens to advance your proposal to the voting stage if the deposit time period has not elapsed. For instance, you can execute the following command to add a deposit:

```bash
archwayd tx gov deposit 8 10000000000000aarch --from mywallet --node https://rpc.mainnet.archway.io:443
archwayd tx gov deposit 8 10000000000000aarch --from <mywallet> --node https://rpc.mainnet.archway.io:443 --chain-id archway-1 --gas auto --gas-prices $(archwayd q rewards estimate-fees 1 --node 'https://rpc.mainnet.archway.io:443' --output json | jq -r '.gas_unit_price | (.amount + .denom)') --gas-adjustment 1.3
```

Where `8` is the proposal ID and `10000000000000aarch` is the amount to be deposited.
Expand Down

0 comments on commit a35a2d6

Please sign in to comment.