teleo-codex/inbox/archive/2025-02-26-futardio-proposal-release-a-launchpad.md

4.5 KiB
Raw Blame History

type title author url date domain format status tags event_type
source Futardio: Release a Launchpad? futard.io https://www.futard.io/proposal/HREoLZVrY5FHhPgBFXGGc6XAA3hPjZw1UZcahhumFkef 2025-02-26 internet-finance data unprocessed
futardio
metadao
futarchy
solana
governance
proposal

Proposal Details

Summary

🎯 Key Points

The proposal seeks DAO approval to create a launchpad for futarchy DAOs to streamline capital formation in crypto, allowing project creators to raise funds while offering funders a safer investment mechanism.

📊 Impact Analysis

👥 Stakeholder Impact

Founders gain early community engagement and improved fundraising opportunities, while funders benefit from reduced risks of losses due to project mismanagement.

📈 Upside Potential

The launchpad could enhance trust in crypto fundraising by minimizing the risk of "rug pulls," thereby attracting more investors and projects to the ecosystem.

📉 Risk Factors

There is a risk that the initial permissioned launchpad model may create dependency on the founding team for project selection, potentially limiting diversity and innovation.

Content

Type

Business - Project

Author(s)

Proph3t, Kollan

Overview

We are requesting the DAOs permission to release a launchpad for futarchy DAOs. Such a launchpad could solve many of the existing issues with capital formation in crypto.

Mechanics

The launchpad would work in the following way -

  1. Project creators raise project ideas and specify a minimum amount of USDC they need to execute on the idea
  2. Funders have 5 days to fund those ideas in exchange for tokens
    1. Funders would receive 1,000 tokens per USDC committed
    2. Except in rare cases, the whole initial supply would be issued by this process
  3. If the launch receives sufficient USDC, 10% of the USDC is paired against an equivalent amount of tokens in a constant-product AMM. Then, all remaining USDC and the ability to mint new tokens are transferred to a futarchy DAO. Contributors can then raise proposals to issue tokens to themselves or to pay themselves on some interval (e.g., monthly)
  4. If the launch does not receive sufficient USDC, all funders would be able to burn their tokens to claim their original USDC back

Why funders will prefer this to the status quo

Rugging is a rampant problem for on-chain capital raises. In this system, its much harder for projects to rug because all of the USDC goes either to the DAO or to the liquidity pool. If the team walks away on day #1, anyone would be able to raise a proposal to the DAO to liquidate the treasury and return all money to the funders. This is also true on day #30, day #365, and day #1083.

Why founders will prefer this to the status quo

This system gives you two benefits as a founder:

  1. Community involvement from day 1
  2. Ability to raise money that you wouldnt have otherwise been able to raise

As Ive written about before, community involvement from day 1 is an unfair advantage for projects. The two biggest crypto projects, Bitcoin and Ethereum, both had it. Bag bias is real, and in this system it works for you as a founder.

This also opens up the door to founders from geographies where its historically been difficult to raise money.

GTM

We will canvas our network to find early-stage (ideally pre-raise) projects to launch on the platform. We already have a few prospective projects.

At the start, launches would be permissioned by us. We would reserve the right to transition to a permissionless system when and if we deem it beneficial.

Founder discretion

We would also have discretion to change the mechanics of launches (e.g. to adopt an IDO pool approach rather than the above fixed price approach) if we deem it +EV for MetaDAO

Raw Data

  • Proposal account: HREoLZVrY5FHhPgBFXGGc6XAA3hPjZw1UZcahhumFkef
  • Proposal number: 13
  • DAO account: CNMZgxYsQpygk8CLN9Su1igwXX2kHtcawaNAGuBPv3G9
  • Proposer: proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2
  • Autocrat version: 0.3
  • Completed: 2025-03-01
  • Ended: 2025-03-01