Skip to main content

Submit a Proposal

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.

  1. (Optional) Hosting supplementary materials for your proposal with IPFS (InterPlanetary File System)
  2. Formatting the JSON file for the governance proposal transaction that will be on-chain
  3. Sending the transaction that submits your governance proposal on-chain

Hosting supplementary materials​

In general we try to minimize the amount of data pushed to the blockchain. Hence, detailed documentation about a proposal is usually hosted on a separate censorship resistant data-hosting platform, like IPFS.

Once you have drafted your proposal, ideally as a Markdown file, you can upload it to the IPFS network:

  1. either by running an IPFS node and the IPFS software, or
  2. using a service such as https://pinata.cloud

Ensure that you "pin" the file so that it continues to be available on the network. You should get a URL like this: https://ipfs.io/ipfs/QmbkQNtCAdR1CNbFE8ujub2jcpwUcmSRpSCg8gVWrTHSWD The value QmbkQNtCAdR1CNbFE8ujub2jcpwUcmSRpSCg8gVWrTHSWD is called the CID of your file - it is effectively the file's hash.

If you uploaded a markdown file, you can use the IPFS markdown viewer to render the document for better viewing. Links for the markdown viewer look like https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/<CID>, where <CID> is your CID. For instance the link above would be: https://ipfs.io/ipfs/QmTk...HSWD

Share the URL with others and verify that your file is publicly accessible.

The reason we use IPFS is that it is a decentralized means of storage, making it resistant to censorship or single points of failure. This increases the likelihood that the file will remain available in the future.

Formatting the JSON file for the governance proposal​

Many proposals allow for long form text to be included, usually under the key description. These provide the opportunity to include markdown if formatted correctly as well as line breaks with \n. Beware, however, that if you are using the CLI to create a proposal, and setting description using a flag, the text will be escaped which may have undesired effects. If you're using markdown or line breaks it's recommended to put the proposal text into a json file and include that file as part of the CLI proposal, as opposed to individual fields in flags.

Text proposals​

TextProposals 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 Evmos chain, a text proposal has no direct effect on Evmos.

Real example​

Proposal 1 was representative of one of four core network activities that users had to participate in to claim tokens from the Evmos Rektdrop.

{
  "title": "Airdrop Claim Mission",
  "description": "Vote to claim",
  "deposit": "10000000000000000000aevmos"
}

Community pool spend proposals​

For community pool spend proposals, there are five components:

  1. Title - the distinguishing name of the proposal, typically the way the that explorers list proposals
  2. Description - the body of the proposal that further describes what is being proposed and details surrounding the proposal
  3. Recipient - the Evmos (bech32-based) address that will receive funding from the Community Pool
  4. Amount - the amount of funding that the recipient will receive in atto-EVMOS (aevmos)
  5. Deposit - the amount that will be contributed to the deposit (in aevmos) from the account submitting the proposal

Made-Up example​

In this simple example (below), a network explorer will list the governance proposal as a CommunityPoolSpendProposal. When an observer selects the proposal, they'll see the description. Not all explorers will show the recipient and amount, so ensure that you verify that the description aligns with the what the governance proposal is programmed to enact. If the description says that a certain address will receive a certain number of EVMOS, it should also be programmed to do that, but it's possible that that's not the case (accidentally or otherwise).

The amount is 1000000000000000000aevmos. This is equal to 1 EVMOS, so recipient address evmos1mx9nqk5agvlsvt2yc8259nwztmxq7zjq50mxkp will receive 1 EVMOS if this proposal is passed.

The deposit of 3500000000000000000000aevmos results in 3500 EVMOS being used from the proposal submitter's account. A minimum deposit is required for a proposal to enter the voting period, and anyone may contribute to this deposit within 3 days. If the minimum deposit isn't reached before this time, the deposit amounts will be burned. Deposit amounts will also be burned if the quorum isn't met in the vote or the proposal is vetoed.

{
  "title": "Community Pool Spend",
  "description": "This is the summary of the key information about this proposal. Include the URL to a PDF version of your full proposal.",
  "recipient": "evmos1mx9nqk5agvlsvt2yc8259nwztmxq7zjq50mxkp",
  "amount": [
    {
      "denom": "aevmos",
      "amount": "1000000000000000000"
    }
  ],
  "deposit": "64000000000000000000aevmos"
}

An example​

This is a governance protocol which Seda, the provider of a cross-chain oracle which provides smart contracts with access to economically secure data feeds, submitted to cover costs of the subsidised FPO (First Party Oracle) solution which they deployed on the Evmos mainnet.

Users can query the proposal details with the evmosd command-line interface using this command:

`evmosd --node https://tendermint.bd.evmos.org:26657 query gov proposal 23`.
{
  "title": "Grant proposal for Flux Protocol an oracle solution live on Evmos",
  "description": "proposal: https://gateway.pinata.cloud/ipfs/QmfZknL4KRHvJ6XUDwtyRKANVs44FFmjGuM8YbArqqfWwF discussion: https://commonwealth.im/evmos/discussion/4915-evmos-grant-flux-oracle-solution",
  "recipient": "evmos15dxa2e3lc8zvmryv62x3stt86yhplu2vs9kxct",
  "amount": [
    {
      "amount": "12900000000000000000000",
      "denom": "aevmos"
    }
  ],
  "deposit": "64000000000000000000aevmos"
}

Params-Change proposals​

tip

Changes to the gov module are different from the other kinds of parameter changes because gov has subkeys, as discussed here. Only the key part of the JSON file is different for gov parameter-change proposals.

For parameter-change proposals, there are seven components:

  1. Title - the distinguishing name of the proposal, typically the way the that explorers list proposals
  2. Description - the body of the proposal that further describes what is being proposed and details surrounding the proposal
  3. Subspace - the Evmos module with the parameter that is being changed
  4. Key - the parameter that will be changed
  5. Value - the value of the parameter that will be changed by the governance mechanism
  6. Denom - aevmos (atto-EVMOS) will be the type of asset used as the deposit
  7. Amount - the amount that will be contributed to the deposit (in aevmos) from the account submitting the proposal

Real example​

In the example below, a network explorer listed the governance proposal by its title: "Increase the minimum deposit for governance proposals." When a user selects the proposal, they'll see the proposal’s description. This proposal can be found on the Evmos network here.

Not all explorers will show the proposed parameter changes that are coded into the proposal, so the delegator should verify that the description aligns with what the governance proposal is programmed to enact. If the description says that a certain parameter will be increased, it should also be programmed to do that, but it's possible that that's not the case (accidentally or otherwise).

Users can query the proposal details with the evmosd command-line interface using this command:

`evmosd --node https://tendermint.bd.evmos.org:26657 query gov proposal 7`.
{
  "title": "Increase the minimum deposit for governance proposals",
  "description": "If successful, this parameter-change governance proposal will change the minimum deposit for future proposals from 10 evmos tokens to 3500.",
  "changes": [
    {
      "subspace": "gov",
      "key": "depositparams",
      "value": {"mindeposit":[{"denom":"aevmos","amount":"3500000000000000000000"}],
      "max_deposit_period":"1209600000000000"}
    }
  ],
  "deposit": "20100000000000000000aevmos"
}

The deposit denom is aevmos and amount is 20100000000000000000. Therefore, a deposit of 20.1 EVMOS will be included with this proposal. At the time, the EVMOS mainnet had a 10 EVMOS minimum deposit, so this proposal was put directly into the voting period (and subsequently passed). The minimum deposit amount is currently 3500 EVMOS. There is a minimum deposit required for a proposal to enter the voting period, and anyone may contribute to this deposit within a 3-day period. If the minimum deposit isn't reached before this time, the deposit amounts will be burned.

Sending the transaction that submits your governance proposal​

For information on how to use evmosd binary to submit an on-chain proposal through the governance module, please refer to the quickstart documentation.

CLI​

This is the command format for using evmosd (the command-line interface) to submit your proposal on-chain:

evmosd tx gov submit-legacy-proposal \
  --title=<title> \
  --description=<description> \
  --type="Text" \
  --deposit="1000000aevmos" \
  --from=<dev0> \
  --chain-id=<chain_id>
  --node <address>
tip

Use the evmos tx gov --help flag to get more info about the governance commands

  1. evmosd is the command-line interface client that is used to send transactions and query Evmos
  2. tx gov submit-legacy-proposal param-change indicates that the transaction is submitting a parameter-change proposal
  3. --from dev0 is the account key that pays the transaction fee and deposit amount
  4. --gas 500000 is the maximum amount of gas permitted to be used to process the transaction
    • the more content there is in the description of your proposal, the more gas your transaction will consume
    • if this number isn't high enough and there isn't enough gas to process your transaction, the transaction will fail
    • the transaction will only use the amount of gas needed to process the transaction
  5. --gas-prices is the flat-rate per unit of gas value for a validator to process your transaction
  6. --chain-id evmos_9001-2 is Evmos Mainnet. For current and past chain-id's, please look at the Chain ID documentation.
  7. --node is using a full node to send the transaction to the Evmos Mainnet

Verifying your transaction​

After posting your transaction, your command line interface (evmosd) will provide you with the transaction's hash, which you can either query using evmosd or by searching the transaction hash using Mintscan or any block explorer.

Depositing funds after a proposal has been submitted​

Sometimes a proposal is submitted without having the minimum token amount deposited yet. In these cases you would want to be able to deposit more tokens to get the proposal into the voting stage. In order to deposit tokens, you'll need to know what your proposal ID is after you've submitted your proposal. You can query all proposals by the following command:

evmosd q gov proposals

If there are a lot of proposals on the chain already, you can also filter by your own address. For the proposal above, that would be:

evmosd q gov proposals --depositor evmos1hxv7mpztvln45eghez6evw2ypcw4vjmsmr8cdx

Once you have the proposal ID, this is the command to deposit extra tokens:

evmosd tx gov deposit <proposal-id> <deposit> --from <name>

In our case above, the <proposal-id> would be 59 as queried earlier. The <deposit> is written as 500000aevmos, just like the example above.

Submit your proposal to the testnet​

You may want to submit your proposal to the testnet chain before the mainnet for a number of reasons:

  1. To see what the proposal description will look like
  2. To signal that your proposal is about to go live on the mainnet
  3. To share what the proposal will look like in advance with stakeholders
  4. To test the functionality of the governance features

Submitting your proposal to the testnet increases the likelihood that you will discover a flaw before deploying your proposal on mainnet. A few things to keep in mind:

  • you'll need testnet tokens for your proposal (ask around for a faucet)
  • the parameters for testnet proposals are different (eg. voting period timing, deposit amount, deposit denomination)
  • the deposit denomination is in 'atevmos' instead of 'aevmos'