teleo-codex/inbox/archive/2024-02-05-futardio-proposal-execute-creation-of-spot-market-for-meta.md
Teleo Pipeline f70720aa78 reconcile: mark 312 archive sources, add 300 bidirectional links
- 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>
2026-03-27 13:40:24 +00:00

3.2 KiB

type title author url date domain format status tags event_type derived_items
source Futardio: Execute Creation of Spot Market for META? futard.io https://www.futard.io/proposal/HyA2h16uPQBFjezKf77wThNGsEoesUjeQf9rFvfAy4tF 2024-02-05 internet-finance data processed
futardio
metadao
futarchy
solana
governance
proposal
decisions/internet-finance/metadao-execute-creation-of-spot-market-for-meta.md

Proposal Details

Summary

🎯 Key Points

The proposal aims to execute the creation of a spot market for META by establishing a liquidity pool, allocating META to participants, and compensating multisig members.

📊 Impact Analysis

👥 Stakeholder Impact

Participants will have the opportunity to acquire META and contribute to the liquidity pool, enhancing their engagement with the DAO.

📈 Upside Potential

Successfully creating the liquidity pool could lead to increased trading volume and price stability for META.

📉 Risk Factors

There is a risk of non-compliance from participants regarding USDC transfers, which could hinder the successful funding of the liquidity pool.

Content

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:

  1. People submit their demand into a Google form
  2. Proph3t decides how much allocation to give each person
  3. Proph3t reaches out on Monday, Feb 5th to people with allocations, telling them they have to transfer the USDC by Wednesday, Feb 7th
  4. 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
  5. 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.

Raw Data

  • Proposal account: HyA2h16uPQBFjezKf77wThNGsEoesUjeQf9rFvfAy4tF
  • Proposal number: 5
  • DAO account: 7J5yieabpMoiN3LrdfJnRjQiXHgi7f47UuMnyMyR78yy
  • Proposer: UuGEwN9aeh676ufphbavfssWVxH7BJCqacq1RYhco8e
  • Autocrat version: 0.1
  • Completed: 2024-02-10
  • Ended: 2024-02-10