- 131 sources → processed (matched to decisions/entities by proposal hash) - 72 sources → null-result (test/spam) - 109 sources → null-result (futardio unmatched, no KB output) - 91 sources kept unprocessed (genuine backlog: health, ai-alignment, space-dev, etc.) - 117 decisions get source_archive backlinks - 131 archive sources get derived_items forward links - Linking pattern: frontmatter only, file paths as identifiers (Ganymede Option A) Script: reconcile-sources.py (proposal hash matching + entity name matching) Co-Authored-By: Epimetheus <noreply@pentagon.ai>
4.8 KiB
| type | entity_type | name | domain | status | parent_entity | platform | proposer | proposal_url | proposal_date | resolution_date | category | summary | key_metrics | tracked_by | created | source_archive | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| decision | decision_market | MetaDAO: Execute Creation of Spot Market for META? | internet-finance | passed | metadao | futardio | UuGEwN9aeh676ufphbavfssWVxH7BJCqacq1RYhco8e | https://v1.metadao.fi/metadao/trade/HyA2h16uPQBFjezKf77wThNGsEoesUjeQf9rFvfAy4tF | 2024-02-05 | 2024-02-10 | treasury | Authorized 4,130 META transfer to 4/6 multisig to execute spot market creation through participant sale and liquidity pool establishment |
|
rio | 2026-03-11 | inbox/archive/2024-02-05-futardio-proposal-execute-creation-of-spot-market-for-meta.md |
MetaDAO: Execute Creation of Spot Market for META?
Summary
This proposal authorized the transfer of 4,130 META tokens to a 4/6 multisig to execute the creation of a spot market for META tokens. The execution plan involved coordinating a private sale to raise 75,000 USDC, then using 1,000 META paired with 35,000 USDC to create a liquidity pool on Meteora, setting an initial spot price of 35 USDC per META.
Market Data
- Outcome: Passed
- Proposer: UuGEwN9aeh676ufphbavfssWVxH7BJCqacq1RYhco8e
- Proposal Number: 5
- Completed: 2024-02-10
- Autocrat Version: 0.1
Execution Structure
The proposal established a 4/6 multisig containing Proph3t, Dean, Nallok, Durden, Rar3, and BlockchainFixesThis to execute a multi-step process:
- Collect demand through Google form
- Proph3t determines allocations
- Participants transfer USDC (Feb 5-7 deadline)
- Backfill unmet demand from waitlist (Feb 8)
- Multisig distributes META to participants, creates LP, and disbands (Feb 9)
Token allocation breakdown:
- 3,100 META to sale participants
- 1,000 META paired with 35,000 USDC for liquidity pool
- 30 META as multisig member compensation (5 META each)
Significance
This proposal demonstrates the operational scaffolding required for futarchy-governed treasury operations. The proposal explicitly acknowledged "no algorithmic guarantee" of execution, instead relying on reputational incentives: "it's unlikely that 4 or more of the multisig members would be willing to tarnish their reputation in order to do something different."
The execution model shows futarchy DAOs using human-operated multisigs with social enforcement for operational tasks even when the governance decision itself is market-determined. This represents a pragmatic hybrid between algorithmic governance and traditional operational execution.
Relationship to KB
- metadao - parent entity, treasury operation
- MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window - governance mechanism
- futarchy-governed DAOs converge on traditional corporate governance scaffolding for treasury operations because market mechanisms alone cannot provide operational security and legal compliance - operational pattern
- meteora - liquidity pool platform
Full Proposal Text
Source: futard.io, tabled 2024-02-05
Proposal 3 passed, giving the DAO the remit to raise money and use some of that money to create an LP pool. Since then, Proph3t and Rar3 have ironed out the details and come up with this plan:
- People submit their demand into a Google form
- Proph3t decides how much allocation to give each person
- Proph3t reaches out on Monday, Feb 5th to people with allocations, telling them they have to transfer the USDC by Wednesday, Feb 7th
- Some people won't complete this step, so Proph3t will reach out to people who didn't get their full desired allocation on Thursday, Feb 8th to send more USDC until we reach the full 75,000
- On Friday, Feb 9th the multisig will send out META to all participants, create the liquidity pool (likely on Meteora), and disband
We've created the multisig; it's a 4/6 containing Proph3t, Dean, Nallok, Durden, Rar3, and BlockchainFixesThis. This proposal will transfer 4,130 META to that multisig. This META will be allocated as follows:
- 3100 META to send to participants of the sale
- 1000 META to pair with 35,000 USDC to create the pool (this sets an initial spot price of 35 USDC / META)
- 30 META to renumerate each multisig member with 5 META
Obviously, there is no algorithmic guarantee that the multisig members will actually perform this, but it's unlikely that 4 or more of the multisig members would be willing to tarnish their reputation in order to do something different.