LogoLogo
  • GoldiDOCS
  • Goldiswap
    • Overview
    • Mechanisms
    • LOCKS
  • Goldilend
    • Overview
  • Goldivaults
    • Overview
    • Mechanisms
  • Info
    • Contract Addresses
    • Audits
    • Brand Assets
  • Governance
    • GGPs
      • GGP 1
    • Goldilocks DAO Governance Charter
      • The 2 Beras
      • Multisig Structure
      • Goldilocks Governance Proposals (GGPs)
      • Governance Process
      • Code of Conduct
      • Goldilocks Values
    • Goldilocks Core Contributor Team “The 2 Beras”
      • Strategy Consultant (SC)
      • Operational Lead (OL)
    • Goldilocks DAO Governance - How to Guide
      • Phase 1: Request for Comment (RFC)
      • Phase 2: Governance Proposal
      • Governance Modifications
Powered by GitBook
On this page
Export as PDF
  1. Governance
  2. Goldilocks DAO Governance - How to Guide

Phase 2: Governance Proposal

PreviousPhase 1: Request for Comment (RFC)NextGovernance Modifications

Last updated 1 month ago

Timeframe: Total 11 days

  • 2 day waiting period

  • 7 day voting period

  • 2 day timelock

Format: On-chain proposal

Quorum: 50M staked LOCKS

Delegation: Proposer needs 5M staked LOCKS delegated

Phase 2 is the final step of the governance process. If this vote passes, then a change will be enacted on-chain.

How to create an on-chain Governance Proposal:

Update any last iterations to your proposal based on the previous feedback provided before posting your Goldilock Governance Proposal for voting.

In the please create a post titled “Governance Proposal — [Your Title Here]”. The post must include links to all previous forum posts.

Create your proposal. This can be done either through the or through writing the calldata for more complicated proposal logic. This calldata will be executed if and when the proposal passes. If writing the calldata yourself, please review the logic with a qualified Goldilock community member before posting the final proposal.

The proposer must have at least 5M staked LOCKS delegated to their address in order to formally put forward a proposal for community voting. If the proposer does not have the required staked LOCKS supply, they must find a delegate who has enough delegated staked LOCKS to meet the proposal threshold to propose on their behalf.

After the proposal has been submitted (or the propose(d) function has been called), a 2 day voting delay will start. After the voting delay is finished, a 7 day voting period will begin. If the proposal passes successfully, a 2 day time lock will follow before the proposed code is executed.

There must be at least 50M staked LOCKS yes votes received for the proposal to pass and be executed. If the “No change” option wins, the proposal will not be initiated.

Governance Forum
Goldilocks Governance Portal