⚡Proposals

WIP

🔒 Governance Proposal Instantiation

PURPOSE

Utilizes the Forge contract to instantiate a Proposal from the Proposal Template Contract. Stores the record of the instantiation in the Forge’s proposal registry.

Proposals

Proposals are Instantiated in the Forge

Proposal Types

Governance

Proposals are Instantiated in the Forge Contract

Standard Proposal Eligibility Requirement

Proposal fYFD Minimum

Minimum amount of fYFD required to submit an Standard Proposal is currently set to: 25,000 fYFD Points

This value can be changed by DAO governance.

Proposer must meet or exceed the fYFD Minimum Amount for the respective type of Proposal. The proposer must have locked enough $YFD to meet or exceed the requirement to be eligible to submit proposals for the specified proposal type. Initial values are set as:

• Governance proposal minimum.
• Vault proposal minimum
• Emergency proposal minimum

Emergency Proposal Eligibility Requirement

fYFD Locking During Proposal Duration

When a proposal is submitted the portion of the proposer’s fYFD equivalent to the amount required to submit a proposal is “locked” for the duration of the submission process. The “fYFD” used to submit the proposal maintains a “locked” status until the associated proposal status changes at the completion voting period and is defined as either accepted or rejected.

Locked fYFD means the fYFD and $YFD equivalent are unavailable for:

• Withdrawal to $YFD
• Meeting the fYFD submission requirements of additional proposals.

When the voting period is complete the fYFD locked for the proposal:

• On a No with Veto an amount of $YFD equivalent to the fYFD locked for the proposal is sent to the { TREASURY ADDRESS }
• On an Affirmative or standard No vote outcome is unlocked and available to the proposer to withdraw or use again on another proposal

Submission would not exceed the Active Proposal Maximum for an individual.

Footnote

Any proposal from the same proposer that is active or pending action counts towards this limit as defined in the Governance Parameter.. Must exceed the Proposal Submission Cooldown Period for an individual4. The amount of blocks since the last active proposal from the proposer must exceed the Proposal Submission Cooldown Period for an Individual before they are allowed to submit a proposal. Acceptance Requirement Mandatory proposal fields are filled and validated Parameters defined by each proposal type are required for a proposal to be accepted by the contract when submitted by a Proposer.

Notes

and because of the way our infrastructure is architected the system is trustless.  When interacting with contracts you just ask or tell the contracts what you want to do but you don't have to tell the contracts with whom you want to react (except the token CW20 $YFD deposits to the forge... you have to state the Forge address) 

otherwise the entire system knows about the entire system -- so there's no opportunity to accept some outside redirection of funds because funds distribution is determined based on how a particular fYFD holder/vault user has interacted with the system
so many systems partially on-chain rely on someone passing addresses to a contract and the contract checking permission against the addresses where-as YFD says "oh it's you... let me check my on-chain ledger" -- yes, {sir|madam} I have these activities available to you
I'm working on writing up the docs
taking our technical documents that we used to build the system and translating them into a cohesive story that someone can walk through and understand the ins and outs of the system
If you're interested I can share the work in progress docs, but I think it's better that I hold back until the draft is complete (and then get your feedback) because otherwise I think the docs might be confusing

Table of contents

• ✍ Text / Sentiment
• 💥 Execution
• 💵 Treasury Spend
• 🛂 Whitelist
• 🔒 Vault
• 🚀 Contract Deployment
• 📜 Parameter
• 🚑 Emergency