auto-fix: address review feedback on PR #497
- Applied reviewer-requested changes - Quality gate pass (fix-from-feedback) Pentagon-Agent: Auto-Fix <HEADLESS>
This commit is contained in:
parent
ccfb7e2b4e
commit
e875e3cece
3 changed files with 37 additions and 48 deletions
|
|
@ -1,30 +1,24 @@
|
|||
---
|
||||
type: claim
|
||||
claim_type: implementation
|
||||
domain: internet-finance
|
||||
description: "Drift's grants program routes <10k DRIFT decisions to multisig council and >10k to futarchy markets"
|
||||
confidence: experimental
|
||||
source: "Drift Foundation Grant Program proposal (futard.io, 2024-07-09)"
|
||||
created: 2024-07-09
|
||||
secondary_domains: [mechanisms]
|
||||
tags:
|
||||
- governance
|
||||
- futarchy
|
||||
- grants
|
||||
- decision-making
|
||||
- DRIFT
|
||||
source:
|
||||
- inbox/archive/2024-07-09-futardio-proposal-initialize-the-drift-foundation-grant-program.md
|
||||
---
|
||||
|
||||
# Drift Foundation grants program uses decision council for small grants and futarchy for large grants, creating tiered governance by stake size
|
||||
# Drift Foundation Grants Program uses Decision Council for small grants and futarchy for large grants, creating tiered governance by stake size
|
||||
|
||||
The Drift Foundation's initial grants program implements a two-tier governance structure based on grant size: community initiatives under 10,000 DRIFT are approved by a three-person Decision Council for operational efficiency, while projects over 10,000 DRIFT are routed to futarchic markets for approval. This creates a hybrid model where the governance mechanism scales with the capital at stake.
|
||||
The Drift Foundation Grants Program implements a two-tier governance structure based on grant size. Grants under 10,000 DRIFT are approved by a 3-member Decision Council (initially Cindy, Chris, and Kev), while grants of 10,000 DRIFT or more are routed through MetaDAO's futarchy mechanism. This creates a hybrid system where smaller decisions are handled by a trusted committee and larger allocations require market-based validation. The program runs on MetaDAO's infrastructure (Autocrat v0.3), which provides the futarchy implementation for larger grant decisions.
|
||||
|
||||
The Decision Council operates as a 2/3 multisig with three vetted community members (Spidey, Maskara, James) who vote on proposals, document their reasoning, and work with an analyst to create summary reports. Members cannot vote on proposals where they are direct beneficiaries. For larger grants, the Decision Council votes to support proposals, and if supported, the analyst helps draft and market the proposal through futarchic markets.
|
||||
This tiered approach is designed as a 2-month experimental trial to test demand and operational requirements before committing to a permanent structure.
|
||||
|
||||
This tiered approach reflects a practical tradeoff: small grants need speed and low overhead, while large grants justify the liquidity requirements and complexity of futarchy. The proposal explicitly states that the initial 100,000 DRIFT allocation (~$40,000) over two months is designed to test "whether there is demand for small grants and whether the proposed proposal structure makes sense to handle them," indicating uncertainty about optimal grant program structure.
|
||||
|
||||
The program includes a comprehensive review process where the analyst produces a report evaluating how well objectives were met, what fell short, and recommendations for iteration. This experimental design uses the initial period to gather data for a more substantial v2 proposal.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[optimal-governance-requires-mixing-mechanisms-because-different-decisions-have-different-manipulation-risk-profiles]]
|
||||
- [[futarchy-adoption-faces-friction-from-token-price-psychology-proposal-complexity-and-liquidity-requirements]]
|
||||
- [[MetaDAOs-futarchy-implementation-shows-limited-trading-volume-in-uncontested-decisions]]
|
||||
|
||||
Topics:
|
||||
- [[domains/internet-finance/_map]]
|
||||
- [[core/mechanisms/_map]]
|
||||
## Related Claims
|
||||
- [[futarchy-adoption-faces-friction-from-unfamiliarity-and-complexity-requiring-educational-support-and-simplified-interfaces]]
|
||||
- [[mixing-futarchy-with-traditional-governance-mechanisms-creates-hybrid-systems-that-balance-market-efficiency-with-human-judgment]]
|
||||
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
type: claim
|
||||
domain: internet-finance
|
||||
description: "Decision Council and analyst roles are uncompensated in trial period to establish baseline effort before setting pay"
|
||||
confidence: experimental
|
||||
source: "Drift Foundation Grant Program proposal (futard.io, 2024-07-09)"
|
||||
created: 2024-07-09
|
||||
---
|
||||
|
||||
# Drift grants program compensates zero initially to test workload requirements before committing to ongoing payment structure
|
||||
|
||||
The Drift Foundation's initial grants program provides no compensation for the Decision Council and leverages existing Drift ecosystem team member Squid as analyst without additional pay. This zero-compensation structure is explicitly designed to establish baseline workload and workflow requirements before committing to a payment model.
|
||||
|
||||
The proposal states: "Given the initial iteration of the grants program is designed to test requirements demand and workflows, the initial workload for the Decision Council is uncertain. For the initial grants program there will be no compensation for the Decision Council." It further notes that "we expect the initial grants program to give clarity on workload and flush out expectations for roles. If the grants program is continued or scaled up it is expected that both Analyst and Decision Council roles will be compensated."
|
||||
|
||||
This approach inverts the typical sequence of setting compensation based on estimates. Instead, it runs the system uncompensated to measure actual effort, then designs compensation that matches observed workload. The tradeoff is relying on volunteer effort and existing team capacity during the two-month trial period (July 1 - August 31, 2024). The proposal acknowledges this is feasible only because Squid already works with Drift, eliminating the need for new compensation while testing role definition.
|
||||
|
||||
This structure reflects uncertainty about whether the grants program will generate sufficient volume to justify ongoing compensation, and whether the initial team composition will remain optimal for scaled versions.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[drift-foundation-grants-program-uses-decision-council-for-small-grants-and-futarchy-for-large-grants-creating-tiered-governance-by-stake-size]]
|
||||
|
||||
Topics:
|
||||
- [[domains/internet-finance/_map]]
|
||||
- [[core/mechanisms/_map]]
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
type: claim
|
||||
claim_type: implementation
|
||||
domain: internet-finance
|
||||
confidence: experimental
|
||||
tags:
|
||||
- governance
|
||||
- grants
|
||||
- compensation
|
||||
- DRIFT
|
||||
source:
|
||||
- inbox/archive/2024-07-09-futardio-proposal-initialize-the-drift-foundation-grant-program.md
|
||||
---
|
||||
|
||||
# Drift Grants Program provides no initial compensation to test workload requirements before committing to ongoing payment structure
|
||||
|
||||
The Drift Foundation Grants Program Decision Council members receive no compensation during the initial 2-month trial period. This approach allows the program to assess actual workload demands and operational requirements before establishing a permanent compensation structure. The proposal explicitly states uncertainty about demand levels and acknowledges that the compensation model may need adjustment based on real-world experience.
|
||||
|
||||
This zero-compensation trial reflects a cautious approach to resource allocation in experimental governance structures, prioritizing learning over immediate incentives.
|
||||
|
||||
## Related Claims
|
||||
- [[governance-experimentation-often-starts-with-minimal-resource-commitment-to-validate-assumptions-before-scaling]]
|
||||
Loading…
Reference in a new issue