Skip to content

mock-proposal.md

Latest commit

 

History

History
67 lines (50 loc) · 2.32 KB

mock-proposal.md

File metadata and controls

67 lines (50 loc) · 2.32 KB
cgp 9999
title Test Proposal for Database Testing
date-created 2025-01-15
author @test-author
status DRAFT
governance-proposal-id 9999
date-executed

Overview

This is a mock proposal used for testing the Celo governance database and proposal lifecycle. It represents a generic governance proposal that can be used to test various proposal states including draft, queued, referendum, execution, and terminal states like executed, expired, withdrawn, and rejected.

This proposal does not represent a real governance action and should only be used in test environments and database dumps for development and testing purposes.

Proposed Changes

This mock proposal simulates changes to the Celo protocol for testing purposes:

  1. Update test parameter A from value X to value Y
  2. Modify test smart contract configuration Z
  3. Adjust test governance threshold for testing various vote outcomes

Fill the transaction list with:

  • TestContract.setParameterA(Y)
  • TestContract.setConfigZ(newConfig)
  • Governance.setThreshold(newThreshold)

Verification

In a test environment, verification would involve:

  • Checking that test parameters are updated correctly
  • Validating that test contract state reflects the proposed changes
  • Ensuring test governance thresholds are properly set

Risks

As this is a test proposal, there are no real risks to the network. However, it simulates the following risk considerations:

  • Potential impact on test parameter values
  • Compatibility with existing test contract state
  • Effects on test governance voting dynamics
  • Edge cases in proposal lifecycle state transitions

Test Scenarios

This proposal is designed to support testing of:

  • Draft state: Proposal metadata exists but not yet on-chain
  • Queued state: Proposal is in upvoting phase with/without upvotes
  • Referendum state: Proposal is in voting phase with various vote distributions
  • Execution state: Proposal passed voting and awaiting execution
  • Approval state: Testing technical approval workflow
  • Terminal states: Executed, expired, withdrawn, or rejected outcomes
  • Edge cases: Vote revocations, re-submissions, partial approvals

Useful Links

  • This is a mock proposal for testing purposes only
  • Not intended for mainnet or actual governance use
  • Use only in test databases and development environments