8.6 KiB
| type | title | author | url | date | domain | format | status | tags | event_type | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| source | Futardio: Liquidation Proposal for $SUPER | futard.io | https://www.metadao.fi/projects/superclaw/proposal/FZNt29qdEhvnJWswpoWvvAFV5TBhnpBzUaFced3ZFx1X | 2026-03-25 | internet-finance | data | null-result |
|
proposal |
Proposal Details
- Project: Superclaw
- Proposal: Liquidation Proposal for $SUPER
- Status: Draft
- Created: 2026-03-25
- URL: https://www.metadao.fi/projects/superclaw/proposal/FZNt29qdEhvnJWswpoWvvAFV5TBhnpBzUaFced3ZFx1X
Content
1. Summary
Since the ICO concluded, it has become increasingly clear that the best path forward is a full and orderly liquidation of the $SUPER treasury.
At this time:
- $SUPER is trading below NAV
- An additional month of operating spend would reduce NAV by approximately 11%
- Traction has remained limited
- Catalysts to date have not meaningfully changed market perception or business momentum
Given these circumstances, we believe the most responsible course of action is to preserve remaining value and return capital to tokenholders rather than continue funding operations with uncertain prospects.
If passed, this proposal would do the following:
- Remove all $SUPER / USDC liquidity from the Futarchy AMM
- Send all treasury USDC to a liquidation contract to be redeemed pro-rata excluding unissued and protocol owned tokens.
- Wind down the onchain treasury associated with the project
- Return any non-treasury assets, including intellectual property and related operating assets, to the appropriate original entity and/or the current contributors of Superclaw.
2. Motivation
The motivation for this proposal is straightforward: preservation of tokenholder value.
At present, $SUPER is trading below NAV. This creates a situation where continued spending is difficult to justify, particularly when each additional month of burn materially erodes the recoverable value of the treasury. Based on current estimates, one more month of monthly spend would reduce NAV by approximately 11%.
At the same time, traction remains limited. Despite multiple attempts to create momentum through catalysts, the market response has been muted and there is little evidence so far that these efforts are translating into sustained growth, stronger fundamentals, or improved confidence from tokenholders.
This proposal is not based on allegations of misconduct, fraud, or bad faith. Rather, it reflects a practical assessment of current conditions. Where a project is trading below NAV, traction is limited, and continued spend meaningfully reduces recoverable value, liquidation should be seriously considered as the most rational path.
We believe that returning capital now is preferable to continuing operations in a way that may further impair tokenholder value.
3. Proposed Plan
Part 1: Return all treasury funds to tokenholders
- No further discretionary operating spend will be made following passage of this proposal, other than costs strictly necessary to execute the wind-down and redemption process
- Remove protocol-owned liquidity upon passage of the proposal and add the USDC balance from the LP to the treasury USDC balance
- Open redemption for tokenholders
- Tokenholders will be able to redeem their tokens for the final book value presented on MetaDAO’s website
- After a defined claim period, any unclaimed USDC may be handled at the discretion of the MetaDAO team or future governance process
Book value calculation method
The final redemption value per token will be determined by:
- The total USDC held in treasury
- The USDC recovered from protocol-owned liquidity after LP removal
- The total number of eligible $SUPER tokens in circulation excluding protocol owned tokens
Final redemption value will depend on actual treasury balances, LP unwind outcomes, and the final eligible token count at the time of calculation.
Part 2: Treatment of non-treasury assets
Upon passage of this proposal, all non-treasury assets — including but not limited to intellectual property, trademarks, domain names, source code, infrastructure, and other operating assets — will return to the appropriate original entity and/or the current contributors of Superclaw.
The intent of this section is to ensure that treasury capital is returned to tokenholders while non-cash operating assets are handled in an orderly and legally coherent manner.
4. Conclusion
This proposal is based on capital preservation.
$SUPER is currently trading below NAV, traction remains limited, and additional monthly spend would materially reduce the value that could otherwise be returned to tokenholders. Under these conditions, we believe an orderly liquidation is the most responsible course of action.
Rather than continue deploying treasury capital in hopes that future catalysts may reverse current trends, this proposal seeks to maximize recoverable value today and return it fairly to tokenholders.
Agent Notes
Why this matters: Superclaw was the second-largest Futardio raise ($6M, 34% of all platform capital). Its liquidation proposal is the first direct test of futarchy's exit rights — the mechanism asserting that token holders can recover capital from a failing investment without relying on team discretion. If the proposal passes and executes correctly, it strengthens Belief #3 (futarchy solves trustless joint ownership) at the exit stage. If it fails or executes poorly, it reveals a critical weakness.
What surprised me: The proposal's language: "This proposal is not based on allegations of misconduct, fraud, or bad faith." This explicitly frames the liquidation as a MECHANISM FUNCTION, not a failure. The mechanism working as designed to preserve capital is the correct framing — but it also means the mechanism detected the problem only after reaching below-NAV, not earlier.
What I expected but didn't find: Evidence that futarchy governance markets were signaling "below NAV" before the proposal was created. The proposal mentions $SUPER is currently below NAV — but when did it reach below NAV? Was there a governance market signal earlier that could have triggered intervention? The proposal doesn't say. This is the reactive vs. proactive monitoring question.
KB connections:
- futarchy is manipulation-resistant because attack attempts create profitable opportunities for defenders — contrast case: here futarchy is protecting AGAINST team self-dealing, not external attack
- MetaDAOs futarchy shows limited uncontested trading — Superclaw's failure may be connected to governance market quality
- redistribution remains unsolved in futarchy-governed systems — liquidation IS a form of redistribution; this tests whether it works fairly
Extraction hints:
- Trustless exit rights claim (CC1 from Session 12): "Futarchy-governed liquidation enables trustless pro-rata capital recovery — Superclaw Proposal 3 demonstrates token holders can recover capital from a below-NAV treasury without depending on team discretion"
- Reactive monitoring claim (CC2 from Session 12): "Futarchy governance markets are reactive decision systems requiring team-initiated proposals — Superclaw's decline required manual detection and proposal creation, not market-triggered governance"
- Track outcome: Did Proposal 3 pass? What was the final NAV per token? Was redemption executed correctly?
Context: Superclaw raised $6M in the Futardio ICO — "AI agent infrastructure" narrative. It was the largest non-meta-bet raise in Futardio history. Its below-NAV status and liquidation proposal make it the clearest test case for futarchy's capital recovery mechanism.
Curator Notes (structured handoff for extractor)
PRIMARY CONNECTION: futarchy solves trustless joint ownership (Belief #3 — this proposal tests the exit rights property directly)
WHY ARCHIVED: First real-world test of futarchy's capital recovery function. The outcome (pass/fail, redemption accuracy) will be one of the most important data points for Belief #3. Extract AFTER proposal resolution for empirical confidence.
EXTRACTION HINT: Create two claims: (1) trustless exit rights mechanism claim (extract now as experimental), (2) reactive monitoring limitation claim (extract now as likely). Update both after outcome data is available. The pro-rata redemption mechanics described in the proposal are worth capturing independently as mechanism design documentation.
Raw Data
- Proposal account:
FZNt29qdEhvnJWswpoWvvAFV5TBhnpBzUaFced3ZFx1X - Proposal number: 3
- DAO account:
6WSUiKmBSM2B7QSxFAxgD9wquekzpkoRvKteFLvWWryU - Proposer:
8Cwx4yR2sFAC5Pdx2NgGHxCk1gJrtSTxJoyqVonqndhq - Autocrat version: 0.6