跳到主要内容

Submitting Proposals

This guide walks through the process of creating and submitting governance proposals on Monolythium.

Overview​

Anyone holding LYTH can submit a governance proposal. To enter the voting period, a proposal must accumulate a minimum deposit of 10,000 LYTH. Once the deposit threshold is met, stakers have 5 days to vote.

ParameterValue
Minimum deposit10,000 LYTH (10,000,000,000,000,000,000,000 alyth)
Deposit period14 days
Voting period5 days
Quorum33.4% of staked LYTH
Pass threshold>50% Yes (excluding Abstain)
Veto threshold>33.4% NoWithVeto

Proposal Types​

TypeDescriptionExecution
TextNon-binding signal to the communityNo automatic on-chain effect
Parameter ChangeModify chain parameters (staking, slashing, governance, mint)Applied automatically upon passing
Software UpgradeCoordinated binary swap at a target block heightNodes upgrade via Cosmovisor or Monarch
Community Pool SpendFund a project or recipient from the community treasuryTokens transferred automatically upon passing

Before Submitting​

Discuss First

Proposals that appear without prior community discussion tend to fail. Before submitting on-chain, share your idea in official community channels. Gather feedback, refine the proposal, and build support. A well-discussed proposal has a significantly higher chance of passing.

Checklist before submission:

  1. Draft a clear title and detailed description
  2. Share the draft in community forums or governance channels
  3. Address questions and objections from the community
  4. Ensure you have at least 10,000 LYTH for the deposit (or coordinate with others to reach the minimum)

Submitting a Text Proposal​

Text proposals signal community sentiment without triggering automatic execution.

Via CLI (monod)​

monod tx gov submit-proposal \
  --title "Proposal Title" \
  --description "Detailed description of what you are proposing and why. Include context, rationale, and expected outcomes." \
  --type text \
  --deposit 10000000000000000000000alyth \
  --from <your-key> \
  --chain-id mono_6940-1

Via Monarch CLI​

monarch gov submit --from <your-key> --proposal proposal.json --deposit 10000000000000000000000alyth

Where proposal.json contains:

{
  "title": "Proposal Title",
  "description": "Detailed description of what you are proposing and why.",
  "type": "Text",
  "deposit": "10000000000000000000000alyth"
}

Parameter Change Proposals​

Parameter change proposals modify on-chain parameters. They are applied automatically if the proposal passes.

Changeable Parameters​

ModuleParameters
stakingunbonding_time, max_validators, max_entries
slashingslash_fraction_downtime, slash_fraction_double_sign, downtime_jail_duration, signed_blocks_window
govvoting_period, min_deposit, quorum, threshold, veto_threshold
mintinflation_rate
distributioncommunity_tax, base_proposer_reward, bonus_proposer_reward

Submission Format​

monod tx gov submit-proposal param-change proposal.json \
  --from <your-key> \
  --chain-id mono_6940-1

The JSON file must follow this structure:

{
  "title": "Increase Max Validators to 75",
  "description": "This proposal increases the active validator set from 53 to 75 to improve decentralization.",
  "changes": [
    {
      "subspace": "staking",
      "key": "MaxValidators",
      "value": "75"
    }
  ],
  "deposit": "10000000000000000000000alyth"
}
Verify Parameters

Incorrect parameter values can destabilize the network. Double-check parameter names, subspaces, and values against the current chain configuration before submitting. Query current parameters with monod query params subspace <module> <key>.

Software Upgrade Proposals​

Software upgrade proposals coordinate a binary swap across all validators at a specific block height. When the chain reaches the target height, nodes running Cosmovisor or Monarch automatically switch to the new binary.

monod tx gov submit-proposal software-upgrade <upgrade-name> \
  --title "Upgrade to v0.3.0" \
  --description "This upgrade introduces IBC improvements and fixes a consensus edge case." \
  --upgrade-height 2000000 \
  --upgrade-info '{"binaries":{"linux/amd64":"https://releases.monolythium.com/v0.3.0/monod-linux-amd64"}}' \
  --deposit 10000000000000000000000alyth \
  --from <your-key> \
  --chain-id mono_6940-1
FieldDescription
<upgrade-name>A unique name for this upgrade (e.g., v0.3.0)
--upgrade-heightBlock height at which the upgrade takes effect
--upgrade-infoJSON with binary download URLs for automated upgrades
信息

Validators using Monarch CLI or Cosmovisor handle the binary swap automatically. Validators managing binaries manually must swap before the target block height.

Community Pool Spend Proposals​

Community pool spend proposals allocate funds from the on-chain community treasury to a recipient address.

monod tx gov submit-proposal community-pool-spend proposal.json \
  --from <your-key> \
  --chain-id mono_6940-1
{
  "title": "Fund Ecosystem Grant for Wallet Development",
  "description": "Allocate 50,000 LYTH to fund development of a hardware wallet integration.",
  "recipient": "mono1abc...xyz",
  "amount": "50000000000000000000000alyth",
  "deposit": "10000000000000000000000alyth"
}

Deposit Period​

After submitting, the proposal enters a 14-day deposit period. The minimum deposit of 10,000 LYTH must be reached within this window for the proposal to advance to voting.

  • You can provide the full deposit yourself at submission time
  • Other LYTH holders can contribute to the deposit using the deposit command
  • If the minimum is not reached within 14 days, the proposal fails and all deposits are burned

Adding to a Deposit​

# monod
monod tx gov deposit <proposal-id> <amount>alyth \
  --from <your-key> \
  --chain-id mono_6940-1

# Monarch CLI
monarch gov deposit <proposal-id> <amount>alyth --from <your-key>
注意

Deposits for proposals that fail to reach the minimum threshold are burned, not returned. Only deposit into proposals you believe will reach the minimum.

Monitoring Your Proposal​

Query a Specific Proposal​

monod query gov proposal <proposal-id>

List Proposals by Status​

# Proposals currently in voting
monod query gov proposals --status voting_period

# Proposals in deposit period
monod query gov proposals --status deposit_period

# All proposals
monod query gov proposals

Via Monarch CLI​

monarch gov list

Check Deposit Status​

monod query gov deposits <proposal-id>

Check Vote Tally​

monod query gov tally <proposal-id>

Tips for a Successful Proposal​

  1. Clear, specific title — State exactly what the proposal does in the title
  2. Detailed rationale — Explain the problem, the proposed solution, and why this approach is best
  3. Community discussion first — Share the draft publicly and address feedback before submitting on-chain
  4. Sufficient deposit — Provide the full 10,000 LYTH deposit upfront when possible to move the proposal to voting quickly
  5. Campaign for votes — After the proposal enters the voting period, remind the community to participate. Low turnout can cause the quorum to be missed even for popular proposals
  6. Link supporting evidence — Reference forum discussions, technical analyses, or precedents from other proposals
  7. Set realistic expectations — For parameter changes, explain the impact clearly. For spend proposals, include a budget breakdown

Proposal Lifecycle Summary​

Submit → Deposit Period (14 days max) → Voting Period (5 days) → Outcome
                                                                    ├── Passed: executed
                                                                    ├── Rejected: deposit returned
                                                                    └── Vetoed: deposit burned