A good way to test any governance system is to see how it handles "hard" proposals: ones that are emotionally charged, reflexive, and information sensitive. The recent wave of buyback proposals across MetaDAO organizations is exactly that kind of test. Rather than take a side, this article uses the discourse as a case study to highlight the trade offs and suggest some guardrails that could improve decision markets going forward.

The Proposals

One such proposal was initiated by community members just days after Ranger's ICO. The proposal involved spending $2M USDC to buy $RNGR on a recurring schedule, capped at $0.78 (described as current NAV), with orders placed every five minutes until the funds run out.

Ranger isn't the only MetaDAO organization where buybacks became an early governance action. Loyal passed a similar buyback proposal, and now Paystream and Turbine Cash have community initiated buyback proposals with the same framing.

The debate has been intense, with rational arguments on both sides.

How Decision Markets Are Meant to Work

Decision markets (futarchy) replace voting with markets. For each proposal, traders take positions on whether the token will be worth more if the proposal passes than if it fails. The premise is that prices aggregate information. If a proposal improves the project, "pass" should trade higher than "fail" and vice versa.

Futarchy works best when two conditions hold:

  • Token price is a decent proxy for project value
  • Proposals don't mechanically move price during the trading window

Buybacks test both assumptions. A buyback can be fundamentally rational, but it also creates predictable pass-aligned demand. When markets can anticipate pass-aligned demand during (or right after) the trading window, "pass" can reflect both fundamental expectations and the mechanical effects of the buyback, which makes interpretation more nuanced.

Why Buyback Proposals Are Controversial in Futarchy

Buybacks can be sensible (for example, repurchasing tokens when NAV is below a certain value), but they can also be interpreted as price management, especially right after launch, when operating history is limited and narratives dominate.

The Ranger $2M buyback proposal illustrates this dynamic in practice. While it passed, the largest wallets were not uniformly aligned (see article: Why the RNGR $2M Buyback Proposal Was Decided Early).

In the proposal, the maximum buy price was set to $0.78 (stated NAV), but the conditional "if approved" price traded around $0.73, with spot around $0.72. Both were below the cap. As of Jan 17 (the day after the community initiated was resolved), $RNGR was trading around the mid $0.60s.

A similar (but smaller) price gap exists in $LOYAL: the buyback cap was $0.238, while $LOYAL has traded below that level (around $0.21 recently).

This demonstrates that the maximum buy price is not a price floor when the market has mixed opinions on project fundamentals. It is not evidence the decision to complete buybacks is "wrong."

Traders can rationally price "pass" below the cap when they expect the buyback to help, but not bring the price back up to the cap. For example, a trader may believe $2M worth of buybacks is good, but not enough to mute short term selling, or they may be discounting the NAV for any number of reasons.

Regardless of how you viewed the proposal outcomes, what has happened with the buyback proposals surfaces information about how they can be improved going forward.

The Case For and Against Early Buybacks

The Case for an Early, Capped Buyback

Supporters of early buybacks have valid arguments:

  • Treasury defense when the token trades below NAV: If the token is meaningfully below NAV, the treasury starts to look like an "arb target" to motivated token holders. Recent community initiated proposals across Ranger, Paystream, and Turbine Cash frame the buyback as a defense to reduce liquidation pressure and protect the treasury.
  • If NAV is reliable, buying below it can be conservative: Repurchasing tokens at a discount to NAV can be value accretive in the long run. The price cap is important to keep the DAO from "over paying."
  • Cooldowns limit repeat decisions: Recent proposals included a "cool-off" clause (i.e. no new buyback proposals for 90 days after proposal concludes). This reduces proposal frequency on an emotionally charged topic.

The Case Against an Early, Capped Buyback

Critics of early buybacks also have valid arguments:

  • Reflexivity: A buyback creates predictable buy demand up to the price cap. In futarchy, that's tricky because markets are using price to answer "is this proposal value accretive?" If the proposal supports price during the trading window (or right after), "pass" can win because the buyback creates demand, not because long term fundamentals have improved.
  • Bad timing when information is limited: Right after an ICO, there's limited operating history and narratives driving price. Critics argue this is bad timing as the project hasn't been given a chance to establish credibility with investors. Also information that supports decision making may be missing or incomplete. For example financial reports, NAV calculation methodology, etc.
  • Opportunity cost and precedence: Even if price is capped, deploying a large amount of treasury value has opportunity cost (i.e. takes away runway, hiring budget, etc.). It can also set a precedent where anytime price is trading below NAV, the community wants to trigger a decision market. So the DAO can get caught in constant price-defense decisions and related politics.
  • Decision legitimacy: If long-term investors interpret community driven decision markets as responding to short term price pain at the expense of long-term value, participation and trust can erode.

Some Ideas for a Better Proposal Process

Decision markets solve some governance problems, but they still need some guardrails, especially for certain proposal types.

Proposal classification: Some community members have suggested a short post-launch grace period on proposals. This could be more specific, like defining proposal classes with different "earliest allowed" windows as some proposal types are harder to evaluate early. For example, proposals involving buybacks, liquidity changes, and large token disbursements are delayed for 30 days post ICO. All other proposal types stay the same.

Financial transparency and disclosures: If a proposal uses NAV, a short disclosure would be helpful. This should include the treasury composition, treasury accounts, methodology (how NAV is calculated), and runway assumptions so misinformation/misinterpretation doesn't spread.

Protect execution runway: Set aside a baseline runway so builders can build, but don't make it too long as to significantly reduce the value of the investor liquidation option. This could be a fixed number of months of runway so the team can continue operating if things go sideways (like a chaotic liquidation).

Mechanism tuning: If a DAO keeps seeing proposals for buybacks, tune the decision market for that class of proposal:

  • Higher pass thresholds (i.e. 5% threshold) that reflects higher market conviction
  • Longer trading windows (i.e. 5-7 day trading window, TWAP after 24 hours) to smooth out short-term dynamics
  • Execution delay after a passed proposal ends (i.e. 2-5 days after) to decouple the decision from immediate price impact
  • Require a larger stake for the proposal to be initiated
  • Protocol level implementation of cool downs (for example, the recent buyback proposals specify a 90 day cool down, this can be enforced onchain)

Conclusion

The debate around the recent buyback proposals has been useful. There's no indication that community members proposing early buybacks acted in bad faith or outside the system's rules as designed. This kind of good-faith experimentation is exactly what helps communities that utilize decision markets evolve. While there are valid reasons to both support and criticize buyback proposals, the key takeaway is that some experimentation on proposal structure may be useful for "hard" proposals going forward. Some options for improvements include timing rules for certain proposal types, lightweight NAV disclosure when NAV is a focal point, and other tuning options such as higher pass thresholds, trading windows, and execution delays.